grub-devel
[Top][All Lists]
Advanced

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

Re: Autoloading WAS: normal/cmdline bug & patch


From: Marco Gerards
Subject: Re: Autoloading WAS: normal/cmdline bug & patch
Date: Fri, 18 Jun 2004 15:51:38 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

address@hidden (Tomas Ebenlendr) writes:

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

Well, I know that.  It is how GRUB detects the filesystem type.

The problem is that the filesystem type can not be determined in a
uniform way.  You will have to include all tests in the core module.
That removes the flexibility.

Consider reiserfs.  If you want to detect if this module has to be
loaded, you need some reiserfs specific code to do that.  But what if
a user want to add another module?

>> 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.)

How about just loading every module that is sane for that
architecture?  For example all linux specific filesystems, fat on the
PC/alpha, hfs[+] on the apple, etc.

What do you mean with fs-auto, unfortunately I do not understand.
An example would help.

Thanks,
Marco





reply via email to

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