>
> >> >Just went throughh that yesterday, RHL 6.3. I'm not competent to run that
> >> >wretched program in manuam mode, and I doubth that anyone on this list is.
> >>
> >> What is so hard about fsck? Has anyone actually read the
> >> manpage? If not, then I can see it being difficult, but after
> >> being bitten once by it, I'd assume a competant admin would do a
> >> "man fsck", "man e2fsck". It really isn't hard at all.
> >
> >It's extremely difficult to read manpages when your comptuter is half-booted.
>
> No, you misunderstand.. I meant, read it _now_, and print it out
> if need be. Learn to use the command, write out a simple cheat
> sheet and stick it to the monitor if need be. fsck is a fact of
> life right now. No matter how much you may hate it or dislike
> the idea of learning how to use it, the options are: learn to
> use it, or format the partition and restart over? Considering it
> takes anywhere from 40 minutes to several hours to reinstall and
> reconfigure everything each time, spending 10-30 minutes to learn
> how to use fsck and print out the manpage is nothing. That was
> my main point. I'm just trying to offer help to the real
> solution thats all. Nobody has to follow it.. ;o)
>
Knowing fsck is useless because the real problem is that it gives you
messages like "inode 43200 has such problem do you want I do this?".
Now hhow do you know what is inode 43200? You are not in normal mode
with a process controlling the terminal so CTRL-C and CTRL-Z are
unavailable and that means you cannot suspend fsck and use find to
know what is this inode. In addition the partition is not even
mounted. All you can do is answer blindly.
--
Jean Francois Martinez
Project Independence: Linux for the Masses
http://www.independence.seul.org
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
