On Friday 18 September 2009 13:52, someone identifying as *Nico
Kadel-Garcia* wrote in /comp.os.linux.setup:/

On Sep 18, 6:43 am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:

There are of course reasons as to why you might prefer GRUB over
LILO. For one, GRUB offers more possibilities - such as an
interactive boot shell and the ability to load many other types of
UNIX operating systems, including GNU/Hurd, Free-/Net-/OpenBSD and
Solaris - and if you're going to use the Xen hypervisor, then using
LILO requires some special trick to get Xen to load the privileged
domain's kernel, because LILO does not support module loading, while
GRUB does.

Still, somehow I don't think that would be an issue in your case, so
if you want to have /ext4/ on the */boot* partition and you can't
install any of the later GRUB versions, try going with LILO instead.
It's not as featureful as GRUB but it'll do the job of booting up
your system.
I'm glad Aragorn is around. He gives good answers, that I can
occasionally add a bit of extra thought to.

Why thank you, I really appreciate that.
#

On Sep 18, 8:07 am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:

It was once postulated by chaoticians that a million monkeys sitting at
a computer would eventually come up with the collected works of William
Shakespeare. Now, with the internet, we know that this is not true. :p

Now, now, be nice to the cage monkeys. I'm restraining a lot of odd
humor about them at the moment, but they've usually done their flat-
out best for me when I've called and I appreciate their on-site hands
and configuration insights tremendously.

grub lacks one feature I really miss from LILO, the command line "use
the old kernel still there as the default", then "use the new kernel
one time and one time only to reboot with". (You had to do them on
different commands, on the same command didn't work, dang it!!!) This
let you reboot once with the new kernel, and if it failed, the boot
procedure would revert to the old kernel merely by someone hitting the
power button. That was incredibly helpful when testing out new kernels
or sending new kernels to weird, remote hardware: having a cage monkey
hit the power button is much safer than making them connect up a
keyboard and console.

If it's there, it's relatively new: I've had to work with RHEL 4 and
RHEL 5 the last few years, and it certainly wasn't there.

On Sep 18, 8:07=A0am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:

It was once postulated by chaoticians that a million monkeys sitting at
a computer would eventually come up with the collected works of William
Shakespeare. =A0Now, with the internet, we know that this is not true. :p

On Sep 18, 8:07=A0am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:
It was once postulated by chaoticians that a million monkeys sitting at
a computer would eventually come up with the collected works of William
Shakespeare. =A0Now, with the internet, we know that this is not true. :p

Nope. they gave us Wikipedia instead.

ITYM facebook.

unruh wrote:
On Sep 18, 8:07=A0am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:
It was once postulated by chaoticians that a million monkeys sitting at
a computer would eventually come up with the collected works of William
Shakespeare. =A0Now, with the internet, we know that this is not true. :p

Nope. they gave us Wikipedia instead.

ITYM facebook.

Aragorn wrote:

On Friday 18 September 2009 13:52, someone identifying as *Nico
Kadel-Garcia* wrote in /comp.os.linux.setup:/

On Sep 18, 6:43 am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:

There are of course reasons as to why you might prefer GRUB over
LILO. For one, GRUB offers more possibilities - such as an
interactive boot shell and the ability to load many other types of
UNIX operating systems, including GNU/Hurd, Free-/Net-/OpenBSD and
Solaris - and if you're going to use the Xen hypervisor, then using
LILO requires some special trick to get Xen to load the privileged
domain's kernel, because LILO does not support module loading,
while GRUB does.

Still, somehow I don't think that would be an issue in your case,
so if you want to have /ext4/ on the */boot* partition and you
can't install any of the later GRUB versions, try going with LILO
instead. It's not as featureful as GRUB but it'll do the job of
booting up your system. ;-)

I'm glad Aragorn is around. He gives good answers, that I can
occasionally add a bit of extra thought to.

Why thank you, I really appreciate that.
#

well add my welcome too, as I appreciate your style and knowledge.

On Sep 18, 8:07=A0am, Aragorn <arag... at (no spam) chatfactory.invalid> wrote:

It was once postulated by chaoticians that a million monkeys sitting
at a computer would eventually come up with the collected works of
William Shakespeare. =A0Now, with the internet, we know that this is
not true. :p

Nope. they gave us Wikipedia instead.

Since GRUB can boot e.g. Windows systems as well - isn't there a GRUB
option, that a logical drive shall be booted in the "traditional"
(LILO) way?

I'm not sure I understand your question... :-/ Both GRUB and LILO boot
Windows in the same manner, i.e. by loading the Windows partition's
bootsector into memory and passing control of the machine onto whatever
code resides there, and this code in question would then be the Windows
bootloader.

As your question was pretty vague, I'm not sure whether my reply is
adequate, though.

Aragorn schrieb:

Since GRUB can boot e.g. Windows systems as well - isn't there a GRUB
option, that a logical drive shall be booted in the "traditional"
(LILO) way?

I'm not sure I understand your question... :-/ Both GRUB and LILO boot
Windows in the same manner, i.e. by loading the Windows partition's
bootsector into memory and passing control of the machine onto whatever
code resides there, and this code in question would then be the Windows
bootloader.

I'm not sure how far this is a Windows specific convention - at least
the first boot stage must be invoked by the BIOS.

[...]
As your question was pretty vague, I'm not sure whether my reply is
adequate, though.

Thanks, I think that I could figure out some facts :-)

It looks to me as if Linux prefers an single boot manager, not one for
every bootable logical drive. What's the problem with updating that boot
manager, when a new filesystem is used for an bootable drive?
#

Hans-Peter Diettrich wrote:

Aragorn schrieb:

Since GRUB can boot e.g. Windows systems as well - isn't there a
GRUB option, that a logical drive shall be booted in the
"traditional" (LILO) way?

I'm not sure I understand your question... :-/ Both GRUB and LILO
boot Windows in the same manner, i.e. by loading the Windows
partition's bootsector into memory and passing control of the
machine onto whatever code resides there, and this code in question
would then be the Windows bootloader.

I'm not sure how far this is a Windows specific convention - at least
the first boot stage must be invoked by the BIOS.

yerrss.. I thought about that, but the boot LOADER - grub, lilo or
whatever, simply resides in the boot SECTOR, which isn't really a file
*system* at all.

So teh sequence is

Bios loads boot sector and jumps to execute into it.
Boot code takes over and loads splash screens and ultimately the
kernel and enough OS to bootstrap the rest.

So its really down to whether or not the boot loader understands the
disk .. and sometimes it dont..and booting fails!

As your question was pretty vague, I'm not sure whether my reply is
adequate, though.

Thanks, I think that I could figure out some facts :-)

It looks to me as if Linux prefers an single boot manager, not one
for every bootable logical drive. What's the problem with updating
that boot manager, when a new filesystem is used for an bootable
drive?
#

Dont see any really.

Newbie question.

Newbie question.