From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Status of GRUB / GRUB2?
Date: Wed, 21 Jul 2004 14:24:59 +0200 [thread overview]
Message-ID: <877jsx7dk4.fsf@marco.marco-g.com> (raw)
In-Reply-To: <FJENINNJFNDFNAAOMDGIIEELCAAA.solar@rootdirectory.de> (Martin Baute's message of "Wed, 21 Jul 2004 06:13:59 +0200")
"Martin Baute" <solar@rootdirectory.de> writes:
> I submitted this as bug #9640 last week, but it seems
> the bug tracker isn't that well maintained, so I'll
> try the mailing list now.
We don't use the bug tracker for GRUB 2.
> The website is very hazy on the following (crucial, IMHO)
> points:
>
> * will GRUB2 still be Multiboot compliant? Will existing
> self-written kernels have to adapt to GRUB2?
It will be. At the moment it is not yet fully multiboot complaint.
> * how far away is GRUB2? What is yet to be done? Any roadmap?
Things change dayly. Just have a look at CVS and this mailinglist.
Currently a lot needs to be done.
> That being said, you still have GRUB dangling at 0.9x, "not
> been released publically", and yet being discontinued for
> some "GRUB 2" that might be years off for all we (casual
> visitors of your website) would know.
Why is that a problem? GRUB Legacy bugs will be fixed, etc. There
won't be any problem. Just because something better will be written
is no reason not to use GRUB Legacy at the moment.
--
Marco
next prev parent reply other threads:[~2004-07-21 12:37 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 [this message]
2004-07-22 19:44 ` Tomas Ebenlendr
2004-07-21 13:44 ` Yoshinori K. Okuji
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=877jsx7dk4.fsf@marco.marco-g.com \
--to=metgerards@student.han.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.