From: komputes <komputes@gmail.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: The development of GRUB 2 <grub-devel@gnu.org>, summer-of-code@gnu.org
Subject: Re: Some GRUB ideas
Date: Wed, 09 Apr 2008 09:57:25 -0400 [thread overview]
Message-ID: <47FCCB45.5090702@gmail.com> (raw)
In-Reply-To: <87skxwkppr.fsf@ossau.uklinux.net>
You're probably right, although the focus of my question/feature request
is on the (hd0,0) syntax and not on the device file. I was thinking it
could prompt devices.map for the drive names. Grub can't use /dev/sda1
style syntax, you are correct, and I can't think of a logical workaround
other than that.
That being said, it would still be useful for the user to be able to see
what drive a grub has access to. Going back to the basic concept of the
request which was to simplify grub for the new user by displaying which
hard drives/partitions are available for grub to boot from (in (hd0,0)
syntax). This could help the user easily create a menu.lst from the grub
prompt/shell/menu.
-k
Neil Jerram wrote:
> komputes <komputes@gmail.com> writes:
>
>
>> $ grub --pitty-da-foo #this command doesn't exist (...yet)
>> Checking disks...
>>
>> Mem Used
>> (hd0) /dev/sda
>> (hd0,0) /dev/sda1 50GB 25%
>> (hd0,1) /dev/sda2 50GB 25%
>>
>> (hd1) /dev/sdb
>> (hd1,0) /dev/sdb1 50GB 25%
>> (hd1,1) /dev/sdb2 50GB 25%
>>
>
> Just a thought: but if Grub could do that, couldn't it just accept the
> "/dev/sda1"-style syntax everywhere?
>
> Regards,
> Neil
>
>
>
next prev parent reply other threads:[~2008-04-09 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 16:35 Some GRUB ideas Robert Millan
2008-04-07 18:15 ` komputes
2008-04-07 18:29 ` Colin D Bennett
[not found] ` <87skxwkppr.fsf@ossau.uklinux.net>
2008-04-09 13:57 ` komputes [this message]
2008-04-10 22:35 ` Pavel Roskin
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=47FCCB45.5090702@gmail.com \
--to=komputes@gmail.com \
--cc=grub-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=summer-of-code@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.