All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Autoloading WAS: normal/cmdline bug & patch
Date: Fri, 18 Jun 2004 20:50:15 +0200	[thread overview]
Message-ID: <87brjgbt08.fsf@marco.marco-g.com> (raw)
In-Reply-To: <874qp9dled.fsf@marco.marco-g.com> (Marco Gerards's message of "Fri, 18 Jun 2004 15:51:38 +0200")

Marco Gerards <metgerards@student.han.nl> 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	other threads:[~2004-06-18 18:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 11:31 normal/cmdline bug & patch Tomas Ebenlendr
2004-06-15 11:39 ` Tomas Ebenlendr
2004-06-15 13:45   ` Tomas Ebenlendr
2004-06-15 14:16     ` Marco Gerards
2004-06-15 16:22       ` Tomas Ebenlendr
2004-06-15 18:03         ` Tomas Ebenlendr
2004-06-15 20:36           ` Marco Gerards
2004-06-16  8:48             ` Tomas Ebenlendr
2004-06-18 20:54               ` Marco Gerards
2004-06-18 21:27                 ` Tomas Ebenlendr
2004-06-27 11:07                   ` Marco Gerards
2004-06-16  9:17             ` Yoshinori K. Okuji
2004-06-16 11:32               ` Marco Gerards
2004-06-16 12:33                 ` Marco Gerards <metgerards@student.han.nl> Tomas Ebenlendr
2004-06-16 12:36                   ` sorry Tomas Ebenlendr
2004-06-15 19:06         ` normal/cmdline bug & patch Marco Gerards
     [not found]           ` <20040615191931.GA18736@artax.karlin.mff.cuni.cz>
     [not found]             ` <873c4wh6um.fsf@marco.marco-g.com>
     [not found]               ` <20040616084333.GA17615@artax.karlin.mff.cuni.cz>
     [not found]                 ` <87pt7zag0e.fsf@marco.marco-g.com>
2004-06-16 11:50                   ` Tomas Ebenlendr
2004-06-18 10:45                     ` Yoshinori K. Okuji
2004-06-18 10:46                       ` Tomas Ebenlendr
2004-06-18 10:52                       ` Marco Gerards
2004-06-18 11:38                         ` Tomas Ebenlendr
2004-06-18 11:44                           ` Marco Gerards
2004-06-18 12:04                             ` Autoloading WAS: " Tomas Ebenlendr
2004-06-18 13:51                               ` Marco Gerards
2004-06-18 18:50                                 ` Marco Gerards [this message]
2004-06-18 19:16                                   ` Tomas Ebenlendr
2004-06-18 19:14                                 ` Tomas Ebenlendr
2004-06-19 15:05                                   ` Yoshinori K. Okuji
2004-06-19 16:01                                     ` Marco Gerards
2004-06-19 16:27                                       ` Jeroen Dekkers
2004-06-20 18:54                                       ` Yoshinori K. Okuji
2004-06-20  2:02                                     ` Tomas Ebenlendr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87brjgbt08.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.