From: Dan Cross <crossd@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix Systems Administration Texts
Date: Tue, 28 Feb 2023 21:34:33 -0500 [thread overview]
Message-ID: <CAEoi9W7KUYn2Z1jESPGK=qU5ysF3jmJk5R+D_s03njjFshi--w@mail.gmail.com> (raw)
In-Reply-To: <2cfef728-ef06-20e4-e29e-9a0c83af8334@gmail.com>
On Tue, Feb 28, 2023 at 8:38 PM Will Senn <will.senn@gmail.com> wrote:
> I'm curious about the experience of those of y'all who actually used them. Were there any early standouts and why did they stand out?
This is not going to be popular, but...
> Nemeth, E., Synder, G., & Seebass, S. (1989). UNIX System Administration Handbook (5th edition is another fatty)
This book gave me some terrible advice when I was very young and impressionable.
In there somewhere it says something about not doing something unless
you're prepared to do it right lest one spend more time working around
a work-around than one would have spent just doing it well in the
first place.
The conclusion is, of course, true, but the admonition ignores all
sorts of externalities, like waiting users. And in some cases it could
really lead to paralysis ("omg _everything_ is broken and I can't do X
until I do Y, but to do Y I have to do this other thing and if I
really want to do it right I need to start by traveling to Nepal and
shaving this Yak, but I need to get my passport renewed and damn I
really oughta lose 20 pounds before I get my passport photo taken for
the next ten years, so I guess I oughta join a gym...but I can't even
find one because the network is down and I can't get to Google, but
how can I fix the network if I have not shaved the Nepalese yak?!").
Talk about letting the perfect be the enemy of the good.
Hopefully nowadays we have a better appreciation of the power of
incrementalism; those grand plans for the perfect system rarely come
to fruition. It's better to be flexible and make small, impactful
changes along the way towards a better system, always being mindful of
and tamping down encroaching entropy.
- Dan C.
next prev parent reply other threads:[~2023-03-01 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 1:38 [TUHS] " Will Senn
2023-03-01 2:34 ` Dan Cross [this message]
2023-03-01 3:24 ` [TUHS] " Larry McVoy
2023-03-01 9:03 ` steve jenkin
2023-03-01 18:34 ` Pete Wright via TUHS
2023-03-01 22:57 ` Alan D. Salewski
2023-03-02 0:41 ` Adam Thornton
2023-03-02 2:02 ` Jan Schaumann via TUHS
2023-03-01 8:34 ` steve jenkin
2023-03-01 18:41 ` Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEoi9W7KUYn2Z1jESPGK=qU5ysF3jmJk5R+D_s03njjFshi--w@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).