Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jul 1996 00:23:25 -0500
From:      Matt Rosenberg <matt@server.wulaw.wustl.edu>
To:        dwhite@resnet.uoregon.edu
Cc:        questions@freebsd.org
Subject:   Re: upgrade 2.1.0 -> 2.1.5
Message-ID:  <31F5B34D.3EC1@www.wulaw.wustl.edu>
References:  <Pine.BSI.3.94.960722151008.318O-100000@gdi.uoregon.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your response.

Doug White wrote:
> > I recently upgraded to 2.1.5 and the upgrade appeared to work properly,
> > but then once rebooted into 2.1.5 I'm having some problems.
> > The first most obvious problem is that on bootup I got error messages
> > about all sorts of lib files being the wrong version, but it would be
> > using them anyway.
> Are they yelling about 'libutil'?  It did that the first time I booted
> 2.1.5 then never saw anything about it again on any subsequent reboots.

Never saw it again after the first 2.1.5 boot except when starting X.

> > 2) When root (but not other users) logs into the terminal (which is set
> > for X-Windows) the login window disappears, an xterm window never
> > appears, and then xdm resets itself and you get the login window again.
> You shouldn't log in as root on any terminal.  Login as yourself then use
> 'su'.  I don't think my x will let me log in as root either.

Apparently the root .xsession file was altered and it was looking for
fvwm.  I switched back to twm and it works again.  I guess the upgrade
installation did that.  I don't know why or for that matter how else it
could have happened.

> > 3) On the nightly tape backup the cron daemon let me know that many of
> > the devices were not dumped, because the minor number was "too high".
> That is odd.

Still happening every night even with the new kernel installed.
 
> > 4) The dialout modem cuaa2 is no longer configured.  (That may also be a
> > kernel problem.... I have compiled but not yet installed my custom kernel.)
> GENERIC no longer recognizes any SIO devices over 0 and 1.  Your new
> kernel will fix that.

That was the problem.  sio2 works fine now.  However, when I dialup and
login as a slip user the system begins to display /etc/motd and then
drops carrier before that is even done (about 1 to 2 seconds).  It may
have nothing to do with 2.1.5 upgrade because I wasn't running as a SLIP
server before the upgrade.
-- 
=============================================
Matt Rosenberg
Washington University School of Law
St. Louis, MO, USA

matt@www.wulaw.wustl.edu
http://www.wulaw.wustl.edu/~matt/
=============================================



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31F5B34D.3EC1>