I can't login! :(

Jerry Feldman gaf at blu.org
Mon Feb 14 20:43:02 EST 2000

First, I assume you are using Red Hat because SuSE does not use Linuxconf. 
I would first boot linux into single user mode:
At the lilo prompt:
LILO: linux S
This mouts your root drive read only:
Then, do an fsck manually:
I prefer: fsck -fsy /dev/hda1 ...
assuming your root drive is hda1. The options are:f - force, s - serialize, 
y - answer y (kind of dangerous).
Then remount your root drive read/write.
mount -o rw,remount /

Check your kernel messages and see if the kernel recognized your ethernet 

At this point, I might want to just reboot, and boot into run level 2 
(command line, no network).
(You could do telinit 2, but for diagnostic purposes, I would just reboot. 

LILO: linux 2

If this comes up ok, then I might want to bring up the network. Check the 
order of the network scripts in /etc/rc.d/rc3.d.
Assuming your script for dhclient is:
/etc/rc.d/init.d/dhclient then,
/etc/rc.d/init.d/dhclient start 
should try to start the network. 

Do one at a time. After you get dhclient up. run ifconfig to make sure your 
interfaces are up.
You could have something else wrong. 

Then I would go through the multi-user steps by hand. In Red Hat, the 
/etc/rc.d/rc3.d has the scripts  to start up in multi-user mode with no 
gui, but with network up.

Josh Forman wrote:
> Suddenly I'm having major problems.
> During the startup process, the last thing I see is "Remounting root
> filesystem in read/write mode         [PASSED]" and it just kinda hangs
> there.  If something is getting frozen, it's whatever comes next.   If I hit
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group

Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).

More information about the Discuss mailing list