Linked by Eugenia Loli on Wed 24th Sep 2003 01:45 UTC
Slackware, Slax For almost a week now, I've been using Slackware 9.1 (RC-1 released today), and I am having a blast. Slackware doesn't have more than 6-8% of the Linux market these days, but it used to be one of the most-used distros back in the day. Today, many think of Slackware as a true classic, a thought that is often accompanied by a feeling that Slackware is not a user-friendly or an uber-modern Linux distribution. There is some truth in that statement, but there is always the big "But". Read on for our very positive experience with Slackware 9.1-pre. Update: In less than 24 hours since the RC-1, Slackware 9.1 RC-2 is out.
Permalink for comment
To read all comments associated with this story, please click here.
RE:Multiple Sound & Linux will implode
by Edward on Wed 24th Sep 2003 03:40 UTC

nifotc is Correct - The VIA sound chips do not support multiple input streams. When I looked at this a couple of months ago (on the very same chip) there was an argument raging on the lists as to if channel mixing should be handled at the driver or user space level.

Since I've got an SB Live! which handles multiple channels in hardware, I stopped caring.

My feeling is that it should be handled at the driver level. ESD/Arts do nothing for me (unless I'm running a remote client), yet KDE / GNOME wanting to run them by default. So with a default setup, this means that userspace level software is emulating hardware. Stupid. It would be much better for the driver to handle mixing. This would mean that h/w mix cards could do it in hardware, and software mix card
can do it in software, without having more complexity added to the system. For those who, for whatever reason, don't like software mixing on single channel cards, this could be turned off during compiling.

This is however, an ALSA issue, not a Slackware issue. ESD and Arts sound like their broken - this is the beta after all.

RE Linux will implode by none:
It sounds like your major issue is with Redhat and it's package system. Try something debian based or source (gentoo maybe) based? Things should work a lot cleaner. I've been running Debian unstable with large amounts of upgrading for the past couple of years off the same installation - and apart from the occasional problem with unstable packages (my bad), things have been pretty clean.

As for memory usage, Linux will use whats avaliable. This isn't an issue. You may also discover on closer inspection that the '200 MB' is shared. Example: Five programs use 5 MB each, plus 15 MB of shared memory. The total used is 40 NB. The total reported is 100 MB.

As for KDE - I've heard reports that it is essentially broken under Redhat. If you prefer KDE to GNOME, Redhat is probably the wrong distrobution to be using.