From owner-freebsd-hackers Sun Jan 21 09:38:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA26395 for hackers-outgoing; Sun, 21 Jan 1996 09:38:54 -0800 (PST) Received: from fledge.watson.org (root@FLEDGE.RES.CMU.EDU [128.2.95.74]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA26390 Sun, 21 Jan 1996 09:38:51 -0800 (PST) Received: (from robert@localhost) by fledge.watson.org (8.6.12/8.6.10) id MAA02722; Sun, 21 Jan 1996 12:38:48 -0500 Date: Sun, 21 Jan 1996 12:38:48 -0500 (EST) From: Robert Watson To: John Fieber cc: Greg Lehey , FreeBSD Hackers , FreeBSD Documenters Subject: Re: What printed documentation do we need? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk I'd add a list of standard stuff, loosely based on a similar handbook provided by BSDI with BSD/OS of various versions. It might include: + How to use the man command, online help of other types -- an overview of lynx if it is the standard browser used now for the online handbook under a new installation. + Description of the file tree -- common locations for files, etc. Also perhaps a list of /etc config files, and a one line description of each, with a reference to the appropriate man page or handbook section. + Configuring ppp and internet connectivity + Adding users; information about the FreeBSD group, passwd, master.passwd, etc... Maybe information on NIS configuration as an appendix + Configuring serial terminals and dialup lines + Specific device issues such as - using a serial mouse under X - an overview of the kernel interactive configuration utility and a little on io ports and conflicts - an overview plus examples for recompiling the kernel to include common devices + a few pages on how to configure - a web server - a bootp server - ethernet cards + simple routing -- perhaps bootp client stuff, etc - anonymous ftp server - dns server Obviously a lot of this is covered in the FreeBSD handbook as is, but to have a simple few-pages guide to this would be great -- especially for a) new unix users and b) users experienced with different versions of unix who need some pointers to the particulars of BSD-style operating systems. Again, the BSDI handbook seems a good place to start looking for a quick guide reference. Not to say it's great for new users, just that in a small space it explains how to get most of the important details of internet connectivity and servers going. Having complete documentation in full form is good, but remembering my first experiences with running a BSD server (the first unix server type I ran) I remember spending a long time locating the configuration file I meant, or wondering how to set up a feature while help from more knowing sources came in. On Sun, 21 Jan 1996, John Fieber wrote: > On Sat, 20 Jan 1996, Greg Lehey wrote: > > > So, the question: which other documentation should be in paper form? > > For a gut feel, I'd say we could handle another 1500 to 2000 pages. > > *Personally* (and many have differing opinions), I like printed > documentation for > > * installation > * dump and restore > * fsck > * disklabel > * newfs > * maybe a couple others > > Or, more generally, for things you rarely use and consequently forget how > to use and, almost by definition, online documentation is unavailable when > you need them. > > I've got a couple other manual pages printed out, but on the whole, I > prefer to keep it online. Since its birth, I've only printed out the > Handbook once. > > As I said, others will have different opinions and I won't argue against > them. > > -john > > == jfieber@indiana.edu =========================================== > == http://fieber-john.campusview.indiana.edu/~jfieber ============ >