Linked by Eugenia Loli on Mon 9th May 2005 18:38 UTC, submitted by Robert Burns
Slackware, Slax "I have very mixed feelings about this release of Slackware. I do not think that the underlying philosophy of Slackware is obsolete. The concept of a system that can be configured and molded to the n'th degree is still in my opinion very much a good idea. However, this release of Slackware is not without its problems in execution." Read the review here.
Permalink for comment
To read all comments associated with this story, please click here.
RE: Slackware is the distro of the past
by ex-slacker on Tue 10th May 2005 14:02 UTC


Besides that the simplicity of Slackware packages is very comfortable, in the end it is just a tarball that sometimes contains one additional post-install script

Have you ever tried Arch Linux? The same situation is with Arch packages. They are just tarballs that sometimes contain one additional post-install script. Basically it's the same KISS philosophy as in Slackware, BUT pacman manage wisely dependencies. and if you really do not want to install dependencies it's as simpe as adding --nodeps to pacman command. NOONE will tell me that Slackware package management system is better than Arch's pacman. Basically pacman is "pkgtool improved". And package database is kept in simple text files, as in Slack. Some of you guys are just funny, you keep preaching to yourself that candle is still the best light source out there, when some people improved on it and discovered a light bulb.

@Father Baker
Let me tell you something. Try Arch first and then speak, all right?

this is a part of rc.conf
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond gpm)

How is this difficult to enable or disable a particular daemon?
You tell me this.