damNageHack wrote:Initrd is not for newbies

Yes, I see. Nowadays the very first thing I do after installation is changing to the generic kernel. I always keep the boot entry for the huge kernel on lilo for backup, if anything goes wrong with the initrd. Learned the hard way, AKA the kernel panic path.

thenktor wrote:

damNageHack wrote:Why need a screensaver at all nowadays?

++

Screensavers suck!

Well, they are fun, aren't they?

Those who have never fooled around AfterDark may throw the first stone!

Aren't those messages gone when you make an initrd and boot the generic kernel instead?

First reaction of non-tech people who take a look at Salix:

"What a pretty wallpaper!"

I'm not joking, I swear! Everybody both at home and at work loved the artwork.

I noticed two python packages that should be included on the installation CD, notify-python and pyxdg. Main reasons for inclusion: Catfish can benefit from pyxdg at run-time. Wicd-gtk can benefit from notify-python at run-time. Parole can benefit from notify-python (build-time notification plugin) a...

This is actually the very first time I see someone who prefers gnome-screensaver over xscreensaver, I remember some 4-5 years ago when I was using Ubuntu that the thing most people complained about was "why not stick with xscreensaver?"

antmon wrote:I guess there isn't that many guys using Salix!

I installed Salix in 3 or 4 boxes in a office room this week. By now there should be at least 10+ people using it.

I was played around with plymouth on Slackware 13.1 once, I didn't touch my initrd but I guess you don't need to if you have a KMS-found video card, since I was able to get a pseudo-bootsplash on console with #plymouth --show-splash. If you call plymouth correctly after the rc.udev start call in rc....