From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Replacing the legacy "map" command
Date: Thu, 29 May 2008 20:55:05 -0400 [thread overview]
Message-ID: <1212108905.4265.59.camel@dv> (raw)
In-Reply-To: <20080528142438.GK26495@thorin>
On Wed, 2008-05-28 at 16:24 +0200, Robert Millan wrote:
> On Tue, May 27, 2008 at 11:59:22AM -0400, Pavel Roskin wrote:
> >
> > Again, I'd like to see the command name shortened, perhaps to "drivemap"
> > or "map". It's not like users will need to distinguish BIOS and
> > non-BIOS mappings.
>
> But then we're occupping generic namespace with arch-specific features.
I think it's OK. If another architecture supports similar
functionality, then "drivemap" would still be fine, even if the
implementation is different. If an architecture doesn't support it, the
command won't exist.
It's very unlikely that there will be two different mechanisms for drive
remapping, each of which should be available to the users. And even
then, a switch could be added to force the preferred mechanism.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-30 0:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 1:36 Replacing the legacy "map" command Javier Martín
2008-05-27 15:59 ` Pavel Roskin
2008-05-27 16:15 ` Urja Rannikko
2008-05-28 14:24 ` Robert Millan
2008-05-30 0:55 ` Pavel Roskin [this message]
2008-05-30 2:13 ` Javier Martín
2008-05-30 3:48 ` Pavel Roskin
2008-05-30 7:19 ` Robert Millan
[not found] ` <-5961521231976305315@unknownmsgid>
2008-05-31 23:15 ` Javier Martín
2008-06-01 7:18 ` Vesa Jääskeläinen
2008-05-27 16:04 ` Vesa Jääskeläinen
2008-05-27 16:18 ` Urja Rannikko
[not found] <483c317b.0c1e640a.2bd9.7c7eSMTPIN_ADDED@mx.google.com>
2008-05-27 21:47 ` Javier Martín
2008-05-28 0:19 ` Replacing the legacy 'map' command Tomáš Ebenlendr
-- strict thread matches above, loose matches on Subject: below --
2008-05-28 13:17 Javier Martín
2008-05-28 16:23 ` Vesa Jääskeläinen
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=1212108905.4265.59.camel@dv \
--to=proski@gnu.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.