public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: zip speak
Date: Fri, 29 Nov 2002 12:37:10 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211291236490.13456-100000@igueths> (raw)
In-Reply-To: <004a01c29764$94ed5220$a600a8c0@glenn>

Well you have an entire drive to devote to it, so why not? All you will
have to do if something goes bye bye is blow away the distro anyway.

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 Thu, 28 Nov 2002, Glenn Ervin wrote:

> Hi Janina,
> I guess I am just paranoid about installing Linux for the first time, and I
> would rather screw up zipspeak, than screw up my first install of RedHat.
>
> ----- Original Message -----
> From: "Janina Sajka" <janina@rednote.net>
> To: <speakup@braille.uwo.ca>
> Sent: Friday, November 29, 2002 10:58 AM
> Subject: Re: zip speak
>
>
> Don't bother with zipspeak. You're wasting your time given that you have
> an entire drive to devote to Linux. You have nothing in jeopardy and
> nothing to lose. Install the Red Hat you downloaded and learn from
> something that's up to date.
>
>
> Glenn Ervin writes:
> > From: "Glenn Ervin" <glennervin@cableone.net>
> >
> > I just installed zipspeak, so I could get some linux under my belt before
> > installing RedHat.
> > I encountered an error, and I would like some feedback please.
> > I got the final message:
> > kernel panic vfs error mounting fs 0300
> > Or something very similar.
> > I had made more progress with this attempt after I changed the root to hda
> > from hda1
> > the zipspeak is installed on c:\linux by default.
> > This is installed on my 80 GB harddrive.
> > I remember some of the speakup keystrokes, but I am not sure what to do if
> > it actually works.
> > I believe it may ask for a password, and it seems like it is:
> > passwrd
> > and there was something about user name I believe.
> > I sure hope someone cane give me some suggestions on the first problem, as
> > well as an idea of what to expect when it works.
> > Thanks in advance!
> >
> >
> > "Live long and prosper",
> > O. Glenn Ervin (Lenny)
> > N0YJV
> > Northeast Nebraska
> > e-mail:
> > glennervin@cableone.net
> > The above address can also be found on MSM.
> > or my work e-mail:
> > gErvin@ncbvi.state.ne.us
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
>
> Email: janina@afb.net Phone: (202) 408-8175
>
> _______________________________________________
> 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
>



  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Glenn Ervin
 ` Janina Sajka
   ` Glenn Ervin
     ` Igor Gueths [this message]
     ` Janina Sajka
  -- strict thread matches above, loose matches on Subject: below --
 Nick Gawronski

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.0211291236490.13456-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).