From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Zipspeak 8.0
Date: Sat, 27 Oct 2001 17:23:37 -0400 [thread overview]
Message-ID: <001801c15f2d$a4d6eb80$3e128fd1@enterprise> (raw)
In-Reply-To: <001001c15f08$7d02d800$7f7ef59b@essex.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Hi, Saqib. I'm starting my own Linux web site soon, and once everything is set I'll be able to take Zipspeak 8, and post it.
What's the exact size, and I'll see if I'll have enough room to give it a slot on my ftp server.
----- Original Message -----
From: Saqib Shaikh
To: speakup@braille.uwo.ca
Sent: Saturday, October 27, 2001 12:57 PM
Subject: Zipspeak 8.0
Hi,
Sorry, studies have bogged me down recently - the second year is certainly harder than the first!
Anyway, the main thing that is holding me back from a public release is finding somewhere to upload it to. I've emailed Patric Volkerding a few times in the past few months about getting some space on the Slackware FTP site but I think he's rather busy. There's been a lot of termoil around Slackware since their parent company dumped them to fend for themselves. I've been giving CDs of ZipSpeak to people who email me, but if someone can suggest somewhere with lots of web space let me know. This brings up another question: are there still a lot of people who prefer Slackware, or should ZipSpeak be transferred over to RedHat or something - just an idea based on feedback from users.
Just before I go I'd like to ask whether anyone's had any joys using the 2.4.x kernels with an umsdos filesystem?
Saqib
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Saqib Shaikh
` Gregory Nowak
` Kirk Reiser
` Thomas Ward [this message]
` brian Moore
` Raul A. Gallegos
-- strict thread matches above, loose matches on Subject: below --
zipspeak 8.0 Gregory Nowak
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='001801c15f2d$a4d6eb80$3e128fd1@enterprise' \
--to=tward@bright.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).