public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Erik Heil" <eheil@rcn.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Installing Linux with Speakup Scheduled at CSUN
Date: Sun, 17 Nov 2002 11:10:58 -0500	[thread overview]
Message-ID: <002e01c28e53$ed671220$0201a8c0@6S4X011> (raw)
In-Reply-To: <Pine.LNX.4.44.0211170957390.546-100000@igueths>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Igor,
Well, this is interesting.  .Net Server 2003 has a whole lot of command
utilities.  You can actually perform all administration tasks via the
console and it even has a command shell.  Wonder if they're actually ports
of Unix utilities?
- ----- Original Message -----
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, November 17, 2002 10:01 AM
Subject: Re: Installing Linux with Speakup Scheduled at CSUN


> Hi Scott. Now that you brought it up, its true that everyone chooses what
> works for them. Unfortunately, M$ wants to impose their system on
> everyone, which really isn't going to work. Others like me, who like to
> see all low-level functionality, and be able to do whatever they want, are
> severely impaired by a system like Winblows, which both hides the
> underlying workings of the box, and makes someone use their stupid gui no
> matter who they are. I'm supposed to interact with a gui when I can do the
> same thing much faster and tweek it much more on the command line? I don't
> think so!
>
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
>
> On Sun, 17 Nov 2002, Scott Howell wrote:
>
> > Ah, We're back to this topic again.
> >
> > Well folks the truth be told, the adverage person doesn't give a tiny
> > tin damn about what os their machine runs, doesn't care to know ram from
> > ram, and isn't even interested in fiddling about with the box. THey go
> > to the store, purchase what they believe to be the best box for the
> > bucks, come home, get out the big poster that tells them where to plug
> > the keyboard, mouse, etc. in, and turn it on. What the adverage person
> > does care about is how can the accomplish the task and how quickly
> > without a great deal of fuss. The same applies to the adverage person
> > who owns a car, they just want to drive and get where they are going.
> > THey don't care how many cylinders it has, where its got a carb or fuel
> > injected etc. I agree if your going to take on the task of learning an
> > os, expect to hit bumps along the way and don't bitch, ask questions,
> > read, learn, and so forth.
> > So, now if you wonder why there are technicians in the world, now you
> > know. So, lets not go about beatting others on the head because they
> > aren't interested in Linux or say that Linux isn't ready for the
> > adverage user. In fact Linux can be used by the adverage user once its
> > install. They wouldn't have a clue or care if its windows or Linux as
> > long as they can accomplish the task at hand. It holds true that the
> > same adverage user probably wouldn't want to install windows either.
> > Hell you buy a machine and it comes with the os already install and most
> > all applications. Now if you handed someone a LInux box with everything
> > on it, I'm sure they would be just as happy. I think the only challenge
> > is perhaps installing some new application. There is no generic method
> > I'm aware of to install some package you bought from the store.
> > COnsider if you were to buy some new word processing package, most LInux
> > distros have a basic feel, but different installation methods, I can see
> > how this would pose a problem for someone who would have to find a
> > package for their distro. Because there is only one windows, its easy to
> > purchase software. I think you see my point.
> > Ay, lets face it folks, Linux is not for everyone and neither is
> > windows, and neither is the Mac os. YOu pick what works best for you. Of
> > course thre are tinkers of cars, computers, and so on and that is what
> > most of us are. We are interested in the "under the hood" stuff.
> >
> > Scott
> >
> >
> > _______________________________________________
> > 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
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 294) Beta

iQA/AwUBPde/jjmECcLUqviGEQKCiwCgyI7yF1oUWWzmvNDk6YAg1Uzu64kAn0zz
rLF1GhSjfw6fbdAHKHa0OXO8
=CVi/
-----END PGP SIGNATURE-----




  reply	other threads:[~ UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Janina Sajka
 ` Alex Snow
   ` Toby Fisher
     ` Thomas Stivers
 ` Will Smith
   ` Janina Sajka
 ` jwantz
   ` Janina Sajka
     ` michael malver
       ` Ed Barnes
         ` shaun_oliver
           ` ccrawford
           ` Scott Howell
             ` shaun_oliver
               ` Ann Parsons
             ` Igor Gueths
               ` Erik Heil [this message]
                 ` ccrawford
                   ` John Lee
               ` Scott Howell
             ` Kerry Hoath
               ` Scott Howell
         ` Chuck Hallenbeck
           ` Ann Parsons
           ` Igor Gueths
       ` Janina Sajka
   ` ccrawford
     ` Ann Parsons
       ` Charles Crawford
         ` Patrick Turnage
 ` Toby Fisher

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='002e01c28e53$ed671220$0201a8c0@6S4X011' \
    --to=eheil@rcn.com \
    --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).