On 6/21/06, Paul Stear [EMAIL PROTECTED] wrote:
Hi,I am running an ~x86 system and yesterday I did an emerge world, all went welluntil the next time I booted. kdm ran but the screen just had a flashingloggin box.I could not even get another terminal using alt F1-F7. So I am
faced with not being
On Wed, 21 Jun 2006 10:47:11 +0100, Paul Stear wrote:
I am running an ~x86 system and yesterday I did an emerge world, all
went well until the next time I booted. kdm ran but the screen just had
a flashing loggin box. I could not even get another terminal using alt
F1-F7. So I am faced with
On Wednesday 21 June 2006 11:05, Neil Bothwick wrote:
On Wed, 21 Jun 2006 10:47:11 +0100, Paul Stear wrote:
1. What is the correct procedure to recover a system in this state?
What tools do I need?
In this case, all you need to do is boot without X, or SSH in from
another box. As a last
2006/6/21, Paul Stear [EMAIL PROTECTED]:
On Wednesday 21 June 2006 11:05, Neil Bothwick wrote:
On Wed, 21 Jun 2006 10:47:11 +0100, Paul Stear wrote:
1. What is the correct procedure to recover a system in this state?
What tools do I need?
In this case, all you need to do is boot without
Paul Stear wrote:
On Wednesday 21 June 2006 11:05, Neil Bothwick wrote:
On Wed, 21 Jun 2006 10:47:11 +0100, Paul Stear wrote:
1. What is the correct procedure to recover a system in this state?
What tools do I need?
In this case, all you need to do is boot without X, or SSH in from
Another way: If you use grub, you can edit the boot command line. Add
init=/bin/sh to the end of the boot command line.
Alexander Skwar
--
Dreams are free, but there's a small charge for alterations.
--
gentoo-user@gentoo.org mailing list
The same method applies to lilo too.
--
Best
Daniel Iliev wrote:
Another way: If you use grub, you can edit the boot command line. Add
init=/bin/sh to the end of the boot command line.
Alexander Skwar
--
Dreams are free, but there's a small charge for alterations.
--
gentoo-user@gentoo.org mailing list
The same method applies to
On Wednesday 21 June 2006 13:39, Alexander Skwar wrote:
True. But with lilo, you've got to modify the lilo.conf (or what's
it called?) and run lilo, don't you?
Or can you modify the boot command line on-the-fly in the boot
menu?
Of course: after selecting an entry from the lilo menu, just
Etaoin Shrdlu wrote:
On Wednesday 21 June 2006 13:39, Alexander Skwar wrote:
True. But with lilo, you've got to modify the lilo.conf (or what's
it called?) and run lilo, don't you?
Or can you modify the boot command line on-the-fly in the boot
menu?
Of course: after selecting an entry
2006/6/21, Etaoin Shrdlu [EMAIL PROTECTED]:
Well, no flame, but it's probably easier than with grub, where you have
to explicitly press some key to modify the command line.
I agree. I don't want to say anything like lilo is better (I
personally prefer grub because I always forget to run lilo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nico Schümann wrote:
2006/6/21, Etaoin Shrdlu [EMAIL PROTECTED]:
Well, no flame, but it's probably easier than with grub, where you have
to explicitly press some key to modify the command line.
I agree. I don't want to say anything like lilo is
On Wednesday 21 June 2006 13:58, Alexander Skwar wrote:
Hm - can you also *modify* the boot commands? Say, the boot command
in lilo.conf contains vga=123 and now, for whatever reason, you
want vga=ask - what to do?
You pass vga=ask on the fly on the command line and this takes precedence
Arturo 'Buanzo' Busleiman wrote:
Nico Schümann wrote:
2006/6/21, Etaoin Shrdlu [EMAIL PROTECTED]:
Well, no flame, but it's probably easier than with grub, where you have
to explicitly press some key to modify the command line.
I agree. I don't want to say anything like lilo is better (I
On Wed, 21 Jun 2006 15:04:04 +0200, Etaoin Shrdlu wrote:
You pass vga=ask on the fly on the command line and this takes
precedence over whatever is in lilo.conf.
The same happens for the root=, initrd=, ramdisk=, and other
kernel parameters.
What happens if something is wrong with your
2006/6/21, Neil Bothwick [EMAIL PROTECTED]:
What happens if something is wrong with your initrd and you need to
remove the initrd= option from the command line?
I'd try things like initrd= for example. Maybe it's ignored.
--
gentoo-user@gentoo.org mailing list
On Wednesday 21 June 2006 15:40, Neil Bothwick wrote:
What happens if something is wrong with your initrd and you need to
remove the initrd= option from the command line?
Good question! In this regard, grub is certainly better since it shows
you the complete command line, and you can tweak
On Wed, 21 Jun 2006 16:37:27 +0200, Etaoin Shrdlu wrote:
What happens if something is wrong with your initrd and you need to
remove the initrd= option from the command line?
Good question! In this regard, grub is certainly better since it shows
you the complete command line, and you can
On Wed, 21 Jun 2006 15:41:56 +0100
Neil Bothwick [EMAIL PROTECTED] wrote:
Those of you that only use x86 based system don't know how lucky you are
to have two decent bootloaders. If you took the worst aspect of LILO and
GRUB and added some extra user-hostility for luck, you'd still have
18 matches
Mail list logo
