From owner-freebsd-questions Thu Aug 8 22:53:57 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA13239 for questions-outgoing; Thu, 8 Aug 1996 22:53:57 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts7-line3.uoregon.edu [128.223.150.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA13234 for ; Thu, 8 Aug 1996 22:53:52 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id WAA00239; Thu, 8 Aug 1996 22:53:36 -0700 (PDT) Date: Thu, 8 Aug 1996 22:53:36 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Branson Matheson cc: FreeBSD-Questions@FreeBSD.ORG Subject: Re: 2.1.5 Failure In-Reply-To: <199608081316.JAA00812@garion.hq.ferg.com> 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 Thu, 8 Aug 1996, Branson Matheson wrote: > Well I "upgraded" my machine last night here at work and had LOTS of > problems. Here is the list: > > 1) the upgrade said it was gonna copy the old files into > /scratch/etc ( where I wanted them ) but after it finished, I found > that the only files there were the new ones :-(. Good thing I did > not trust the installtion and stored them elsewhere. It's a sysconfig bug (or feature?). It happened to me too. > 2) Big Problem with the ep driver. I have been running this system > solidly for some time now. After the upgrade, whenever I am using > the epdriver, the number of socknames and headers and data steadily > increases until all network traffic ceases on the device and finally > I start to get errors like this: The ep driver is acknowledged to be problematic. 2.1.5 was re-released to repair this bug, so if you grabbed your copy just after it was put up on ftp.freebsd.org I'd try re-getting the kernel sources and recompiling. > 3) mountd hangs at startup. I did a ktrace of mountd and it seems to > hang right as it reads resolv.conf. I read in todays mail about the > issue of having non locally resolvable hostnames in /etc/resolv.conf > ( Ie. ones normally resolved over the network ) and I will add them > to the /etc/hosts file and fix /etc/hosts.conf to check that first > and see if that solves the problem. That usually does it. > I am rather frustrated and I have to have this machine working, so I > am downgrading back to 2.1 until this issue is resolved. If anyone > has any idears or suggestions, let me know. I don't quite know what to make of the ep problems other than not using a 3com adapter until the problem is fixed. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major