On Sun, 31 Aug 2003 00:41:58 GMT
Whyld-Chyld <test@example.com> wrote:

> 'Kay. Much easier to do it when your wide awake. Biggest thing I
> discovered acidently is that it's much safer not to boot directly into
> X, especially if you've trashed your X config. Had it happen and with
> the system being setup to boot into the gui, I wasn't able to fix it
> until I booted with the install disk, chrooted and then removed X from
> the default run level. Once that was done, I fixed the problem and
> have never resorted to a gui boot again.
You could also have booted into a runlevel that doesn't start the gui by
default. Of course you would have to have that configured. I alwas have
the runlevel console and xfree and say it boots into runlevel 5 aka
xfree on default and runlevel 3 would be console.
So on your lilo prompt you would enter
<image> 3 and voila it boots in runlevel 3 (console)
In grub you can select the image, hit e, select the kernel line, hit e,
add a 3 at the end, hit enter and hit b to boot.

Kinda easier than booting rescuedisk and chrooting...

Daniel

On Sun, 31 Aug 2003 12:15:58 GMT
Whyld-Chyld <test@example.com> wrote:

> Grub doesn't like my system since I've got onboard video although I'm
> using the AGP slot.The main reason I was forced to use the recovery
> mode, was simply the fact that when X is configured for the default
> run level, it comes up before you can get the single user mode prompt
> for maintenance. If X is trashed or improperly configured you
> literally can not boot into a working display unless you use the
> recovery cd as I was forced to.

Well, if you haven't configured an optional runlevel witout x to start
you could always pass lilo the init=/bin/bash parameter, which would
completely bypass the init process. But then you would have to manually
remount your root partiton and configure stuff as init would do. So it's
not nice, but it is possible :-)

> The advantages of using the recovery cd are a working enviroment, the
> ability to chroot and correct the problem by running xf86cfg and
> getting X configured. Then you can reboot normally, which is what I'd
> done.

ACK.
I was just pointing out the possibility if you mysteriously lost al your
working rescue disks (yes, I know what I'm talking about - My PC gone
nuts and all knoppix and Gentoo rescue disks disappeared...).

> Having had that problem though, I changed my mind and removed X from
> the default. I've now got a script in the users file to startx when I
> log on. The script works great and isn't setup for the root account.

Okay, that sounds like a nice idea.
Were's what I did:
I copied /etc/runlevels/default to /etc/runlevels/console and
/etc/runlevels/xfree and added xdm only to the xfree runlevel.
Then I changed the inittab to reflect the changes and made xfree my
default runlevel.

# Default runlevel.
id:5:initdefault:

l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc console
l4:4:wait:/sbin/rc console
l5:5:wait:/sbin/rc xfree

Now if I type "<image> 3" at the LILO prompt linux boots directly into
runlevel 3 whick doesn't boot into X at all.

Daniel Willmann

Matata <koen@NOSPAM.pi.be> schrieb:

>I emerged kde.
>But I don't know how to start it now.
>I believe I need to start Xserver first...

look here:
http://www.gentoo.org/doc/en/kde-config.xml
Eggert