From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Slack 9 problems!!!
Date: Wed, 9 Apr 2003 20:39:35 -0400 [thread overview]
Message-ID: <006501c2fef9$a98d0b60$2b849641@tward1978> (raw)
In-Reply-To: <5.1.0.14.2.20030409163416.00ad3090@mail.shawcable.com>
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.
----- Original Message -----
From: Doug Sutherland <wearable@shawcable.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, April 09, 2003 10:36 AM
Subject: Re: Slack 9 problems!!!
> Steve,
>
> Slack 9 is awesome ... with the new hotplug support
> in place it found everything for me ... slack is
> getting better all the time. I am a slack addict :)
> Patrick is doing good work. To be honest redhat is
> too complex to even know what it does IMO ...
>
> BTW I tried building a linux sytstem entirely from
> source www.linuxfromscratch.org ... lots o fun. If
> you really want to understand linux ... this goes
> down to the basics ...
> -- Doug
>
>
> At 01:29 PM 4/9/2003 -0700, you wrote:
> >On Sat, Apr 05, 2003 at 11:36:37AM +0200, Doug wrote:
> > > Thomas,
> > >
> > > > Thanks, this was vary helpful.
> > >
> > > I started on Redhat long ago in the Redhat 5 days, then
> > > switched to slackware a few years ago. Yes there is a lot
> > > to learn, but if you persist, slackware is a great system.
> > > It is great because of its simplicity. That may not seem
> > > true right now, but it will later if you keep on plugging.
> > > If you have more slackware questions, feel free to send
> > > me email directly. I've done so many slackware installs
> > > I can almost do it in my sleep.
> >
> >Yeah and now the 9.0 release was pretty to upgrade in place too. Past
> >experiences with upgrading in place usually ended up having to be a
> >complete reinstall but this time, I was able to update the various
> >packages tweek a few files in /etc and away I go! Sure handy to have
> >diff around to compare the new files from the upgrade with the
> >original ones.
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas D. Ward
` Doug
` Adam Myrow
` Thomas D. Ward
` Adam Myrow
` Doug
` Lorenzo Prince
` Thomas D. Ward
` Doug
` Steve Holmes
` Doug Sutherland
` Thomas D. Ward [this message]
` Doug Sutherland
` Luke Davis
` Thomas D. Ward
` Alex Snow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006501c2fef9$a98d0b60$2b849641@tward1978' \
--to=tward1978@earthlink.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).