The mount capability has to be included as a kernel option in a custom build kernel. I forget exactly what it's called (I'm writing in another OS on the system, so I can't check it right now), but I think it's something like this:
option EXT2FS
Have you included that in your kernel build?
/Paul
Rahul Siddharthan wrote:
Paul A. Mayer wrote:I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc.Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a "real" linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it?The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashesNot a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
