From owner-freebsd-questions Mon Jul 22 15:12:13 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15419 for questions-outgoing; Mon, 22 Jul 1996 15:12:13 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts9-line14.uoregon.edu [128.223.150.95]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA15408 for ; Mon, 22 Jul 1996 15:12:05 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id PAA00423; Mon, 22 Jul 1996 15:12:05 -0700 (PDT) Date: Mon, 22 Jul 1996 15:12:05 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Matt Rosenberg cc: questions@freebsd.org Subject: Re: upgrade 2.1.0 -> 2.1.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Matt Rosenberg 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. > All of the others are likely related: > > 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. > 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. > 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. I'd stick in your new kernel, reboot, and see what you get. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major