public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Jude DaShiell <jdashiel@shellworld.net>
To: <blinux-list@redhat.com>
Cc: <fleet@teachout.org>
Subject: red hat install lock up
Date: Fri, 7 Sep 2001 00:20:59 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0109070008320.19721-100000@ns.shellworld.net> (raw)

For the installation we selected everything and got the hard drive
partitioned with disk druid.  I got to put the parameter in for lilo and
eventually got asked to put the second cd in and hit ok.  No problem more
files were being installed.  Then I dozed off for a little bit and when I
woke up all was silent.  I used the keys to find out what was on the
screen and found the whole system had locked and control had gone away
from the keyboard.  I take it that this is the penguin's way of telling me
I neeed more installation practice.  Though next time when packages start
installing I'll disconnect the litetalk from the computer.  I found that
allows installation to go much faster.  My install also warns me it's time
to run e2fsck because check time has been reached but then goes on to do
the install.  I hope that's not why the linux installation won't come up
talking.  I think we're further ahead of the game though since we have the
disk partitioned and formatted provided we can skip that step.  The boot
disk I have loads speakup 0.9 on the system.  I'll get an update if one's
available and needed but before I try another installation of this system.
I did try bringing up linux on the hard drive with floppy and cd removed
and the speech synthesier was detected but the installation came up silent
this time too so I'll try this again tomorrow night.

Jude <jdashiel@shellworld.net>




             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jude DaShiell [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=Pine.LNX.4.33.0109070008320.19721-100000@ns.shellworld.net \
    --to=jdashiel@shellworld.net \
    --cc=blinux-list@redhat.com \
    --cc=fleet@teachout.org \
    /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).