public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: down for the count
Date: Sat, 30 Sep 2000 22:49:13 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0009302237420.648-100000@localhost.localdomain> (raw)
In-Reply-To: <m13fRLq-0013u8C@braille.uwo.ca>

Without trying to slam anyone, I would not take an install problem on one
machine to mean much. I also wouldn't take a lack of install problem to
mean much. I can truthfully say I have never had a problem installing
Winblows 3.x on a machine (and did it many times). Anyone care to say it
is superior?

I have had trouble with a Slackware install. But I also worked through
said install. As for the problems in maintaining RedHat, I think the
problem that some run into is trying too hard. I have installed both RPM
and the compile thing. For some, RPM is easier. For others, it will lead
to problems later. (Domn, that is starting to sound like so many other
things with computers and life in general.) But for most things, there are
straight forward tools to do your configuration for you. My complaint
about RedHat is that you get many things installed that you don't know
about. Then again, I think that a great thing would be a database with all
dependancies listed for each package. Yea, I know RPMs provide that (in
theory). But there is no tool (for any distro I have seen) that allows one
to plan ahead seeing all dependancies and configure the system to install
just the way you want it minus perhaps the settings.

I think going with a preconfigured machine is a good idea. It won't take
any longer to wipe out the installed OS then if you get one with
Winblows. I mean really, fdisk covers a multitude of sins. If you know you
are going to run linux and that is an option for the machine it makes
sense. You can always blow it away and install a different distro. (And
you can later do the same thing to that distro. I know it is obvious, but
too often it is forgotten.)

-- 
Kirk Wood
Cpt.Kirk@1tree.net
------------------

Seek simplicity -- and distrust it.
		Alfred North Whitehead





  parent reply	other threads:[~ UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Charles Hallenbeck
 ` Jacob Schmude
 ` philwh
   ` Brent Harding
 ` Kirk Wood [this message]
   ` Victor Tsaran
     ` Kirk Wood
   ` Geoff Shang
     ` Frank J. Carmickle
       ` speakup on a sparc Raul A. Gallegos
         ` Kerry Hoath
           ` World Blind Union Janina Sajka
         ` speakup on a sparc Buddy Brannan
           ` Victor Tsaran
             ` Chris Nestrud
             ` Brent Harding
           ` Kirk Reiser
             ` Kerry Hoath
               ` Kirk Reiser
                 ` Kerry Hoath
             ` Brent Harding
               ` Kerry Hoath
                 ` Brent Harding
   ` down for the count Geoff Shang
     ` Kirk Wood
  -- strict thread matches above, loose matches on Subject: below --
 Charles Hallenbeck
 ` Buddy Brannan
   ` Frank J. Carmickle
     ` Victor Tsaran
   ` Brent Harding
 rturner2
 Charles Hallenbeck
 ` Jacob Schmude
   ` Kerry Hoath
     ` Jacob Schmude
 Charles Hallenbeck
 Charles Hallenbeck
 ` Jacob Schmude
   ` Kerry Hoath
 ` Cheryl Homiak

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=Pine.LNX.4.21.0009302237420.648-100000@localhost.localdomain \
    --to=cpt.kirk@1tree.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).