From: "Daniel Richard G." <oss@teragram.com>
To: "'The development of GNU GRUB'" <grub-devel@gnu.org>
Subject: RE: Trouble booting from a large USB hard drive
Date: Sun, 17 Jan 2010 15:45:06 -0500 [thread overview]
Message-ID: <000701ca97b5$f39bcff0$dad36fd0$@com> (raw)
In-Reply-To: <4B532073.2000706@isaac.cedarswampstudios.org>
[Replying with Outlook, please forgive the atrocious formatting]
Isaac Dupree wrote:
>
> I accidentally have an out-of-order partition table
> and I was surprised
> that such a thing is possible (vs. that everything
> gets automatically
> numbered in order). Nevertheless, it is a useful
> feature, though not
> obvious how to control with 'gparted' and the like.
> "extended
> partitions" probably add a bit of complication too.
Yes, I used fdisk(8) to get the effect, but with most "user-friendly"
partitioning tools I'd have been SOL. I'm thinking about the implications for
something like the Ubuntu installer/partitioner, which has to be dead simple
for the user, and yet producing an out-of-order table would be a helpful
measure of interoperability with Windows systems.
> if grub-install, which doesn't have code space
> limitations, could
> possibly check for it, it would be a great help. But
> is it possible for
> a running system to check the BIOS like that? (or
> possible for grub to
> check somehow on a non-running system in a safe
> testing sort of manner?)
Consider, too, that GRUB may be installed on a system where the BIOS is good,
and then booted on a system where it borks. USB drives have a natural mobility
to them, of course, and even IDE/SATA drives may be transplanted from one
computer to another.
--Daniel
next prev parent reply other threads:[~2010-01-17 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 9:25 Trouble booting from a large USB hard drive Daniel Richard G.
2010-01-17 14:36 ` Isaac Dupree
2010-01-17 20:45 ` Daniel Richard G. [this message]
2010-01-18 0:07 ` Colin Watson
2010-01-18 0:47 ` Isaac Dupree
2010-01-18 1:54 ` Daniel Richard G.
2010-01-18 12:38 ` Colin Watson
2010-01-18 18:15 ` Daniel Richard G.
2010-01-18 1:21 ` Grégoire Sutre
2010-01-18 2:10 ` Daniel Richard G.
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='000701ca97b5$f39bcff0$dad36fd0$@com' \
--to=oss@teragram.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.