Telsa Gwynne <[EMAIL PROTECTED]> wrote:
>
> That's one of the reasons I like that article. As well as giving
> a presumably slightly outdated tale of woe and recovery, it gives
> an idea of how you might think about such a problem and get around
> it. (So it seems to me, speaking from the outside of this mindset,
> at least.) And I think that's the key skill, which is useful and
> transferable across different architectures and scenarios.
Yes, agreed. Unix and derivatives aren't closed systems like M$,
Novell, and others, are. One always has to think of what other
processes, users, hosts, etc., are being affected by the commands she
types. There's quite a difference between having complete control of
the system, or only part of it. One has to be mindful of the
resources being used by other users (even if it's only a cron job).
Robert
************
[EMAIL PROTECTED] http://www.linuxchix.org
