All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix file name transformations (mostly)
Date: Thu, 17 Apr 2008 22:07:11 +0200	[thread overview]
Message-ID: <20080417200711.GA13794@thorin> (raw)
In-Reply-To: <1208460029.27241.32.camel@dv>

On Thu, Apr 17, 2008 at 03:20:29PM -0400, Pavel Roskin wrote:
> On Thu, 2008-04-17 at 13:49 +0200, Lubomir Kundrak wrote:
> 
> > > As for /boot/grub, we are not installing anything there on "make
> > > install".  I don't think it should be transformed.  But we could accept
> > > a configuration option to change that directory.
> > 
> > We should have a sensible default that wouldn't clash with GRUB Legacy's
> > default.
> 
> There is no clash here.  Names of all files under /boot/grub are
> different, except device.map.  But device.map has the same format and is
> system specific.

Lubomir, if you're worried about making GRUB 2 and Legacy coexist, I can
confirm you it's perfectly possible using the same directory.  In Debian we
do that in fact (I only had to fix grub-install removing menu.lst, but that's
all).

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-04-17 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 22:12 [PATCH] Fix file name transformations (mostly) Lubomir Kundrak
2008-04-15 13:33 ` Robert Millan
2008-04-17 11:47   ` Lubomir Kundrak
2008-04-15 19:19 ` Pavel Roskin
2008-04-17 11:49   ` Lubomir Kundrak
2008-04-17 19:20     ` Pavel Roskin
2008-04-17 20:07       ` Robert Millan [this message]
2008-04-18  6:41       ` Lubomir Kundrak

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=20080417200711.GA13794@thorin \
    --to=rmh@aybabtu.com \
    --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.