Date: Fri, 13 Mar 1998 16:19:08 -0800 From: Paul Traina <pst@juniper.net> To: jkh@FreeBSD.ORG Cc: committers@FreeBSD.ORG Subject: dumb question about fstab and 226 beta Message-ID: <199803140019.QAA01896@red.juniper.net>
next in thread | raw e-mail | index | archive | help
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. Was this intentional? If not, can we fix this before 226 ships? If it was intentional, I'd like to urge folks to rethink this. This is not an appropriate change for -stable, since there is not only a significant backwards compatibility problem, but the problem manifests itself in a very "unfixable" fashion -- you need console access to the box to discover the problem and fix it. I am now going to go off in the corner and read who made this change and why, and try to catch up on the lists, research I should have done before sending this mail. I apologize if I opened this can of worms up again, but this does need fixing. Paul 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?199803140019.QAA01896>