"Jenn V." <[EMAIL PROTECTED]> wrote:
> Robert Kiesling wrote:
> >
> > But not very much, since sysadminning requires experience as well as
> > the ability to read the instructions. (If not exactly nerves of
> > steel, if the folks on alt.sysadmin.recovery are to be taken
> > seriously. Make mine extra dry, please.)
> >
> > To answer your question: I suppose it would depend on the state of the
> > backups and the utilites that were still present on the system. (Of
> > course, on *modern* systems, we all have boot/root disks at the ready,
> > right?).
>
> Uhhh....
>
> But we do have three linux machines, all duplicates of the others.
> And while I can't put my hands on my boot disk without thinking, I
> know which husband/hacker had his hands on it and 'put it down
> somewhere'.
>
> But yes, sysadminning requires a 'never act in panic' state of
> mind.
Does that mean it's like being married? Really, I wasn't trying to be
rude.... Unix requires a different frame of mind than M$ Windows or
DOS. But systems are different and it's difficult to give good,
generic advice. If you were to have worked as a sysadmin in the
era/on the hardware that are described in the article that Telsa
referred to (which is one of my favorites, btw), you'd very likely
already have used 'sh' and 'echo' to restore a copy of the root file
system's superblock from one of it's backup locations. :)
Robert
************
[EMAIL PROTECTED] http://www.linuxchix.org
