[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Autoloading WAS: normal/cmdline bug & patch

From: Tomas Ebenlendr
Subject: Re: Autoloading WAS: normal/cmdline bug & patch
Date: Fri, 18 Jun 2004 14:04:11 +0200
User-agent: Mutt/1.5.6i

> >
> > linux.mod cmd linux
> > ext2.mod fs /"file" like magic-recognition pattern (may have whitespaces)/
> How do you know which filesystem to use?  For example when accessing a
> ufs filesystem?

Do you tried unix command 'file' on some partition?

$ file -sk /dev/hda1
/dev/hda1: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1",
sectors/cluster 8, Media descriptor 0xf8, heads 240, hidden sectors
1164303, sectors 10251297 (volumes > 32 MB) , FAT (32 bit), sectors/FAT
9993, rootdir cluster 655, reserved3 0x800000, serial number 0x164d1002,
label: "WIN        "
$ file -sk /dev/hda2
/dev/hda2: x86 boot sector, code offset 0x48\012- Linux rev 0.0 ext2
filesystem data (mounted or unclean)

I think every fs can be identified using some "magic". This was what i
mean by "file" like recognition pattern.

> How about loading all filesystems explicitly in grub.conf?

yes this is much simper (and with less bugs be here), but user must know
which fs he uses. But he can have comfort when booting grub from CD, not
to load every fs module by grub.conf and also not to type insmod.
(Ok, in grub.conf will be specified something like fs-auto.mod which
will implement domain 'fs' for module autoloader.)

                                 Tomas 'ebi' Ebenlendr
                                 PF 2004.46332982316

reply via email to

[Prev in Thread] Current Thread [Next in Thread]