Linked by Thom Holwerda on Fri 15th Jun 2007 22:13 UTC, submitted by lost
Slackware, Slax Patrick J. Volkerding announced the first release candidate of Slackware 12 in the current changelog. This will be the first Slackware release with a kernel from the 2.6 tree (2.6.21.5) as default. "It's that time again, and here we have Slackware 12.0 release candidate 1! If we're lucky, we got it all right the first time. Big thanks to the crew."
Thread beginning with comment 248445
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: lilo
by shapeshifter on Sat 16th Jun 2007 21:44 UTC in reply to "lilo"
shapeshifter
Member since:
2006-09-19

Last time I checked Grub didn't support a lot of filesystems, like XFS, so if you wanted to use one of those you had to install Lilo.
Debian 4 is same way, it'll install Grub for you by default, but if you choose XFS as your main file system then it'll install Lilo.

Reply Parent Score: 1

RE[2]: lilo
by psychicist on Sun 17th Jun 2007 10:30 in reply to "RE: lilo"
psychicist Member since:
2007-01-27

Last time I checked Grub didn't support a lot of filesystems, like XFS, so if you wanted to use one of those you had to install Lilo. Debian 4 is same way, it'll install Grub for you by default, but if you choose XFS as your main file system then it'll install Lilo.


I have been using both GRUB and XFS for years so it should really not be a problem. The trick is to make a separate (/boot) ext3 partition where GRUB resides. GRUB can't coexist with XFS on the same partition so you shouldn't even try.

As a matter of fact the way I install GRUB on a partition of itself it's a completely separate entity from the installed operating system(s) and it isn't mounted anywhere in any of them by default.
So I never install GRUB or LILO when installing Slackware. I don't even bother with CD/DVD installs anymore, just installing from the hard disk, which is both faster and less error-prone.

Also I hardly ever upgrade the bootloader unless there is a major advantage to doing so and just update menu.lst to point to the newer kernel on the Slackware partition, which is usually just a version number change.

Of course it helps that I have created and installed self-contained rescue images (30-90 MB) that can be run from this separate boot partition in case I misconfigure GRUB. And modern firmwares such as PMON and OpenFirmware, which combine the functionality of the BIOS and GRUB, let you directly boot kernels anyway on non-x86 architectures.

Edited 2007-06-17 10:31 UTC

Reply Parent Score: 2