TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> Before you agree to anything, make sure the persons asking you to take this
> on understand that this will eat a good chunk of production time (at first,
> anyway). Just make sure you realize what you are committing yourself to,
> and be careful not to spread yourself too thin.
You may also need to talk about security issues. If someone breaking into
that server would be a major disaster, then either they shouldn't use an
inexperienced admin, or you'll need a lot of help. Look at www.sans.org
for some training courses and other good info.
If at all possible, try to get your server installed behind a firewall run
by experts. Ask them to lock down the firewall so nothing except web stuff
and SSH (for your admin work and file transfers) reaches your server. This
takes a lot of the security worry off you.
If security is important and they expect you to do this without help, don't
take the responsibility. Something will almost certainly hit that fan at
some point, so don't stand next to it.
> If this is an NT file server, that is about the easiest server to set up and
> maintain. Find any good book on NT server and have at it.
Perhaps, if you're familar with Windows and security isn't a big issue.
Otherwise, I'd say use Unix.
> If it's an inexpensive Unix server your needing, I might suggest FreeBSD
> over Linux. Linux gets more hype, definitely, but FreeBSD is, in my opinion
> anyway, a more stable server platform
I'd have said Linux because it is more widespread and easier to get help on
(a weak argument; anyone who can work on one Unix can learn another easily)
and because I prefer it. However, if you need stability, avoid the bleeding
edge. Don't use Redhat 7 or 2.4 kernels.
OpenBSD, FreeBSD or NetBSD should be fine too. Of those, I'd choose OpenBSD
because they are really serious about security.
> (the sources are still based on the old System V code from the 60s).
No. System V was an early 80s AT&T product. BSD 4.2 users at the time sold
posters saying "4.2 > V". I still have one on my wall.
Neither Linux nor any of the *BSD's are based on any AT&T code. If anything,
Linux is closer to System V in design than the *BSDs are.
> Yahoo runs on FreeBSD.
Yes, as do some other large sites like cdrom.com.
> If you are going this route, and intend to use Samba for file service, get
> the O'Reilly book on Samba.
I'm not sure this is relevant.
Samba is a Linux implementation of SMB, the windows protocol for file, printer,
etc. sharing. It might be relevant if you're in a Windows shop, but even there
you can transfer files in other ways.
However, "get the O'Reilly book" is excellent advice for almost anything you
need to do on Unix and some things on other systems.
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by ForeFront, Inc., maker of ForeHelp Help authoring tools
for print, WinHelp, HTML Help, JavaHelp, and cross-platform InterHelp
See www.forehelp.com for more information and free evaluation downloads
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.