This has to be bogus. How is it even possible that someone actually capable of installing and running Linux From Scratch AND has run "good ol' Slack 9" doesn't even realize that Slackware is not responsible for Lilo (or Grub) AND that it still has zero problems booting from any drive any partition? This is only one of the glaring discrepancies..

Oh Wait... that's right. He's a forking troll!

Plonk!

How to cook a troll

I wonder if using AlienBob's Recipe will help flavor this one.

Needing to get out of the house more is not a problem unique to Canada .

Well, speaking from the point of view of another Canadian on this forum I would like to mention that we are not all as intense as the OP. Many kudos to Alien Bob for his thoughtful, articulate reply.
Best wishes to the OP as he forks around with LFS.

If you think Slackware is being weird, wait until you really see what is happening around. Perhaps soon they'll try to force 'systemd'...

Sorry for your upgrade... Recently I replaced an old ISA server for Slackware current. Without services/daemons, the box is booting with ~nine MiB of RAM. Nowadays serving Slack/Windoze clients with filtered proxy and basic Samba. It is booting from the second hard drive until I think it is time to kill the other server and format the disk to Squid. Two small five gigs. disks, and Slack only take one (almost half empty).

I can't compare the similarities between Slackware and the other OS, because there are none, but I must admit: Slack seems the best replacement for XP/2K clients and NT/2K/2K3 servers around (go Russia =]).

Another machine running Slackware current went with minimal 'x' and, even slow, compiz made the show without trouble. It's running ratpoison right now and is my dream seed box. Just love that old piece of hardware. With initial 12 MiB of RAM, the rig is sucking torrents and streaming video/music (thanks Alien).

Uptime is being short this days after some recent updates. The first test ended with eleven days serving the 'internets' for my old new server =]

Two desktops are running current with all the eye candy GNU/Linux can supply. Just stable, fast and beauty machines...

Still the king Slackware is!

1 members found this post helpful.

If you are used to Slackware, then nomatter how many distros you try you WILL go back to slack.
I think its a law of nature or something.

I've seen nothing but improvements in Slackware, with the notable exception that KDE 4 has introduced some problems. So far as booting is concerned, I have been booting Slackware from any disk or partition including fake RAID since version 10. I use Slackware because it is very well maintained and flexible. You get out of Slackware what you put into it. If you aren't willing to work through a few problems then it's probably not the distro for you. There are plenty of cookie-cutter GNOME distros that will (usually) install and run, giving you no choices about what you get nor any understanding of how Linux works.

I've had my frustrations with Linux, but other Slackers always help, including people like Alien Bob, who spend time proactively making things easier and better. I'd much rather know how to solve a few problems than to be completely ignorant about the operating system that I'm using. A good craftsman understands the tools that they use and how to sharpen them.

Some Linux complaints should rightly be directed at the hardware developers who still halfheartedly support Linux or don't support it at all. Graphics card manufacturers haven't done a good job of keeping Linux features up to date with their hardware. Fake RAID controller manufacturers have not kept their drivers up to date with changes in distros and often completely ignored support for legacy products. Some companies still pretend that SUSE and REDHAT are the only Linux distros in existence.

I do hope to see another Slackware release soon. A lot of packages that go into Slackware have been improved since 13.1 and some of those will make a big difference in my system configuration. I am using Slackware current so that I can enjoy the benefits now without waiting for the next release. In the past I have preferred to install the released versions without installing updates from the current versions. Thanks to everyone who contributes to Slackware.

3 members found this post helpful.

Guys,don't feed the troll!!!
It's only a pointless flame,let's go on.

Well nobody said anything for a day until you arrived and wrote your post...

Eric

Is this guy really distro maintainer grade?

I'm not, and I know how to install Slack to any partition on my hard drives.

Also as a Canadian, Slackware is the best I have ever found for an os. Stable beyond stable, 32 and 64b. I have built water cooled overclocked rigs for gaming since getting into computers around the pIII 500mhz cpu and with linux since fedora5 and tried most of linux os till finding slackware 13. I still need a windoz install for most games but use Slack as my daily system.

I have only one problem, same as OP that I can only ever boot Slack when installed on the primary master drive. I can put more then one slack install on that drive no problem but when installing it to a secondary drive I always get a kernel panic even if its the only os on that drive.

Well, I'm in Canada, I've got no problems running Slackware 13.1 on various boxes.

From fileserver (sempron), firewall/router (atom as well as on two Pentium III's), desktop (Phenom II), laptop (Core2) and a bunch of Pentium 4 desktops...

Despite reading the OP's post twice, I don't really understand why he is having so many problems (or hatred).

Wait a minute! About what version we talk? And, how you can reproduce this bug?

Also, to understand that this bug occurs during installation? Then, there is a bug in installer.

All you have to do is map the secondary drive in lilo to make it think its the primary drive. Here's a sample - change it to match your system:

Its been awhile since I used a secondary drive, but I think that's correct.