From owner-freebsd-stable Sun Apr 11 15:37: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 2FD2415B17 for ; Sun, 11 Apr 1999 15:36:22 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10WN7k-0003vM-00; Sun, 11 Apr 1999 09:30:20 -0700 Date: Sun, 11 Apr 1999 09:30:18 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Spidey Cc: FreeBSD Stable , Eric Griff Subject: Re: SOLVED. Re: ps problems (explained) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Spidey wrote: > Well, I think that it does. I think that it was the cause of my problems, > until another theory seems more valuable. I see no other thing. > > And it does make a difference, technically, because some files are > installed as they are used! So files like /var/run/utmp that are often > written, if they are written as they are installed, kaput! > > Am I wrong? Yes you are. /var/run/utmp is a data file. It isn't even "installed" during a installworld. It was probably damaged during a switch from 8 character usernames to 16 character names. Just copy /dev/null over it, and everything is fixed. Also, you stating that you started you system without a procfs, because it had become "corrupted". That too is impossible, because procfs is created during boot and resides completely in memory. Also, running without procfs is really bad. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message