You know, I always thought it said Boo Boo, and not Ubu. Guess I never noticed the Ubu Productions overlay
http://en.wikipedia.org/wiki/Ubu_Productions

Let me be even more clear. I'm not championing Arch over Slackware. I like Slackware. I made one reference to Arch, which was in fact expressing the exact same sentiment, that people like different things. I was asked a question and I explained myself. So please, everyone, chill out. This isn't a clubhouse and you don't need to keep out the other kids and their cooties. Nor is this a binary world, despite being about computers and operating systems. It shouldn't be "I'm an Archer" or "I'm a Slacker".

If you plan to install Slackware alongside Vista and Ubuntu, I would also recommend to not install lilo, and just boot Slackware with the grub from Ubuntu. This is what I do.
If you are using Ubuntu 9.10, an important thing to remember is that 9.10 uses grub2. Normally, if you install another distro and want to use grub2 to boot that distro, you should be able to just boot up Ubuntu and run:
and this will update the /boot/grub/grub.cfg file to add that distro to the grub list. However, when I installed Slackware 13 32bit, running update-grub would not add the initrd line to the entry in grub.cfg for the Slackware generic kernel for some reason. This prevents booting from the generic kernel. For Slackware 13 64bit, update-grub did not even detect the 64bit Slackware for some reason.
The solution to all of this was to add custom entries for booting Slackware in the /etc/grub.d/ directory, and then run "sudo update-grub so that grub2 would then add my custom entries to the grub.cfg file. See this tutorial on grub2:
https://wiki.ubuntu.com/Grub2
and specifically, the part about adding custom entries:
https://wiki.ubuntu.com/Grub2#User-defined%20Entries
I just wanted to point this out in case you have problems booting Slackware from Ubuntu's grub.

If you plan to replace Ubuntu with Slackware, then I would just use Slackware's lilo to dual boot Slackware and Vista.

1 members found this post helpful.

Tommcd, Thanks so much! Lets suppose I change nothing in Grub2,(simply installing Slackware with Lilo), will lilo at least recognize my Vista? And would there be any way to get into Ubuntu? (even with a little effort?)

Lilo can be installed and yes those things are possible, but I found Grub to be an easier ride.

Another Slacker! Praise Bob!

Lilo should see vista
As I recall, the automatic lilo install from the slack disk will automatically recognize the windows partition. However I am not sure it will recognize the ubuntu partition.

Based on reviewing this link, it appears that ubuntu 9.1 should load with lilo. Unlike debian lenny in a earlier post.

If you install lilo and for some reason only see slackware in the lilo splash screen, it is relatively easy to edit lilo to boot both vista and ubuntu

Another epic thread would be: http://bbs.archlinux.org/viewtopic.php?id=91812

I have not used lilo much since I have mostly always booted with grub. If you wanted to use lilo, I would think the best method would be to let Slackware install lilo to the MBR. Then isntall Ubuntu's grub2 to the Ubutnu root partition. Then chainload Ubuntu like it says in post #4 in this thread:
http://www.linuxquestions.org/questi...ubuntu-613632/
As Damgar said, I think it would just be easier to use grub. Just choose not to install lilo when you install Slackware.

Lol that's nothing check this out:
http://bbs.archlinux.org/viewtopic.php?id=91727

My point was that today in Linux every user logged in through a display manager is granted with permission to do anything he pleases...

I don't care about your point,just wanted to share that ridiculously epic thread! You ain't gonna troll me no more!

Not on my box they ain't. Hell, I don't even give myself permission to do somethings.

Hey Bradford,

Welcome to Slackware, man! Let us know if we can help.

This is sums up my personal experience with different Linux distributions over more than nine years: Slackware requires less maintenance.

Regarding the OP's initial question, most relevant aspects have been mentioned. I just would like to add:

Package management with automated dependency resolution always relies on information that the respective package maintainer has added to his package, based on his very own, personal experience and quality assured in their own environment. If the package maintainer did a good job, the package management tool can make things comfortable. If the package maintainer overlooked something, that's relevant in your particular environment, it will either not work, add things you actually don't need to your system, or even screw up something in your system.
Several years ago, I friend of mine installed Debian on his desktop, switching from Gentoo. He wanted to install Gnumeric and Gnucash, and ended up with a complete Gnome desktop --- which he never wanted to have.
I have to say, that I had been using SuSE Linux for many years, and that I never really ran into dependency hell. But I as this is one of the most comprehensive distros on the market I didn't have the requirement to add a lot of software after the initial install.

But overall, I can say, that of all distros I know, Slackware requires the least enduser maintenance, despite or because it avoids complex automatisms.

And I don't know another distro that is so well maintained and so consistent over so many releases. If a slackware version is released as table you can just depend on the highest quality assurance in the Linux world. This relatively small crew of people, who develops Slackware, coordinated by Patrick Volkerding, somehow manages to produce the most consistent distro there is, every time. An upgrade has NEVER been a risk. This is "conservative" in the very best sense!

Given the resources of manpower and money of some of the other players, this deserves nothing, but respect and admiration.

gargamel

2 members found this post helpful.