It could be entirely commented out, many stock slackware config files are installed this way.

Yeah I would say it should include less software it's fun finding and compiling my own software and too much of a pain deleting all the stuff I don't want or doing a custom install

What bugs me about Slackware are all the people who whine about what bugs them in Slackware.

Its one thing to report a bug, problem, etc., or to suggest an improvement, but quite another to complain about PV's and teh Slackware team's choice of configuration defaults. No rc.firewall? bah! I prefer my routers. No bootsplash? You have got to be f***ing crazy.

A quick scan of distrowatch provides a plethora of choices. Go.

Hey, what's the name of the thread again? 'Things you don't like about Slackware', not 'Things you demand to be changed in Slackware'.

Let me tell you, I've been using Slackware since 12.0 and have never even tried another distro since then. Love the BSD-style init, love the solid selection of 'base' software, love the absence of 'dependency-hell', love the slackbuild.org community. But that doesn't mean I am not allowed to dislike a couple of settings, even if I know it's possible to change them easily.

I don't like the fact that the kernel timer now has a 1000hz frequency. Overkill for laptops, and it's been known to give me singing capacitors.

I don't like when -current goes longer than 4 days without an update....

cheers,

Sorry I didn't see your reply. Here are my reasons: Every time I select an entry lilo takes a long time till the system starts loading, the part with that growing line of dots. I don't know what the heck it's doing all that time, grub jumps right to business.

I also can't stand the fact that you cannot edit a lilo entry from lilo itself, contrary than grub. Being able to change the kernel version or the runlevel can be very useful, somtimes lifesaving.

Sure, lilo works. Grub is faster, more powerful and flexible, hence: clearly superiour.

(For the record: I'm talking about grub legacy. grub 2 kind of sucks )

-A

Install lilo in compact mode. Problem solved.

I don't know,...


I don't know,...


I don't like about Slackware being so much better than the other dsitros,
sometime it just sucks naming all the benefits (and so many) when explaining why not use that other distro...

Maybe if it where less best one there is?

Stevan C.
P.S.
Yes I'm kidding ...

It's just too good

I just noticed that I had missed this part.
You can't change the kernel version in lilo, but you can certainly pass extra kernel options and/or specify the runlevel on boot.

I would love to see inkscape and blender adopted to slackvare/extra
and avidemux, for that matter, but that's less probable.
At least mplayer is back besides xine.
I always missed on the desktop/office productivity koffice just fails short to deliver?

And, here's another thing: During install there is no checking if the DVD is corrupt. It should at least be an option. Like someone mention in another thread Fedora does this by default, which is a good idea. There have been many threads here that were either asking how to check the md5sum or problems cause by a bad disk burn. Maybe an option like this would be a good idea. I'm sure it can't be that hard to implement, the package md5sums are already on the disk.

1 members found this post helpful.

It would be nice if the Slackware DVD supported CPU frequency scaling...unless I missed something there is no powernow-k8 module available on the install CD/DVD (and of course other modules would be necessary for other CPUs...). I was using the install CD as a rescue disk to copy files from a Windows PC across the network but it kept overheating and crashing (stupid HP). I ended up having to resort to plop on a USB disk, which can do CPU scaling. Though not the original intention of the Slackware install CD I can definitely see some laptops (including that HP space heater) dying during package installation from overheating. It would probably have lasted long enough (assuming it starts cold) to install the a/ series and then reboot into the system to enable the ondemand governor and finish package installation...but I definitely don't think it would have lasted long enough to get through a full install.

That perl (for the debugger, perl -d script.pl) had the Readline stuff already installed.