Date: Fri, 13 Mar 1998 18:55:23 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Paul Traina <pst@juniper.net> Cc: jkh@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: dumb question about fstab and 226 beta Message-ID: <Pine.BSF.3.96.980313185412.19404D-100000@gdi.uoregon.edu> In-Reply-To: <199803140019.QAA01896@red.juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Mar 1998, Paul Traina wrote: > Sorry to bug you -- I admit this is a stupid question that should go to > "questions" but it may have 226 release implications I hadn't seen yet > on the mailing list (I'm kinda out of date due to travel). > > If this has already been settled, please accept my apologies. > > I just recently upgraded the kernel on a 225 machine to 226 and > the 226 kernel with 225 /sbin/mount would not allow me to use > /dev/sd0a in my fstab to represent root. I had to change it to > /dev/sd0s1a. It looks like someone broke the compatibility code. > I don't know if it was deliberate or not, probably so, but I think > this is really going to catch people with their pants down. I had this happen when i moved from one version to another some time ago. Looks like your system finally recognized that it's on a sliced disk and thought to update reality. Updating /etc/fstab is the correct thing to do. This may also happen if your devices were rebuilt. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980313185412.19404D-100000>