Date: Sat, 6 Apr 2002 20:24:28 -0500 From: Garrett Rooney <rooneg@electricjellyfish.net> To: Tom Rhodes <darklogik@pittgoth.com> Cc: murray@stokely.org, keramida@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG Subject: Re: Splitting the Handbook? (was: [a couple of new doc PRs]) Message-ID: <20020407012427.GB98779@electricjellyfish.net> In-Reply-To: <20020406200938.23dd2ef4.darklogik@pittgoth.com> References: <20020404062954.6607E2E827@mail.freebsdmall.com> <20020406221709.GA1181@hades.hell.gr> <20020406231126.GP5732@freebsdmall.com> <20020406190204.21cad8a8.darklogik@pittgoth.com> <20020407001148.GA8008@freebsdmall.com> <20020406200938.23dd2ef4.darklogik@pittgoth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 06, 2002 at 08:09:38PM -0500, Tom Rhodes wrote: > On Sat, 6 Apr 2002 16:11:48 -0800 > murray@stokely.org wrote: > > > On Sat, Apr 06, 2002 at 07:02:04PM -0500, Tom Rhodes wrote: > > > And so on, each book should contain: > > > > > > Ports and packages installation > > > System Installation and Configuration > > > Rebuilding your Kernel > > > Staying up to date *cutting edge* (some people may want this) > > > > That is over 130 pages of content. I do NOT think all of that > > material should be repeated in each book. That material should just > > be in the "Getting Started" guide, or other appropriately named > > guides. > > I figured, and yes I know ``figured'' is not usually the best way to > go, but anyway I figured it would probly be helpful for people. But > this would need more discussing. What I mainly am getting at, is that > it might not be the best idea for that information to only be in one > printed book, as it could pertain to new users and competant sysadmins > at the same time... Thoughts? personally, it seems like the problem is in the definition of 'user' and 'sysadmin'. from my point of view, packages, building a kernel, staying up to date with cvsup, these are all 'sysadmin' type activities, and it's just the fact that many users happen to admin their own machines that make it useful to users. if i had to make the call, i'd say put it in the admin manual, and make the user manual something targeted toward someone who's just using the system, not running it. people who need to know how to perform the admin tasks, even the simple ones like these, are probably going to need at least some of the more complicated stuff later, so having the admin manual will probably pay off for them in the end anyway. -garrett -- garrett rooney Remember, any design flaw you're rooneg@electricjellyfish.net sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020407012427.GB98779>