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 20:50:15 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Marco Gerards <address@hidden> writes:

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

Perhaps it would be better to do this just when it is required.  So
whenever all loaded filesystems are scanned and the filesystem is not
detected GRUB needs to load new modules.  So it loads modules in a
fixed order (sorted on how likely it is that the filesystem is used,
perhaps).

We can even make a /boot/grub/fs directory and just load the modules
from there.  Of course you just read the modules until you found the
required module.

The advantage of this approach is that you just have to load modules
when there is a need for it.  The bad thing is that something like `ls
(hd)' will become slower.

Anyway, I'd like to hear more ideas about this.  I am just
brainstorming. :)

Thanks,
Marco





reply via email to

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