From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Everything and the kitchen sink
Date: Thu, 14 Feb 2013 16:48:13 +0100 [thread overview]
Message-ID: <511D073D.2040005@gmail.com> (raw)
In-Reply-To: <511CFD54.1050401@ubuntu.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
On 14.02.2013 16:05, Phillip Susi wrote:
> I recently had an incident that reminded me that while the grub rescue
> shell is better than nothing when there's a problem, it often isn't
> enough to troubleshoot and work around the error. These days most
> disks start the first partition at 1 MiB, so there is no need to keep
> the core.img slim and trim, so it would be really nice to throw all of
> the modules in there, so you can have a fully functional grub to help
> troubleshoot when things go wrong.
>
> Now I realize that I can manually build a ramdisk image to contain all
> modules, and pass that to grub-mkimage, but then as soon as grub is
> updated, and grub-install is re-run automatically, my changes would be
> wiped out.
>
> So I think what needs to happen is for grub-install to grow an
> --everything option where it would build the ramdisk and attach it
> automatically. Additionally there needs to be a conf file or
> something where this could be enabled so that it will be applied when
> grub is updated. It may also be nice to have this enabled by default
> when the embed area is detected to be large enough.
>
> Thoughts?
GRUB diskboot.S runs in real mode. No way it can load more than ~512K
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-02-14 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 15:05 Everything and the kitchen sink Phillip Susi
2013-02-14 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-02-14 19:34 ` Phillip Susi
2013-02-14 20:44 ` O_SYNC Phillip Susi
2013-03-20 14:15 ` Do not use O_SYNC Phillip Susi
2015-01-05 19:07 ` Phillip Susi
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=511D073D.2040005@gmail.com \
--to=phcoder@gmail.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.