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 again
Date: Tue, 18 Jan 2005 16:36:08 +0100	[thread overview]
Message-ID: <200501181636.09127.okuji@enbug.org> (raw)
In-Reply-To: <98B29D3E-6960-11D9-A482-000A95A0560C@penguinppc.org>

On Tuesday 18 January 2005 15:52, Hollis Blanchard wrote:
> For now let's not talk about where aliases are created. What about my
> original question: grub has just booted, and when it asks what device
> it was booted from (the /chosen/bootpath property) it gets this:
> 	/pci@1f,0/pci@1,1/ide@3/disk@0,0
> (that is the real "disk" device on Vincent's UltraSparc). The next
> thing we want to do is load a config file from the same device. What
> value should we put into "prefix"?

This has already been discussed. Marco suggested to have a "boot drive" 
for this.

> Is the only reason you're suggesting this "alias" scheme is to keep
> the PC-style device syntax?

Don't call it "PC-style". This is not accurate. It is GRUB-style as _we_ 
define the syntax.

> 1) complexity and bugs in code to translate between the two,

Why? You can simply register a new device with a device path. What is 
complex?

> 2) frustrating UI requirements ("no no, you have to run 'alias'
> first"), and

GRUB can automatically create aliases.

> 3) require users to learn yet another syntax.

We have already discussed this, and I got no objection to my opinion at 
that time. I'm surprised that you refrain this.

Don't assume that ordinary users know Open Firmware or EFI. Basically, 
they don't know anything quite technical. So GRUB should provide an 
unique syntax rule so that users do not have to learn new things when 
they get new architectures.

And, have you ever asked any ordinary person to 
type /pci@1f,0/pci@1,1/ide@3/disk@0,0 rather than hd0? I'm sure that 
she will be scared. In addition, this would make remote assistance very 
hard. It should be easy to imagine how difficult it is to pronounce the 
long and mysterios string by phone.

As far as I know, most people use /dev/hda instead 
of /dev/ide/host0/bus0/target0/lun0/disc on Linux, whenever possible. 
This is simply because shorter is easier. Ordinary people think "the 
first IDE disk" instead of "the hard disk attached to the master of the 
first IDE bus of the main controller". Don't you agree?

Okuji



  reply	other threads:[~2005-01-18 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  0:57 device syntax again Hollis Blanchard
2005-01-18 14:52 ` Hollis Blanchard
2005-01-18 15:36   ` Yoshinori K. Okuji [this message]
2005-01-19  1:59     ` Hollis Blanchard
2005-01-19  7:58       ` Vincent Pelletier
2005-01-19 15:30         ` Hollis Blanchard
2005-01-19 10:06       ` Yoshinori K. Okuji
2005-01-21  2:33         ` Hollis Blanchard
2005-01-21 12:22           ` Marco Gerards
2005-01-21 14:38             ` Hollis Blanchard
2005-01-21 16:00               ` Yoshinori K. Okuji
2005-01-19 12:40       ` 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=200501181636.09127.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.