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: normal vs. rescue mode commands
Date: Thu, 10 Jun 2004 13:51:32 +0200	[thread overview]
Message-ID: <200406101351.32692.okuji@enbug.org> (raw)
In-Reply-To: <87y8mwkcz0.wl@pc-jeroen.dekkers.cx>

On Wednesday 09 June 2004 16:44, Jeroen Dekkers wrote:
> The European Parliament voted against software patents last
> time. There is a good chance they will do it next time too.

Maybe. It depends on the coming election.

> Yes, but still I don't think that we should obfuscate the module
> names. Multiboot is already 9 letters, for example.

Why are abbreviations so bad? In fact, we use "mb" as an abbreviation of 
multiboot in GRUB Legacy, but there is no problem with this.

I agree that abbreviations should be avoided for ordinary users. But the 
filenames of modules are not for ordinary users. They should be used 
only by those who know how GRUB works more or less.

The advantage of abbreviations: GRUB is compatible with all filesystems, 
including popular ones (e.g. FAT, ISO9660, MinixFS, HFS).

The disadvantage of them: Sometimes filenames do not tell you what they 
are clearly.

For me, the advantage looks much more important, since the disadvantage 
can be overcome with a good documentation.

> > All the essential files fit:
> >
> > stage1 -> 5 + 0
> > stage2 -> 5 + 0
> > menu.lst -> 4 + 3
>
> Yes, but stage1.5 files don't.

So?

Okuji




  reply	other threads:[~2004-06-10 11:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 12:17 ext2 find patch Tomas Ebenlendr
2004-06-01 20:13 ` Tomas Ebenlendr
2004-06-01 20:47   ` Marco Gerards
2004-06-01 21:09     ` Jeroen Dekkers
     [not found]     ` <20040602100915.GA1629@artax.karlin.mff.cuni.cz>
     [not found]       ` <1086176188.40bdbbbc4d86d@webmail.han.nl>
2004-06-02 14:43         ` normal vs. rescue mode commands Tomas Ebenlendr
2004-06-02 15:11           ` Tomas Ebenlendr
2004-06-02 16:10             ` Marco Gerards
2004-06-03 11:12               ` Yoshinori K. Okuji
2004-06-03 11:55                 ` M. Gerards
2004-06-03 12:50                 ` Tomas Ebenlendr
2004-06-04 11:24                   ` Yoshinori K. Okuji
2004-06-06 10:55                     ` Tomas Ebenlendr
2004-06-09 11:19                       ` Yoshinori K. Okuji
2004-06-09 12:07                         ` Jeroen Dekkers
2004-06-09 12:25                           ` Yoshinori K. Okuji
2004-06-09 12:48                             ` Jeroen Dekkers
2004-06-09 13:12                               ` Yoshinori K. Okuji
2004-06-09 13:54                                 ` Jeroen Dekkers
2004-06-09 14:22                                   ` Yoshinori K. Okuji
2004-06-09 14:44                                     ` Jeroen Dekkers
2004-06-10 11:51                                       ` Yoshinori K. Okuji [this message]
2004-06-09 12:28                         ` Tomas Ebenlendr
2004-06-09 12:31                           ` Tomas Ebenlendr
2004-06-03 11:08           ` Yoshinori K. Okuji
2004-06-27 10:45   ` ext2 find patch 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=200406101351.32692.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.