Neil Bothwick wrote:
On Tue, 11 Jan 2011 16:46:43 -0600, Dale wrote:
What is there to do with it? It's a bootloader that boots and loads,
what more do you want?
No longer updated can mean broken, but it can also mean finished.
My point was, if something changes and it no longer works, then we may
all have to switch. According to the website, nothing much is being
done with the old grub.
What can change? We are stuck with a hardware spec from 30 years ago for
booting. That won't change any time soon.
File systems for one. They do make new ones every once in a while. '
I want to wait until either the old grub doesn't work for me or the new
grub is known to be stable and has got all the kinks worked out. Even
then, I may wait until I have a issue or the old grub leaves the tree.
I seem to recall hal was stable and worked for most people too. It
just didn't work here for me.
That's completely different. HAL had to deal with varying hardware and
varying requirement of the software that wanted to interface with that
hardware.
OK. Hal has to deal with different hardware. Doesn't grub work on
different hardware too? All computers are not the same. We also don't
know what will be out in a few years either.
When is the last time a package was finished never to be changed
again? I have never seen that from any program. There is always
something new, some better way to do things or just some little tweak
to improve things.
Maybe there are, and if that's what you want you can use GRUB2, but
legacy GRUB won't stop working as long as we are using the BIOS to boot
from disk-like devices.
I don't want to use grub2. As I said, I'll switch when I know it is
safe to do so or when the old grub stops working, whichever comes first.
Grub does have to work with the BIOS but there is more to it than that.
It has to work with the file systems too. There could be other things
that pop up and need fixing too.
Dale
:-) :-)
