Yeah, I was looking at that too. Turns out the kill-file didn't have any more executive privilege than rm ! And frustratingly, the rmdir is not implemented yet!
Anyhow, I ran fsck again from insidethe debug shell, and this time it fixed things. Running fsck changed /setiold//var/loc to /setiold/.var.loc and /setiold//dev/log into /setiold/.dev.log, at which point the system rebooted and I could delete them. I don't know why it didn't do it first time, but I guess I'm not going to worry about it, now it's working.
I ran fsck one more time and tidied up the rest of carnage from the bad restart, and it all appears to be OK now.
Now I can upgrade 7.2 to 9, which is what I was trying to do in the first place.
Cheers,
julian. ============================== At 04:47 PM 6/29/03, you wrote:
Hi Julian,
> As a result of an unclean shutdown, I have some rogue files on my 7.2 > installation, which are preventing a complete boot up.
Have a look at debugfs (in e2fsprogs). I have no experience using it but the
kill_file command sounds promising.
Bye, Leonard.
-- How clean is a war when you shoot around nukelar waste? Stop the use of depleted uranium ammo! End all weapons of mass destruction.
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
