From: Pete Wright via TUHS <tuhs@tuhs.org>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix Systems Administration Texts
Date: Wed, 1 Mar 2023 10:34:52 -0800 [thread overview]
Message-ID: <20230301183452.rcf6rftetpgfmree@topanga> (raw)
In-Reply-To: <CAEoi9W7KUYn2Z1jESPGK=qU5ysF3jmJk5R+D_s03njjFshi--w@mail.gmail.com>
On Tue, Feb 28, 2023 at 09:34:33PM -0500, Dan Cross wrote:
> 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.
>
i'll agree here with you on that, but i will say that as a front line sysadmin
at the time it was one of the few resources i had that covered how to do basic
tasks correctly across many unix systems. it helped me alot as a sysadmin for
hire early in my career - esp when i had to fix something at a site with a poorly
maintained unix i may not have had much experience with at the time - "sure i can
fix your print spooler running hpux".
-pete
--
Pete Wright
pete@nomadlogic.org
next prev parent reply other threads:[~2023-03-01 18: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 ` [TUHS] " Dan Cross
2023-03-01 3:24 ` Larry McVoy
2023-03-01 9:03 ` steve jenkin
2023-03-01 18:34 ` Pete Wright via TUHS [this message]
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=20230301183452.rcf6rftetpgfmree@topanga \
--to=tuhs@tuhs.org \
--cc=crossd@gmail.com \
--cc=pete@nomadlogic.org \
/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).