All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Gerards" <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>,
	Hollis Blanchard <hollis@penguinppc.org>
Subject: Re: device syntax
Date: Wed, 20 Oct 2004 16:44:25 +0200	[thread overview]
Message-ID: <1098283465.417679c90a494@webmail.han.nl> (raw)
In-Reply-To: <FCC87996-22A0-11D9-AB55-000A95A0560C@penguinppc.org>

Quoting Hollis Blanchard <hollis@penguinppc.org>:

> On Oct 20, 2004, at 3:58 AM, Marco Gerards wrote:
> 
> > Hollis Blanchard <hollis@penguinppc.org> writes:
> >
> >> I was thinking about how GRUB specifies device paths using
> >> "(device,partition)/path" syntax. That's a problem because Open
> >> Firmware device paths can contain commas. The legal character list is
> >> the alphanumerics plus ", . _ + -". My Mac's video card is named
> >> "ATY,Rage128y", and I'm pretty sure I've seen disks with commas in
> >> their names.
> >
> > Does this problem occur for disks as well in practice?
> 
> On my briQ, the hda devalias is "/pci@FF500000/isa@6/ide@i1f0/disk@0,0".

But in that case you could use (hda,0), right?

--
Marco



  reply	other threads:[~2004-10-20 14:59 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 [this message]
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
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=1098283465.417679c90a494@webmail.han.nl \
    --to=metgerards@student.han.nl \
    --cc=grub-devel@gnu.org \
    --cc=hollis@penguinppc.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.