From owner-freebsd-doc Thu Jan 6 12:21: 6 2000 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 4BBD315768 for ; Thu, 6 Jan 2000 12:20:24 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id QAA26926; Thu, 6 Jan 2000 16:38:20 GMT (envelope-from nik) Date: Thu, 6 Jan 2000 16:38:20 +0000 From: Nik Clayton To: Ean Kingston Cc: Acadix Software Systems , freebsd-doc@FreeBSD.ORG Subject: Re: ZIP Drive doc for handbook Message-ID: <20000106163820.A25389@catkin.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Ean Kingston on Thu, Jan 06, 2000 at 09:54:34AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jan 06, 2000 at 09:54:34AM -0500, Ean Kingston wrote: > I recently started working on the Zip drive part of the handbook. This > does not prevent anyone else from writing for that section of the book. > Since you certainly had more problems getting your Zip drive to work then > I did mine, you have much more information on what can go wrong and how to > fix it then I do. At the very least I will be using your paper as a > reference (and giving you credit) and with your permission I will > integrate my efforts with yours for the final Zip drive section. Of > course, if you give that permission, you would then be associated with the > FreeBSD Documentation project :-) FWIW, I think there can be room for both kinds of document. As well as 'cannabilising' it for parts, as it were, it could pretty much move wholesale in to the tutorials section. Thoughts? N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message