All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] rename "grubof" to "grub"
Date: Tue, 02 May 2006 19:49:19 +0200	[thread overview]
Message-ID: <87irooqpuo.fsf@xs4all.nl> (raw)
In-Reply-To: <e72d2ce1aa9d2226f12fa6cd98b49711@penguinppc.org> (Hollis Blanchard's message of "Tue, 25 Apr 2006 19:37:14 -0500")

Hollis Blanchard <hollis@penguinppc.org> writes:

> On Apr 21, 2006, at 4:15 AM, Marco Gerards wrote:
>
>> Hollis Blanchard <hollis@penguinppc.org> writes:
>>
>>> This patch renames "grubof", the executable name for PPC and Sparc, to
>>> "grub". I'm still not sure what the naming convention should be for
>>> the executable output by grub-mkimage; I'm thinking maybe
>>> "grub.ppc". It isn't an image ("grub.img"); it's still an ELF file...
>>
>> Personally I would prefer something like `_grub' so people see there
>> is something special about it and just don't use it like that.  After
>> that the output file can just be called grub if people want that.
>
> What about "grubkernel" and "grub"? Or "grub.raw" and "grub"? I'd like
> to try to stay within 8.3 naming for all files, since people will be
> deploying the end result on FAT filesystems.

_grub works on fat.  We use an underscore for the rescue mode
chainloader on the PC as well.  Personally I prefer something like
this or another obscure name that scares people. :-)

--
Marco




      parent reply	other threads:[~2006-05-02 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  3:23 [patch] rename "grubof" to "grub" Hollis Blanchard
2006-04-21  9:15 ` Marco Gerards
2006-04-26  0:37   ` Hollis Blanchard
2006-04-27  8:49     ` Roger Leigh
2006-04-27  9:16       ` Stefan Reinauer
2006-04-27 10:26         ` Marco Gerards
2006-05-02 17:49     ` Marco Gerards [this message]

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=87irooqpuo.fsf@xs4all.nl \
    --to=mgerards@xs4all.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.