From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Status of GRUB / GRUB2?
Date: Wed, 21 Jul 2004 15:44:25 +0200 [thread overview]
Message-ID: <200407211544.25663.okuji@enbug.org> (raw)
In-Reply-To: <FJENINNJFNDFNAAOMDGIIEELCAAA.solar@rootdirectory.de>
On Wednesday 21 July 2004 06:13, Martin Baute wrote:
> How can there be a GRUB *2* if there never was a GRUB *1*
> to speak of? I'd expect at least a 1.0 file release - however
> incomplete and inferor that version might feel for you - that
> people can use and rely upon until that GRUB 2 materializes.
Since Macro answered other questions, I reply only to this question.
1.0 will never be released. This is because GRUB Legacy has missing
features to be 1.0 but it is not worth developing any further. So we do
only bugfixes and beta releases. IMHO, it is much more efficient to
create a better boot loader (i.e. GRUB 2).
I know some people worry about version numbers too much. But what do you
get from version numbers really? Nothing. That's why GRUB Legacy is
used widely by many people and vendors, although the version is the
horrible "0.9x". GRUB Legacy is not released publicly yet. So what?
Most people do not care about version numbers anyway. They just care
about if the software is really usable or not.
For me, version numbers are just like "date + compatibility
information". If the major version is different, it means that
compatibility is not perfect. If the minor version is different, it
means that it's released at a different time.
Okuji
prev parent reply other threads:[~2004-07-21 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 4:13 Status of GRUB / GRUB2? Martin Baute
2004-07-21 12:24 ` Marco Gerards
2004-07-22 19:44 ` Tomas Ebenlendr
2004-07-21 13:44 ` Yoshinori K. Okuji [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=200407211544.25663.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.