At 08:04 AM 9/10/2003, Benjamin Flaming wrote: >For the sake of offering an alternative view, I've found Slackware to be a >*much* better distro for a hands-on learner like me. I never really got >into Linux very deeply until I switched over to Slackware. Believe it or >not, I think you have to know *more* in order to use Redhat or Debian for >audio. The simple reason is that the other distros introduce so many >non-standard behaviors, that I could rarely even complete a simple HOWTO >without some cryptic error message popping up. Now that I've switched to >Slackware, OTOH, things generally work right from the start. Even >Cinelerra, which (according to the web site) is supposed to be difficult >to build from source, compiled without complaint and runs without a >hitch. Your milage may vary, of course ;) I totally agree. Started with Debian 2.2, tried Mandrake, RedHat, and now Slackware. This is where I am staying. I feel totally in control of my system, I know exactly what is running, and how it is started and stopped, I can break a package open to fetch one file without having to install the whole damn thing, and even rebuild it again without having to write some criptic file just to tell the package manager that something should be done when the package is installed etc. I also like the fact that all the setup programmes, eg the installation and configuration, is all written in bash scripting, using the dialog programme to make it interractive. Installation programmes written and compiled are more of a problem IMO, as if you have a problem, you can simply open the script file, find the spot with the problem, and make a modification on the fly, and continue with the running of the script. ---------------- Luke Yelavich AudioSlack Founder and main package maintainer Audio software packaged for the Slackware Linux Distribution http://www.audioslack.com luke@xxxxxxxxxxxxxx
