From owner-freebsd-fs Mon Apr 2 19:56: 7 2001 Delivered-To: freebsd-fs@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [216.224.193.50]) by hub.freebsd.org (Postfix) with ESMTP id 558C337B71B for ; Mon, 2 Apr 2001 19:56:04 -0700 (PDT) (envelope-from kirk@honeypot.net) Received: from pooh.honeypot (mail@pooh.honeypot [10.0.1.2]) by kanga.honeypot.net (8.11.3/8.11.3) with ESMTP id f332u1N13267 for ; Mon, 2 Apr 2001 21:56:03 -0500 (CDT) (envelope-from kirk@honeypot.net) Received: from kirk by pooh.honeypot with local (Exim 3.12 #1 (Debian)) id 14kGzA-000081-00 for ; Mon, 02 Apr 2001 21:56:00 -0500 To: freebsd-fs@freebsd.org Subject: Re: My Vinum heart attack References: <87vgooi7kz.fsf@pooh.honeypot> <878zljmnw9.fsf@pooh.honeypot> <20010403093947.K25226@wantadilla.lemis.com> From: Kirk Strauser Date: 02 Apr 2001 21:56:00 -0500 In-Reply-To: <20010403093947.K25226@wantadilla.lemis.com> Message-ID: <873dbqhetb.fsf@pooh.honeypot> Lines: 53 X-Mailer: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 2001-04-03T00:09:48Z, Greg Lehey writes: > The real issue here is that you seemed to think it OK to update your > kernel and not update userland. Experienced people will say "that's a > no-no", but somehow you were able to get that impression. I'm still > planning to investigate how this could happen. Greg, I'm honestly not trying to be argumentative, but I don't quite agree with your statement. I freely admit that I'm not as experienced with FreeBSD as some people (particularly those with subject-matter books with their name :) ), but I don't think that I'm particularly incapable of reading documentation. In this case, following the "official" instructions to the letter produced unforeseen consequences. I'm sure that I'll gain wisdom with experience, but for now I'm just a relative (one year) newbie who does as instructed. I completely understand the need to keep kernel and userland in sync. However, given that the instructions in /usr/src/UPDATING are a bit misleading, I still don't know the "correct" way to installworld. That file says, and I quote: make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster reboot [1] You can often get away without doing this step as the system will be properly updated. During the running of the installworld, however, system components may break and other oddities may happen. To a newbie's eyes, that can seem to say that if you don't reboot into single user mode (with the new kernel, freshly installed in the previous step), then parts of your system may be broken. That may very well be an incorrect interpretation, but I'm not experienced enough with my chosen favorite system to know what else it could mean. > In any case, it does look as if you paniced. I did indeed. > If you had rebooted with the old kernel, all would have been well. I did, and it was, but only because of experience with other systems (cardinal rule: when I get lost, I stop moving until I regain direction). If I had less experience then I shudder to think of what I might've done next. -- Kirk Strauser To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message