Linux Newbie help
 help / color / mirror / Atom feed
From: Amin <raihan@citech-bd.com>
To: linux-newbie@vger.kernel.org
Subject: Re: How do I stop GUI from autoloading?
Date: Sat, 10 May 2003 22:09:17 +0600	[thread overview]
Message-ID: <20030510160917.GA890@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.1.20030510082110.01eae2b0@celine>

On Sat, May 10, 2003 at 08:42:05AM -0700, Ray Olszewski
wrote:

> I did not see the original posting, and I can't find it
> anywhere. Amin's response does not indicate whether the
> original posting mentioned the Linux distro involved, and
> he does not do so. And Amin's advice is not

Sorry, I found the original post in Google Groups:
http://groups.google.com/groups?q=mlist.linux.newbie&ie=UTF-8&oe=UTF-8&hl=en&btnG=Google+Search

And here it is:

    From: Workman (david.rust@watkinsmfg.com)
    Subject: How do I stop GUI from autoloading?
    Newsgroups: mlist.linux.newbie
    This is the only article in this thread
    View: Original Format
    Date: 2003-03-30 08:00:16 PST
    
    I've FINALLY freed up one of my Pentiums to use as a
    Linux platform.  (I gotta get away from Microsoft!)
    
    I fought with it for an hour trying to get the install
    program to work, only to find out that my CD drive was
    screwed up (I think removable media drives are the
    weakest link in computers and CD drives are one of the
    worst).
    
    Swapped in a different CD drive and the installation
    took off like gangbusters.  Turbolinux Server 6.0 -
    Lite. Right now it's set up and seems to be working fine
    except that I tried to load the GUI (Gnome - I think)
    and I must have entered the wrong values for the monitor
    Vsync and Hsync.  So the GUI comes up and it's messed
    up. I can't do anything in it.  Damn! Looking back I see
    that my big mistake was in making the loading of the GUI
    automatic - so now I have to figure out how to stop it
    from loading so I can use one of the CLI configuration
    tools to alter the Vsync and Hsync values.
    
    Well - I've heard of the problem in the Linux discussion
    groups (trouble getting the monitor values right) so I
    know this isn't unusual but I think the other people
    were smart enough not to have the GUI load automatically
    and prevent the accessing of the CLI configuration
    tools. The documentation says that pressing
    Control-Alt-Backspace will kill the GUI but it doesn't
    work for me.  It's locked up when the GUI
    displays. Control-Alt-Delete won't reboot it.
    
    Well I wanted to learn about Linux, I guess I AM!
    
    I know I'll need to read more documentation. Meanwhile,
    any ideas, criticism, or encouragement?

> distro-neutral; not all distros use the runlevel setting
> to launch xdm (or gdm). Debian, for example, uses a script
> in /etc/init.d that gets called from runlevel 2 (which it
> uses as its default runlevel).

Sorry, I didn't know about this.  I assumed it was
controlled by ``inittab''.

> Amin made reference to a "messy GUI" in his reply. Since I
> never saw the original message, and he did not quote any
> of it, it is possible that the original questioner
> indicated some reason why he or she could not actually use
> the GUI interface to open an xterm (or possibly even to
> log in). In that case ... typically, distros that run xdm
> also open a hidden console on /dev/tty1, which one can
> access by pressing CTRL-ALT-F1 when the xdm display is
> active. You can then log in, make any needed changes, and
> reboot.

That is a good idea, but I was afraid that it would mess
around with X.  I tried it once (I'm using RH8.0), and it
seemed to hose my X server.

> Finally, if even that does not work, at the lilo prompt
> (assuming we're talking about an install that uses lilo),
> instead of accepting the default load, you can usually
> enter "linux single" to boot/init into single-user mode
> with a console rather than X presented.

I assumed Linux was the lone OS on the PC, so there was no
bootloader.

HTH,
Yawar Amin
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-05-10 16:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 10:09 How do I stop GUI from autoloading? Amin
2003-05-10 13:29 ` Charlotte Miller
2003-05-10 15:09   ` Chuck Gelm
2003-05-10 15:42   ` Ray Olszewski
2003-05-10 16:09     ` Amin [this message]
2003-05-10 16:39       ` Ray Olszewski
2003-05-11 13:51         ` sean
2003-05-11 21:14         ` renaming really long filenames Chuck Gelm
2003-05-11 21:44           ` Ray Olszewski
2003-05-19 16:11           ` Stephen Samuel
2003-05-20 22:16             ` Chuck Gelm
2003-05-19 17:51       ` How do I stop GUI from autoloading? Stephen Samuel
2003-05-19 18:49         ` Richard Adams
2003-05-19 19:07           ` Stephen Samuel
2003-05-19 19:55             ` Richard Adams
2003-05-19 20:39               ` Stephen Samuel
2003-05-19 21:06                 ` Richard Adams
2003-05-19 21:14               ` Ray Olszewski
2003-05-20  5:23                 ` Richard Adams
2003-05-20  6:19                   ` Ray Olszewski
2003-05-20 22:26                     ` Chuck Gelm
2003-05-21 22:47                       ` Riley Williams
2003-05-10 15:43   ` Amin
2003-05-10 15:50     ` Brian P. Bilbrey

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=20030510160917.GA890@localhost.localdomain \
    --to=raihan@citech-bd.com \
    --cc=linux-newbie@vger.kernel.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