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 15:51:38 +0200	[thread overview]
Message-ID: <874qp9dled.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20040618120411.GA20750@artax.karlin.mff.cuni.cz> (Tomas Ebenlendr's message of "Fri, 18 Jun 2004 14:04:11 +0200")

ebik@artax.karlin.mff.cuni.cz (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	other threads:[~2004-06-18 13:53 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 [this message]
2004-06-18 18:50                                 ` Marco Gerards
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=874qp9dled.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.