I would really appreciate it if someone would see if this patch to
GENERIC produces a kernel that can't mount a UFS root.
With this minimal change, I get the following when booting:
mount: ufs filesystem is not available
Filesystem mount failed, startup aborted
Enter full pathname for shell ....
I got this when I upgraded from the 19980803-SNAP (ie, pre-LETTERS), to
-CURRENT from a CVSup yesterday. I have *not* passed thru E-day, but the
CVSup did take me thru C-day and P-day.
Thru many kernel compiles, I have narrowed it down the changes below.
Note that uncommenting any one of the options resolves the problem. I
usually don't statically compile in these FS's so that the LKM versions
will be used.
-- David (obr...@NUXI.ucdavis.edu -or- obr...@FreeBSD.org)
--- GENERIC Sat Sep 19 13:55:55 1998
+++ MINBAD Tue Sep 29 23:45:23 1998
@@ -25,12 +25,12 @@
options INET #InterNETworking
options FFS #Berkeley Fast Filesystem
options NFS #Network Filesystem
-options MSDOSFS #MSDOS Filesystem
-options "CD9660" #ISO 9660 Filesystem
-options "CD9660_ROOT" #CD-ROM usable as root device
+#options MSDOSFS #MSDOS Filesystem
+#options "CD9660" #ISO 9660 Filesystem
+#options "CD9660_ROOT" #CD-ROM usable as root device
options FFS_ROOT #FFS usable as root device [keep this!]
-options NFS_ROOT #NFS usable as root device
-options PROCFS #Process filesystem
+#options NFS_ROOT #NFS usable as root device
+#options PROCFS #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device
options UCONSOLE #Allow users to grab the console
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message