home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!darwin.sura.net!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!nsisrv!tron!css
- From: css@tron.stx.com (Chris Shenton)
- Subject: Re: Breaking in to Unix admin. Need Suggestions!!
- In-Reply-To: weave@apache.dtcc.edu's message of 13 Nov 1992 13: 12:36 -0500
- Message-ID: <CSS.92Nov13142447@tron.stx.com>
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: tron.stx.com
- Organization: Hughes/STX, Lanham, MD
- References: <74707@hydra.gatech.EDU> <1e0r6kINN110@apache.dtcc.edu>
- Distribution: na
- Date: Fri, 13 Nov 1992 19:24:47 GMT
- Lines: 21
-
- As previous posters have indicated, the best way to learn it is to do
- it. Getting a cheap Sun 3, or perhaps throwing Linux (free) on your
- 386 would be a help. (You do have an underutilized intel box, don't
- you? :-)
-
- I found _UNIX_System_Administration_Handbook_ by Nemeth, Snyder,
- Seebass to be a very good overview of the sysadm chores. Lots of
- detail, etc. This would be a good place to start for an idea of where
- things live (eg: filesystem organization) and how to configure stuff
- (eg: sendmail, printers).
-
- It's not really oriented toward troubleshooting, but it will arm you
- with enough information so that you can make intelligent decisions on
- where to look for problems in a confused system.
-
- By the way, sysadm-ing is *not* a glorious job: it's completely
- thankless -- people just bitch when something goes wrong. On the other
- hand, you'll know more about UNIX and networking, most likely on a
- variety of platforms, than anyone else around you.
-
- Good luck.
-