All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: partition layouts - "root"
Date: Thu, 07 Apr 2005 16:37:31 +0200	[thread overview]
Message-ID: <87oecqfyac.fsf@student.han.nl> (raw)
In-Reply-To: <200504071617.11721.okuji@enbug.org> (Yoshinori K. Okuji's message of "Thu, 7 Apr 2005 16:17:11 +0200")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> On Thursday 07 April 2005 02:02 am, Hollis Blanchard wrote:
>> It's clear to you and I, but seeing "root=foo" "root=bar" is obviously
>> not very friendly and in general should be avoided.
>
> I understand your point. But I don't like "device", because it is too generic.

Someone suggested bootdevice on IRC.  I like that one, while is not
that generic.

> The advantage of "root" is that all GRUB Legacy users understand it.

This is really important, I think.

> One radical change would be to introduce the concept of "current working 
> device" or "current working directory":
>
> grub> cd (hd0)
> grub> pwd
> (hd0)
>
> This is consistent with Bash, but users would expect that they can do "cd 
> (hd0,0)/boot". Then the behavior of "ls" or TAB is inconsistent.

This should not be the case.  Not if both tab, ls, linux, etc work
from pwd.  In that case you can cd somewhere and everything you use is
in the current dir.  And there are relative (../foo) and absolute
(/foo) paths.

This is all consistent with bash.  And it should work with all
filesystems I have implemented.  I would like this approach.  You
could even parse `.', `..' and `/' in fs.c so it becomes generic and
you don't have to pass idiotic strings to the filesystems.

Thanks,
Marco



  reply	other threads:[~2005-04-07 14:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05  0:38 partition layouts Hollis Blanchard
2005-04-05  4:55 ` Vernon Mauery
2005-04-05  7:02   ` Marco Gerards
2005-04-05 13:40     ` Vernon Mauery
2005-04-05 13:50       ` Marco Gerards
2005-04-05 15:50     ` Hollis Blanchard
2005-04-05 15:47   ` partition layouts - separate /boot Hollis Blanchard
2005-04-05  5:41 ` partition layouts Yoshinori K. Okuji
2005-04-05 16:01   ` Hollis Blanchard
2005-04-05 16:45     ` Marco Gerards
2005-04-05 22:53       ` partition layouts - "root" Hollis Blanchard
2005-04-06  6:32         ` Marco Gerards
2005-04-06 14:52           ` Hollis Blanchard
2005-04-06 15:43             ` Antoine Terrienne
2005-04-07  0:02               ` Hollis Blanchard
2005-04-07 14:17                 ` Yoshinori K. Okuji
2005-04-07 14:37                   ` Marco Gerards [this message]
2005-04-07 16:46                     ` Yoshinori K. Okuji
2005-04-08  6:39                       ` Marco Gerards
2005-04-12 10:15                         ` Yoshinori K. Okuji
2005-04-12 11:13                           ` Marco Gerards
2005-04-14  3:46                         ` Hollis Blanchard
2005-04-14 12:15                           ` Yoshinori K. Okuji
2005-04-14 16:30                             ` Marco Gerards
2005-04-05  7:00 ` partition layouts Marco Gerards
2005-04-05 15:38   ` partition layouts - symlinks Hollis Blanchard
2005-04-05  7:58 ` partition layouts Tomas 'Ebik' Ebenlendr

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=87oecqfyac.fsf@student.han.nl \
    --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.