From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: device syntax
Date: Thu, 28 Oct 2004 19:02:27 +0000 [thread overview]
Message-ID: <87bremvf7g.fsf@marco.marco-g.com> (raw)
In-Reply-To: <1F8CE95E-2371-11D9-A336-000A95A0560C@penguinppc.org> (Hollis Blanchard's message of "Thu, 21 Oct 2004 09:54:35 -0500")
Hollis Blanchard <hollis@penguinppc.org> writes:
>> devalias foo "/pci@FF500000/isa@6/ide@i1f0/disk@0,0"
>> multiboot (foo,0)/boot/kernel
>
> I suspect it will be a point of confusion that a user can directly use
> "hda" (a real/OF devalias) for their first disk, but if they want to
> use their second disk they must add a devalias command to their
> menu.lst file (or in OF itself).
Why do they have to add it to the menu.lst? You can add additional OF
devaliases using the OF command line interface. But there is no
problem to make a temporary one either.
What Okuji described is exactly what I had in mind when I initially
started working on the PPC port. You can use devaliases in any case,
although it would be nice if it is possible to use a full path, which
is what your patch made possible. But if the full path conflicts with
the GRUB syntax, it just shouldn't be used...
--
Marco
next prev parent reply other threads:[~2004-10-28 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 2:14 device syntax Hollis Blanchard
2004-10-20 8:58 ` Marco Gerards
2004-10-20 7:33 ` Tomas Ebenlendr
2004-10-20 9:47 ` Marco Gerards
2004-10-20 10:13 ` Tomas Ebenlendr
2004-10-20 14:14 ` Hollis Blanchard
2004-10-20 14:04 ` Hollis Blanchard
2004-10-20 14:44 ` M. Gerards
2004-10-20 15:22 ` Hollis Blanchard
2004-10-21 10:53 ` Yoshinori K. Okuji
2004-10-21 11:26 ` Tomas Ebenlendr
2004-10-21 11:33 ` Yoshinori K. Okuji
2004-10-28 18:59 ` Marco Gerards
2004-10-21 14:54 ` Hollis Blanchard
2004-10-28 19:02 ` Marco Gerards [this message]
2004-10-29 1:40 ` Hollis Blanchard
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=87bremvf7g.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--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.