From: Mike Gorse <mgorse@mgorse.dhs.org>
To: <blinux-list@redhat.com>
Subject: Re: red hat system almost talking
Date: Sat, 8 Sep 2001 21:33:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0109082122220.13206-100000@mgorse.dhs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109082056260.15301-100000@ns.shellworld.net>
You should be able to get back to a virtual console by hitting
ctrl-alt-f1. You may be able to disable Gnome by telling init to start
using a different runlevel. You should have a line in /etc/inittab like
id:2:initdefault
where the 2 indicates to start with runlevel 2. The runlevel is often
used to determine which initialization scripts should be run, and x may
not be started with a lower runlevel. I am not sure how RedHat works,
though, so someone can correct me...
--Michael Gorse / ICQ:22583968 / http://mgorse.home.dhs.org
On Sat, 8 Sep 2001, Jude DaShiell wrote:
> When I boot now, I hear lilo, then I hear boot, then I hear loading linux,
> then I hear the at sign, and all the rest is silence. If I hit ackspace I
> don't hear the beep so this thing is still coming up in gnome mode. I
> managed to log in using gnome and get such changes I have managed using
> exec >/dev/ttyS0 2>&1 on a line by itself.
> I got Bill's speakup.kmap.gz file stored and loaded into
> /etc/sysconfig/keyboard too. How do I disable gnome permanently so it
> doesn't break the log in anymore?
>
>
> Jude <jdashiel@shellworld.net>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Mike Gorse [this message]
` red hat system almost talking: question related to comments Cheryl Homiak
` Jude DaShiell
` Janina Sajka
` Cheryl Homiak
` S. Massy
` red hat system almost talking L. C. Robinson
` Jude DaShiell
` L. C. Robinson
` Jude DaShiell
` Janina Sajka
` 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.0109082122220.13206-100000@mgorse.dhs.org \
--to=mgorse@mgorse.dhs.org \
--cc=blinux-list@redhat.com \
/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).