All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: moving ata initialisation to a command
Date: Fri, 21 Dec 2007 17:47:36 +0100	[thread overview]
Message-ID: <8763ysyoyf.fsf@xs4all.nl> (raw)
In-Reply-To: <20071220173607.GA20508@thorin> (Robert Millan's message of "Thu,  20 Dec 2007 18:36:07 +0100")

Robert Millan <rmh@aybabtu.com> writes:

> On Mon, Dec 17, 2007 at 01:26:31PM -0500, Pavel Roskin wrote:
>> On Mon, 2007-12-17 at 17:01 +0100, Marco Gerards wrote:
>> > A better solution, IMO, would be changing grub-mkrescue so it doesn't
>> > load all modules.
>> 
>> Maybe grub-mkrescue should create a filesystem?  Even FAT should be
>> fine.  This way, it will be possible to load problematic modules from
>> the filesystem.  The only problem would be dependency on filesystem
>> making tools.  Fortunately, mtools is quite common.
>
> I'd prefer to support embedding filesystems in core.img instead.  This
> solves the problem for every situation instead of just PC boot media
> (e.g. LinuxBIOS ELF payload image).

Agreed, I would like to see such feature.  Also for stuff like
diskless boot.

What I had in mind was the following.  We could perhaps make it
possible to add all files using grub-mkimage, not only modules.  When
you add modules, those will be loaded automatically.  All other files
will be ignored.

Another filesystem module has to be written.  It scans over these
files and will make them available.  This can be simple and elegant.
I do not like the idea of adding a diskimage or so.  Are you
interested in working on this?

> Anyway, as long as root privileges aren't made necessary, I'm fine with
> grub-mkrescue creating a filesystem (one saner than FAT, preferably ;-).

Great!  Will you do that? :-)

--
Marco




  reply	other threads:[~2007-12-21 16:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 15:30 moving ata initialisation to a command Robert Millan
2007-12-16 15:58 ` Christian Franke
2007-12-16 16:06 ` Vesa Jääskeläinen
2007-12-16 16:19   ` Robert Millan
2007-12-17 15:52     ` Marco Gerards
2007-12-17 16:01 ` Marco Gerards
2007-12-17 18:26   ` Pavel Roskin
2007-12-17 19:01     ` Marco Gerards
2007-12-20 17:38       ` Robert Millan
2007-12-20 17:36     ` Robert Millan
2007-12-21 16:47       ` Marco Gerards [this message]
2007-12-21 18:04         ` Robert Millan
2007-12-21 20:54           ` embedding filesystems in core image (Re: moving ata initialisation to a command) Robert Millan
2007-12-22  4:28             ` Bean
2007-12-22 11:24               ` Robert Millan
2007-12-22 12:27                 ` Yoshinori K. Okuji
2007-12-22 12:18               ` Robert Millan
2007-12-22 12:24                 ` Yoshinori K. Okuji
2007-12-23 18:44                   ` Robert Millan
2008-01-16 20:10                     ` Marco Gerards
2008-01-20 23:21                       ` Robert Millan
2007-12-24  8:29                 ` Bean
2007-12-24 13:09                   ` Robert Millan
2007-12-24 13:27                     ` Bean
2007-12-24 16:24                       ` Robert Millan
2007-12-24 16:44                         ` Bean
2008-01-02 19:56             ` Robert Millan
2007-12-26  8:00       ` embedding data in ELF " Robert Millan
2008-01-02 18:21         ` Pavel Roskin
2007-12-26  7:57   ` avoid firmware in grub-mkrescue " Robert Millan

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=8763ysyoyf.fsf@xs4all.nl \
    --to=mgerards@xs4all.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.