Date: Mon, 9 Mar 1998 01:25:48 -0600 (CST) From: igor@alecto.physics.uiuc.edu (Igor Roshchin) To: mike@smith.net.au (Mike Smith) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: *HEADS UP* Important change warning. (long version) Message-ID: <199803090725.BAA05040@alecto.physics.uiuc.edu> In-Reply-To: <199803090723.XAA13717@dingo.cdrom.com> from "Mike Smith" at Mar 8, 98 11:23:49 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, Mike, I didn't mean to be mean or offensive. My appologies, if it sounded that way. IgoR > > > > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803090725.BAA05040>