From owner-freebsd-stable Tue Dec 30 12:10:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21589 for stable-outgoing; Tue, 30 Dec 1997 12:10:21 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA21583 for ; Tue, 30 Dec 1997 12:10:16 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xn7zM-0004Tp-00; Tue, 30 Dec 1997 13:10:08 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA29978; Tue, 30 Dec 1997 13:10:26 -0700 (MST) Message-Id: <199712302010.NAA29978@harmony.village.org> To: Tom Subject: Re: Nov 21st stable kernel panicking... Cc: The Hermit Hacker , Wut!? , freebsd-stable@freebsd.org In-reply-to: Your message of "Tue, 30 Dec 1997 10:04:35 PST." References: Date: Tue, 30 Dec 1997 13:10:26 -0700 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Tom writes: : Do an entire make world is important, updating /etc/ isn't. After all, : the /etc/rc* stuff is just shell scripts. I have 2.2.5 boxes running with : /etc/rc* from 2.1. However these shell scripts don't work so well, if : bins that mess with the kernel aren't updated. Just as an aside, I have (or had until very recently) a -current system that used the 2.0.5R rc scripts. Worked just fine. Fear of the unknown kept me from upgrading, and the "don't fix what ain't broken" mantra. After getting some rc.conf expereinces under my belt, and seeing how easy it was to do, I changed my mind and upgraded after the next make world. There are those in the -core team that tell of systems they have had since patchkit days that still have the same rc scripts..... Warner