Wierd thing happened, I was trying ot modify a user's password while su'd as root using linuxconf and it crashed and crashed and crashed!! So i got out of the system, rebooted and now root is completely shut out of the system, can't log in. 2 users are the only ones that can log in out of about 20. I can't seem to bring it down to single mode either so i can change the passwrd there, i've tried linux single and it doesn't work, brings me to some GUI where it asks for root password and won't accept it at all. I'm using RH 6.2 and I can't upgrade it due to configuration control, it has to be 6.2 to work with some custom drivers and software we built. Any help would be appreciated on this, i'm kind of at a loss on it. I can't evne back up my data because when i can get in as one of the users, they don't have permissions to the directories i need.

you will probably need to find a boot disk or cd where you can mount your drive and restore the /etc/passwd file and your filesystem permissions.

Hi,

you can reboot the system and add the kernel option init=/bin/sh, then you will be on the system without any password.

Regards
malcom

Easiest way to recover Linux from root being locked out is to use Toms Root Boot. Really easy to use. All you need is the program, and access to a floppy drive on the system. Download the program at Toms Root Boot

Included in the package:
1) tomsrtbt is

"The most GNU/Linux on one floppy disk"

for:

rescue recovery panic & emergencies

tools to keep in your shirt pockets

whenever you can't use a hard drive

Tomsrtbt stands for:

"Tom's floppy which has a root filesystem and is also bootable."
___ _ _ _ _ _


2) Design goals

as much stuff as possible on 1 floppy disk

keep it self contained, build under itself

try to make it behave like a normal system

rescue and recovery functions get priority


3) Contents

What you have is... AHA152X AHA1542 AIC7XXX BUSLOGIC DAC960 DEC_ELCP(TULIP)
EATA EEXPRESS/PRO/PRO100 EL2 EL3 EXT2 EXT3 FAT FD IDE-CD/DISK/TAPE IMM INITRD
ISO9660 JOLIET LOOP MATH_EMULATION MINIX MSDOS NCR53C8XX NE2000 NFS NTFS
PARPORT PCINE2K PCNET32 PLIP PPA RTL8139 SD SERIAL/_CONSOLE SLIP SMC_ULTRA SR
ST VFAT VID_SELECT VORTEX WD80x3 .exrc 3c589_cs agetty ash badblocks basename
boot.b buildit.s busybox bz2bzImage bzip2 cardmgr cardmgr.pid cat chain.b
chattr chgrp chmod chown chroot clear clone.s cmp common config cp cpio cs
cut date dd dd-lfs debugfs ddate df dhcpcd-- dirname dmesg domainname ds du
dumpe2fs e2fsck echo egrep elvis ex false fdflush fdformat fdisk filesize
find findsuper fmt fstab grep group gunzip gzip halt head hexdump hexedit
host.conf hostname hosts httpd i82365 ifconfig ile init inittab insmod
install.s issue kernel key.lst kill killall killall5 ld ld-linux length
less libc libcom_err libe2p libext2fs libtermcap libuuid lilo lilo.conf ln
loadkmap login ls lsattr lsmod lua luasocket man map md5sum miterm mkdir
mkdosfs mke2fs mkfifo mkfs.minix mknod mkswap more more.help mount mt mtab mv
nc necho network networks nmclan_cs nslookup passwd pax pcmcia_core pcnet_cs
pidof ping poweroff printf profile protocols ps pwd rc.0 rc.S rc.custom
rc.custom.gz rc.pcmcia reboot rescuept reset resolv.conf rm rmdir rmmod route
rsh rshd script sed serial serial_cs services setserial settings.s sh shared
slattach sleep sln sort split stab strings swapoff swapon sync tail tar tcic
tee telnet telnetd termcap test tomshexd tomsrtbt.FAQ touch traceroute true
tune2fs umount undeb-- unpack.s unrpm-- update utmp vi vi.help view watch
wc wget which xargs xirc2ps_cs yecho yes zcat

GNU/Linux package

clone.s duplicate
fdflush flush floppy cache
fdformat format floppy 1.7M
install.s install
settings.s used by tools
tomsrtbt.FAQ documentation
tomsrtbt.raw <== This is it
unpack.s unpack for rebuild

DOS package

initrd.img installer image
install.bat install it
loadlin.exe starts GNU/Linux from DOS
tomsrtbt.FAQ documentation
zimage installer kernel

Ok, I'm going to try this, I'm at my wit's end trying to figure it out and i dread redoing the os so going to try this today.

Wait a sec, this has me logging in as root and that's the whole problem, I CAN"T! this won't work

'Login as root' means the USER ID is "root"! When you load it, Toms will prompt you to enter a passwd (Toms is a filesystem on the disk which you log into as root. ) and will allow you into your system so that you can then mount the filesystem that contains the file you wish to fix (example: /etc/passwd). Search Google for Toms Root Boot and see for yourself. It will work wonders for you.