From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] memdisk plus lnxboot extension
Date: Wed, 23 Jan 2008 20:10:56 +0100 [thread overview]
Message-ID: <20080123191056.GA15742@thorin> (raw)
In-Reply-To: <ca0f59980801230818r7978a084o8c75de8ff6269795@mail.gmail.com>
On Thu, Jan 24, 2008 at 12:18:43AM +0800, Bean wrote:
> On Jan 23, 2008 4:54 PM, Marco Gerards <mgerards@xs4all.nl> wrote:
> > When is this feature useful? Can you give an example? More features
> > can mean more bugs, more maintainance work, etc. If the feature is
> > not worthwhile for more than one person, I am not sure if it should be
> > included. Perhaps a better explaination of the problem to solve,
> > instead of what the patch does might help here.
>
> the most important usage of external initrd is to overcome the size
> limit of core.img.
I understand that it overcomes a size limit, but, in which situations would
this be used? core.img is primarily targetted at being used with grub-setup
(where memdisk isn't needed), to be chainloaded from GRUB Legacy (where
memdisk isn't necessary either), or to build a rescue floppy (where this
feature, in principle, can't be used). Do you have other uses of core.img
in mind?
And in the case of rescue floppies, if we find a way to overcome the size
limit via loading memdisk image separately, I don't think using Linux boot
semantics is the best way to do it. Linux excels at a lot of things, but its
boot mechanism is full of legacy cruft. I don't think it's the best option
to take as a reference to implement GRUB.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-01-23 19:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 9:05 [PATCH] memdisk plus lnxboot extension Bean
2007-12-30 13:48 ` Robert Millan
2008-01-20 23:24 ` Robert Millan
2008-01-22 4:25 ` Bean
2008-01-22 13:57 ` Robert Millan
2008-01-22 16:22 ` Bean
2008-01-22 16:51 ` Robert Millan
2008-01-22 17:17 ` Bean
2008-01-22 19:53 ` Robert Millan
2008-01-23 8:54 ` Marco Gerards
2008-01-23 16:18 ` Bean
2008-01-23 19:01 ` Bean
2008-01-23 19:14 ` Robert Millan
2008-01-23 19:24 ` Bean
2008-01-23 20:15 ` Robert Millan
2008-01-23 21:04 ` Bean
2008-01-23 21:15 ` Robert Millan
2008-01-24 3:40 ` Bean
2008-01-24 11:32 ` Robert Millan
2008-01-24 11:49 ` Bean
2008-01-24 14:25 ` Robert Millan
2008-01-24 14:57 ` Bean
2008-01-24 15:16 ` Robert Millan
2008-01-24 16:55 ` Robert Millan
2008-01-24 17:04 ` Bean
2008-01-24 17:21 ` Robert Millan
2008-01-24 18:06 ` Marco Gerards
2008-01-24 21:23 ` Yoshinori K. Okuji
2008-01-23 19:10 ` Robert Millan [this message]
2008-01-23 8:48 ` Marco Gerards
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=20080123191056.GA15742@thorin \
--to=rmh@aybabtu.com \
--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.