All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: device syntax
Date: Thu, 21 Oct 2004 12:53:10 +0200	[thread overview]
Message-ID: <200410211253.10450.okuji@enbug.org> (raw)
In-Reply-To: <D7B7CD2C-22AB-11D9-AB55-000A95A0560C@penguinppc.org>

I prefer consistency among various architectures. Note that PC BIOS does 
not offer any name for drives. They are represented by numbers. "hd" 
and "fd" are aliases for numbers.

If we assume that the user knows her firmware very well, we don't need 
to provide "hd" or "fd", since the user should be able to specify 
numbers. Actually, specifying drives by numbers is supported by GRUB 
legacy, but nobody uses it, simply because it is not intuitive.

IMO, we should not assume that the user knows technical details. If we 
write an installer for Open Firmware-based machines, the user may not 
know anything about Open Firmware. The best thing for the user is that 
the user does not have to learn many things. If we provide a consistent 
interface, the user needs to study the single thing. Nothing else.

I think the important goal for GRUB is to provide an easy way for 
ordinary users and a complicated but still useful features for experts. 
So I propose always using simple aliases for drives. If you want to use 
a device name provided by your firmware explicitly, you could use this 
kind of syntax:

devalias foo "/pci@FF500000/isa@6/ide@i1f0/disk@0,0"
multiboot (foo,0)/boot/kernel

EFI uses more horrible device names. This is quoted from EFI How To 
Guide:

Acpi(PNP0A03,1)/PCI(0|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig1B16CC00-ABD0-0)

If we use escape chacters, it becomes too unreadable.

Okuji



  reply	other threads:[~2004-10-21 11:00 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 [this message]
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=200410211253.10450.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.