Thank you for your reply. I really appreciate your effort.
Vidiot wrote:
Excuse me, but if the boot fails, how were you able to start up aI have a very small RH 6.2 install on the same hard drive as Win95 at hda5, the large RH install that won't boot is on hdc1. I can boot RH on hda5 and look at any dir or file on hdc1, even edit and save it back to the same location on hdc1. Haven't you ever used a small maintenance install? I keep one for all three OS's on my box.
shell session and look at the file systems?
They aren't "flags." If you do a "ls -la /etc/rc.d" you'll see where theOk, that may be. I apologize for my structured programming terminology. I'm not sure what happened or how it happened. It was working fine, I shut it down and booted Win95 and used it for four or five days then tried to boot RH on hdc1 and found this problem. No manual changes were made to either OS by me and no one else has access. I haven't setup email on that install yet so I doubt I have a Linux virus but since I have accessed the web, I suppose it's possible. But doesn't a virus usually delete key files, like boot data? Looking at the files, they all seem to be there. By comparing the /etc and /boot dirs (they were almost identical immediately after installation and still are) is how I found that /etc/rc.d was different. Everything I've read so far says to edit the files in /etc/rc.d/rcx.d to change the boot process so that's where I looked.
link points. It wasn't a "flag" that changed the situation, the filesystem
was restructured.
Please find a Unix book that explains file systems,I'd really like to. In fact, so far, I've bought four but they seem to 'dance' around the actual heart of the subject. The only good book I've got is Linux in a Nutshell by Ellen Siever from O'Reilly. It's great for checking syntax, if you know the command to check. Can you recommend a good Linux book that explains file systems and other aspects of the OS?
it will help you understand your problem.
BTW, you may have worse problems, as init is supposed to be in /sbin.You may be correct but I hope not. I will check /sbin. I am assuming (I hate that word) that since I can browse the partition and edit and save files that my problem is correctable as long as I can find the actual cause.
Thank you.
