public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Subject: Re: The FAQ
Date: Mon, 18 Jun 2001 03:31:48 +0200	[thread overview]
Message-ID: <002f01c0f796$ce8d84b0$0100a8c0@cybertsar> (raw)
In-Reply-To: <Pine.LNX.4.33.0106171756020.1601-100000@toccata.grg.afb.net>

Very good point, Janina! But this should be pointed out in the FAQ. Users
should feel the advantages!
Best,
Victor

----- Original Message -----
From: "Janina Sajka" <janina@afb.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 17, 2001 11:59 PM
Subject: Re: The FAQ


> You're missing my point. The issue is not "can it be done." The issue is
> how easy is it using the canned install software of the various distros.
> If the various distros will do this in a smart way, as a recent poster
> suggests Debian does, then it argues for pushing the minimum system reqs
> back. And, as Ann points out, that's very good because it includes more
> people with more systems that are sitting around. But, if you have to be a
> Matt Campbell to figure out how to put a working distro topgether in 95
> megs, that's another story. Functionality is also important--you want to
> have things you can do with the minimal system--and that doesn't mean "use
> it as a router," not for the audience this FAQ addresses, imho.
>
>  On Sun, 17
> Jun 2001, Gregory Nowak wrote:
>
> > Zipslack demonstrates that you can have
> > a basic system running on 95 megs.
> > Greg
> >
> >
> > On Sun, Jun 17, 2001 at 04:18:04PM -0400, Ann Parsons wrote:
> > > Hi all,
> > >
> > > First of all, I want to tell you all how much I appreciate all your
> > > help.  You guys are great, and I really appreciate all your comments.
> > >
> > > Now, let me rebut some of this stuff.  From the discussion about the
> > > different distros and the different ways to obtain good results, I
> > > have concluded that the instructions on how to install Speakup do not
> > > belong in the FAQ.  They belong in a full document of their own,
> > > complete with full discussion of the exact commands relating to
> > > synthes and distros and kernel versions.  This is a FAQ.  the answer
> > > to the question about how to install Speakup should be as general as
> > > possible and point to specific info in an additional document.  Note:
> > > Janina, the reason that the install part of the FAQ seems to be skewed
> > > toward Slackware is simply because that was the *only* specific
> > > instructions I received.  Since I'm not a techie, I'm a writer, I work
> > > with what I'm given.
> > >
> > > RE the beginning paragraph, yes, Janina, you are right on all counts,
> > > and I will change it forthwith.
> > >
> > > RE the discussion on cursoring, yes, you're right there too.  I think
> > > I'll just delete it.
> > >
> > > RE the discussion of Speakup and Emacspeak, notice I didn't say V.S.,
> > > I liked your comments there too.    I shall incorporate them.
> > >
> > > RE the question about which versions of speakup work with which
> > > kernels, I think that I will change 0.10 to 0.10A and say that those
> > > who are using older kernel versions need to consult either the list or
> > > blah, blah, docs which I hope are available.
> > >
> > > RE the bit about Linux and older systems, no, I disagree about leaving
> > > this out.  Reason?  This is an issue close to my heart.  It is
> > > precisely because Linux can run well on a 486, I have one upstairs,
> > > that it is so valuable!  It is not difficult to get Linux to work on a
> > > 486, especially if you use a distro that allows you to use the pkgs
> > > you need instead of the pkgs that include X and so on.  Debian and
> > > Slackware are particularly well suited to this type of customized
> > > installation.  If there were a doc about which pkgs were actually
> > > needed in order to run a decent system on a 486, that would be great.
> > > Maybe I'll write one, after this here FAQ.  Do you guys remember when
> > > you had a shell account that only had 20 megs in it?  You can run a
> > > basic system in about 800 megs.  As for mp3's no, you may not have
> > > room for MP3's but you can stream some of them.  If 30 gig hard drives
> > > are down to $99, what are 2.5 ones going for, eh?
> > >
> > > Yes, the comment about if it runs on Windows OK, it will run on Linux
> > > is apt.    I will include it.
> > >
> > > I think I've covered the water-front here.  If I haven't, just give me
> > > a nudge and remind me.  I figured it would be easier to write one long
> > > msg rather than try to answer everyone individually.  Again, thanks so
> > > much for all your help.  I'm going to continue to need it if this docs
> > > project is going to continue.
> > >
> > > Ann P.
> > >
> > >
> > >
> > > --
> > > Ann K. Parsons
> > > email:  akp@eznet.net ICQ Number:  33006854
> > > WEB SITE:  http://home.eznet.net/~akp
> > > "All that is gold does not glitter.  Not all those who wander are
lost."  JRRT
> > >
> > >
> > > _______________________________________________
> > > 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
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ann Parsons
 ` Gregory Nowak
   ` Janina Sajka
     ` Gregory Nowak
       ` Janina Sajka
     ` Victor Tsaran [this message]
 ` Janina Sajka

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='002f01c0f796$ce8d84b0$0100a8c0@cybertsar' \
    --to=tsar@sylaba.poznan.pl \
    --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).