From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: internal device representation
Date: Tue, 18 Jan 2005 12:04:09 +0100 [thread overview]
Message-ID: <200501181204.10144.okuji@enbug.org> (raw)
In-Reply-To: <6E8C0543-6911-11D9-A482-000A95A0560C@penguinppc.org>
On Tuesday 18 January 2005 06:25, Hollis Blanchard wrote:
> Nobody has replied to my previous mail about device syntax, so I will
> assume that means you all agree that I'm right about requiring
> different device syntaxes for different architectures. ;)
I don't agree. Sorry, I forgot to send a reply again.
You assume that aliases are made by a firmware, but I actually meant
that GRUB could make arbitrary aliases in itself, since GRUB has its
own device drivers. For example:
alias hd0 /path/to/a/device
This does not have to call Open Firmware, because GRUB itself can map
"hd0" to "/path/to/a/device" transparently.
I agree that you can use different naming conventions from architecture
to architecture, but I believe that the basic syntax should be the
same. For instance, I accept that you use "sd0" for a SCSI disk, which
is difficult on PC BIOS.
Okuji
next prev parent reply other threads:[~2005-01-18 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 5:25 internal device representation Hollis Blanchard
2005-01-18 11:04 ` Yoshinori K. Okuji [this message]
2005-01-18 14:41 ` Hollis Blanchard
2005-01-18 18:36 ` 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=200501181204.10144.okuji@enbug.org \
--to=okuji@enbug.org \
--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.