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.
Subject:Re: Including third-party Linux documentation? From:John Cornellier <cornellier1 -at- stavanger -dot- oilfield -dot- slb -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 12 May 2003 14:27:30 +0200
Common practice is not to include OS documentation with a product.
Most *nix systems are pretty well documented in the man pages.
John Cornellier
2003-05-09 20:55:34, fbelton -at- octigabay -dot- com wrote:
>
>Hi all,
>
>I'm working on a new SysAdmin guide for users who will be Linux experts.
>
>Obviously I don't want to describe the Linux commands and syntax in great
>depth in my guide, but am wondering how to make sure all the bases are
>covered. Specifically:
>
>- Is it enough to say that users are expected to be Linux savvy in the
>document intro and leave it at that?
>
>- Or do some companies also package a basic "off-the-shelf" Linux manual
>with their own in-house manuals, and then simply refer to the
>off-the-shelf manual when appropriate?
>
>I'm interested in hearing how others have dealt with this issue.
>Thanks very much
>Fiona
---
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.