From owner-freebsd-stable Sun Mar 8 23:26:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23126 for freebsd-stable-outgoing; Sun, 8 Mar 1998 23:26:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23119 for ; Sun, 8 Mar 1998 23:26:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA13717; Sun, 8 Mar 1998 23:23:50 -0800 (PST) Message-Id: <199803090723.XAA13717@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: igor@alecto.physics.uiuc.edu (Igor Roshchin) cc: john.saunders@scitec.com.au (John Saunders), mike@smith.net.au, freebsd-stable@FreeBSD.ORG Subject: Re: *HEADS UP* Important change warning. (long version) In-reply-to: Your message of "Mon, 09 Mar 1998 01:10:07 CST." <199803090710.BAA04713@alecto.physics.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 23:23:49 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > > Don't know why some people get so emotional about the name of a device. > > If FreeBSD is to move forward we all must accept that change is > > inevitable. Mike also did a good job of warning us before hand. > > 3 hours advance notice ? or I just missed something ? ;) The point behind the announcement was that, if you're serious, you read -stable *before* you rebuild. The updates and the messages were timed to avoid any gaps, but I don't have the luxury of a few months to let one change propagate before building on it. 8( > Sitting in front of all your computers you might be forgetting that > There are plenty (or at least - quite a few) of people who are doing > such upgrades remotely... If you are doing remote upgrades without a fallback plan, and without local testing, then you are already accepting a plethora of risks. We can't stop you from shooting you feet off, much as we'd like to. > I am a bit confused: what would be the behavior of an updated system > with the disk which was divided as follows: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0a 31775 24103 5130 82% / > /dev/wd0s1g 1004015 558208 365486 60% /home > /dev/wd0s2e 63567 19 58463 0% /tmp > /dev/wd0s1e 500463 290300 170126 63% /usr > /dev/wd0s2f 2980238 645811 2096008 24% /usr2 > /dev/wd0s2g 2878330 2485211 162853 94% /usr3 > /dev/wd0s1f 98479 2869 87732 3% /var > /dev/wd0s1h 98802 23382 67516 26% /var/log This will result in a diagnostic from mount at boot time, telling you that you should be mounting /dev/wd0s1a on /. If you have updated mount as per messages to this list, you'll still work just fine. > Also, > If a have an "inherited" computer - > how can I tell whether it has an old or a new type of slices without going > into /stand/sysinstall .... ? Install the new kernel and new mount. It will tell you if things need to be changed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message