Joshua Oreman <oremanj@...> writes:
Thanks for your help.
> On Sun, Oct 05, 2003 at 05:24:28PM +0200 or thereabouts, Bernhard Marx wrote:
>> "Hugo Rabson" <hugo.rabson@...> writes:
>> | Finalize softlinks...mkdir: cannot create directory `/usr/lib/libncurses.so.4': file exists
>> is still there compare now seems to work almost.
> Benign error.
>> after typing 'compare' at the boot promt mindi/mondo boots fine. The
>> only thing that goes awry is that it can't mount my ext3 filesystems:
>> | Could not mount devices /dev/hda5 ...
>> Of course the following compare goes wrong.
>> But all ext3 filesysstems are marked as fstype auto in /etc/fstab. The
> Well why didn't you say so earlier!?
When was I supposed to say that earlier? In my initial post? I simply
wasn't aware of this.
>> failsafe kernel doesn't seem to support ext3. I thought though that the
> It does, but Mondo doesn't support "auto". Yet.
>> ide of fstype 'auto' in /etc/fstab was that kernels not supporting ext3
>> should automatically mount these partitions as ext2.
> And that programs that try to parse the fstab will get all screwed up...
> Mondo uses the "fstype" field almost exactly as the -t argument to mount.
In my Debian system "mount -t auto" does mount ext3 filesystems. The
manpage to fstab doesn't talk about this but man mount does:
If no -t option is given, or
if the auto type is specified, the superblock is probed for the
filesystem type (adfs, bfs, cramfs, ext, ext2, ext3, hfs, hpfs,
iso9660, jfs, minix, ntfs, qnx4, reiserfs, romfs, udf, ufs,
vxfs, xfs, xiafs are supported). If this probe fails, mount
will try to read the file /etc/filesystems, or, if that does not
exist, /proc/filesystems. All of the filesystem types listed
there will be tried, except for those that are labeled "nodev"
(e.g., devpts, proc and nfs). If /etc/filesystems ends in a
line with a single * only, mount will read /proc/filesystems
The auto type may be useful for user-mounted floppies. Creating
a file /etc/filesystems can be useful to change the probe order
(e.g., to try vfat before msdos) or if you use a kernel module
autoloader. Warning: the probing uses a heuristic (the presence
of appropriate `magic'), and could recognize the wrong filesys-
tem type, possibly with catastrophic consequences. If your data
is valuable, don't ask mount to guess.
More than one type may be specified in a comma separated list.
> The only exception is comma-separated formats, e.g. "ext3,ext2" will try
> ext3 if supported and ext2 if not, AND Mondo will parse it correctly.
OK. I changed my fstab to:
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/hda5 / ext3,ext2 errors=remount-ro 0
/dev/hda2 swap swap defaults 0 0
proc /proc proc defaults 0 0
/dev/hda1 /boot ext2 errors=remount-ro 0 2
/dev/hda7 /mnt/data ext3,ext2 errors=remount-ro 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/cdrom1 /dvd iso9660 ro,user,noauto 0 0
/dev/sr1 /mnt/dvd-ram auto user,noauto 0 0
/dev/sda1 /mnt/cf auto user,noauto,noatime 0 0
But the problem still remains: mondo won't mount /dev/hda5 and /dev/hda7
> Yes. Workaround: Fix your fstab! :-)
see above. Maybe I need some more fixing? :-)
> The failsafe kernel DOES support ext3. See above.
Hm, then I might not be using the failsafe kernel although I DID specify
"-k FAILSAFE" .
When I'm in the mondo/mindi shell after booting from cd and try to mount
an ext3 partition by specifying "-t ext3" or "-t auto" I get the
errormessage "mount: fs type ext3 not supported by kernel"
How can I make sure I use the FAILSAFE kernel? Ill boot again and see
what dmesg has to say about the kernel version.