From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Few More questions!
Date: Wed, 8 May 2002 19:09:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205081907330.1072-100000@igueths> (raw)
In-Reply-To: <20020508214530.GA28371@asmodean.net>
Hi all. Speaking of maintanace of distros, I am aware of the fact that the
Debian isos are not up to date with the latest kernel. The Speakup iso
that is. Is anyone maintaining that? Possibly Bill? Because what I was
thinking is that if not, me and a friend of mine are interested in
updating the iso. Please get back to me on this. I will be glad to try and
help out, but I just want to know if someone is actively maintaining the
images.
Gates go to hell, your OS is waiting for you there!
On Wed, 8 May 2002, Raul A. Gallegos wrote:
> Yes Cris now I remember your last name which to me sounded familiar.
> Talk about reunions. Those wer the days when I used irc from a netcom
> shell and Bill Acker used ibm's OS to get into netcom as well. Nice to
> remember you, irc is still used and I still se it. Hope your hunting
> goes well. If you get slackware it comes with a speakup kernel all
> ready to go. Bill Acker has also provided redhat installation with
> speakup compiled into the kernel as well. And let's see, Frank has
> provided disks for Debian. On top of all that there are the other ways
> you can get linux working. To answer your question it does not matter
> which Linux you use as speakup is a part of the kernel which will run
> any distribution of Linux.
>
> --
> If you perceive that there are four possible ways in which a procedure can
> go wrong, and circumvent these, then a fifth way will promptly develop.
> Raul A. Gallegos - http://www.asmodean.net
>
> _______________________________________________
> 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: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
Why does it need that much hard disk space? Cris Ali
` Buddy Brannan
` Raul A. Gallegos
` Ann Parsons
` Gregory Nowak
` Igor Gueths
` Ann Parsons
` Buddy Brannan
` Igor Gueths
` Gregory Nowak
` Toby Fisher
` Buddy Brannan
` Ann Parsons
` Toby Fisher
` Toby Fisher
` William F. Acker WB2FLW +1-303-777-8123
` Ann Parsons
` TALMAGE
` Toby Fisher
` Toby Fisher
[not found] ` <Pine.LNX.4.33.0205100357420.9750-100000@frontdoor.g0ucu.fr eeserve.co.uk>
` TALMAGE
` Toby Fisher
` Igor Gueths
` Few More questions! Cris Ali
` Alex Snow
` Raul A. Gallegos
` Igor Gueths [this message]
` Gregory Nowak
` Why does it need that much hard disk space? Raul A. Gallegos
` Ann Parsons
` Raul A. Gallegos
` Ann Parsons
` Toby Fisher
` jwantz
` Ann Parsons
[not found] ` <Pine.LNX.4.33.0205100415120.9750-100000@frontdoor.g0ucu.fr eeserve.co.uk>
` TALMAGE
` Toby Fisher
` Alex Snow
` Toby Fisher
` Charles Hallenbeck
` Gregory Nowak
` Charles Hallenbeck
` Adam Myrow
` Steve Holmes
` Steve Holmes
` Alex Snow
` Gregory Nowak
` 'Georgina'
` Kerry Hoath
` Cecil H. Whitley
` Igor Gueths
` Gregory Nowak
` Alex Snow
` Cecil H. Whitley
` Gregory Nowak
` Igor Gueths
` Alex Snow
` 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=Pine.LNX.4.44.0205081907330.1072-100000@igueths \
--to=igueths@attbi.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).