From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from shawmail.shawcable.com ([64.59.128.220] helo=bpd2mo1no.prod.shawcable.com) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 193Q9U-0007oQ-00 for ; Wed, 09 Apr 2003 20:42:52 -0400 Received: from bpd2mi2no.prod.shawcable.com (bpd2mi2no-qfe3.prod.shawcable.com [10.0.184.121]) by l-daemon (iPlanet Messaging Server 5.2 (built Feb 21 2002)) with ESMTP id <0HD300L9ORAIIN@l-daemon> for speakup@braille.uwo.ca; Wed, 09 Apr 2003 18:42:18 -0600 (MDT) Received: from nomad.shawcable.com ([24.70.172.254]) by l-daemon (iPlanet Messaging Server 5.2 (built Feb 21 2002)) with ESMTP id <0HD300B22RAIA0@l-daemon> for speakup@braille.uwo.ca; Wed, 09 Apr 2003 18:42:18 -0600 (MDT) Date: Wed, 09 Apr 2003 19:42:51 +0200 From: Doug Sutherland Subject: Re: Slack 9 problems!!! In-reply-to: <006501c2fef9$a98d0b60$2b849641@tward1978> X-Sender: wearable@mail.shawcable.com To: speakup@braille.uwo.ca Message-id: <5.1.0.14.2.20030409194014.02bc9508@mail.shawcable.com> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Content-type: text/plain; charset=us-ascii; format=flowed References: <5.1.0.14.2.20030405113312.00ad7b60@mail.shawcable.com> <5.1.0.14.2.20030405102215.00aeae40@mail.shawcable.com> <5.1.0.14.2.20030405113312.00ad7b60@mail.shawcable.com> <5.1.0.14.2.20030409163416.00ad3090@mail.shawcable.com> Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: All of those tools for automatic config etc are good when they work ... but they add complexity. That was my point. A better example is mandrake. Pretty slick install but you're buried layers of stuff. I like the minimalistic slackware mentality. I know where everything is, and what depends on what. I should keep my mouth shut because this is not the place to debate such things. What if kudzu doesn't do what it's supposed to? -- Doug >I'm a little unclear why you would say Red Hat is too complex to understand >what it does. I suspect since I have used RH from the beginning I understand >it's inner workings better than a Slack user, but I personally don't find it >dificult.