From owner-freebsd-doc Sun Jan 7 07:15:10 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA13502 for doc-outgoing; Sun, 7 Jan 1996 07:15:10 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA13484 for ; Sun, 7 Jan 1996 07:15:02 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id KAA17381; Sun, 7 Jan 1996 10:10:46 -0500 Date: Sun, 7 Jan 1996 10:10:45 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Peter da Silva cc: doc@freebsd.org Subject: Re: Has the copyright dust settled? In-Reply-To: <199601061501.JAA28361@bonkers.taronga.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Sat, 6 Jan 1996, Peter da Silva wrote: > In article , > Jonathan M. Bresler wrote: > > better to ask why computer once had only uppercase. this was > >not an engineering or ergonomics decision. a management bozo decided this. > > for the love of god. NO. THAT'S NOT CORRECT. IT WAS FOR THE LOVE OF GOD. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-doc Sun Jan 7 20:40:24 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA11704 for doc-outgoing; Sun, 7 Jan 1996 20:40:24 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA11699 for ; Sun, 7 Jan 1996 20:40:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id UAA21685 for ; Sun, 7 Jan 1996 20:39:58 -0800 To: doc@freebsd.org Subject: How do folks feel about legitimizing the `style split' in our docs? Date: Sun, 07 Jan 1996 20:39:58 -0800 Message-ID: <21683.821075998@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@freebsd.org Precedence: bulk "What the hell is he talking about?" they ask. I'm talking about our long-standing problem with having docs submitted in one of two fairly different styles: 1 "How to do this ..." 2 "How this work works ..." Contrast the difference between a driver's manual ("when you see a red light, STOP!") and an owner's manual ("If you open your hood, you'll a collection of hoses and mysterious chunks of metal - this is how they work and how to fix them when they stop"). Both can be extremely valuable during the period where you own and operate your car, but few would argue that there are many instances when they'd both be used at the same time, or even necessarily by the same people. However, despite the fact that much is also true for operating systems documentation, we've not seen fit to make two books out of it. Instead, we've smashed beginner's guides and expert docs together, resulting in The Handbook. If you try to read it from start to finish, you'll be presented with a bewildering array of stylistic twists and turns as you leave one author's section and move into another's. I would argue that this is not necessary, nor do we need to split the handbook in half. What I would argue for instead is a further level of subcategorization for every major topic, looking something like this: Subject Heading: E.g., you might have something like: 1.2. Network communications with SLIP Contributed by . SLIP is a serial point-to-point protocol for allowing remote hosts to speak TCP/IP to one another over dialup or hardwired links. It use has been largely superceded by PPP, but there are still situations where SLIP is useful. 11.2.1. How to set up SLIP 11.2.2. How SLIP works And the reader would have three `touchpoints' on the page. The intro if they have no idea what SLIP is ("am I even interested in this?"), the `How To' choice if they're definitely interested and need to know how to actually do it step-by-step, and the `How it works' choice if they're more interested in knowing how it all works (and possibly because they don't want step-by-step, they just want to know which parts of the system are "reponsible" for the feature in question). I have the feeling that if we could sweep large sections of the handbook into one category or the other, it would both make the whole thing a lot more readable, and it would point up (through the empty sub-sections) just where we were deficient in howto or hacker documentation. Comments? John, would something like this conflict significantly with your proposed reorg? Jordan From owner-freebsd-doc Sun Jan 7 21:17:32 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA13362 for doc-outgoing; Sun, 7 Jan 1996 21:17:32 -0800 (PST) Received: from localhost.lightside.com (user58.lightside.com [198.81.209.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA13357 for ; Sun, 7 Jan 1996 21:17:29 -0800 (PST) Received: (from jehamby@localhost) by localhost.lightside.com (8.6.12/8.6.9) id VAA00391; Sun, 7 Jan 1996 21:17:52 -0800 Date: Sun, 7 Jan 1996 21:17:28 -0800 (PST) From: Jake Hamby X-Sender: jehamby@localhost To: "Jordan K. Hubbard" cc: doc@freebsd.org Subject: Re: How do folks feel about legitimizing the `style split' in our docs? In-Reply-To: <21683.821075998@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Sun, 7 Jan 1996, Jordan K. Hubbard wrote: > "What the hell is he talking about?" they ask. > > I'm talking about our long-standing problem with having docs submitted > in one of two fairly different styles: > > 1 "How to do this ..." > > 2 "How this work works ..." > > [deletia...] > > Comments? John, would something like this conflict significantly with > your proposed reorg? Sounds like a good idea. I have two comments, though: First, I think that the Handbook SHOULD be split in the sense that the first section NEEDS to be focused for new users (assuming a mixture of readership between people new to Unix and experienced Unix admins new to FreeBSD). It needs to cover: 1) Which hardware is adequate/recommended to run FreeBSD on, 2) How to install it without clobbering your precious DOS partition, 3) How to perform basic sysadmin tasks and/or what books to read (we have the advantage over Linux in that we can say, "Just read this book and follow the SunOS/BSDI instructions," rather than "Linux is weird in almost every way, so buy a Linux-specific book or you'll be hopelessly confused"). :-) Second, some chapters are difficult to split in this way. Take "my" chapter, on Kernel Configuration (btw, John, I reread that for the first time in a few months, and I should do a bit of work on it, I'll post some diffs soon), anyway, rebuilding the kernel is something that every competent sysadmin should do, on the other hand the "how it works" is VERY intertwined with "how to do it." I doubt that anyone can "reorg" that chapter differently from how John and I settled on the layout, without making it less sensible than it is currently... So there is no hard and fast rule that will apply to every chapter. ------------------------------------------------------------------------------ Jake Hamby | E-Mail: jehamby@lightside.com Student, Cal Poly University, Pomona | System Administrator, JPL ------------------------------------------------------------------------------ From owner-freebsd-doc Sun Jan 7 21:31:18 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14063 for doc-outgoing; Sun, 7 Jan 1996 21:31:18 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA14058 for ; Sun, 7 Jan 1996 21:31:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA21954; Sun, 7 Jan 1996 21:30:51 -0800 To: Jake Hamby cc: doc@freebsd.org Subject: Re: How do folks feel about legitimizing the `style split' in our docs? In-reply-to: Your message of "Sun, 07 Jan 1996 21:17:28 PST." Date: Sun, 07 Jan 1996 21:30:51 -0800 Message-ID: <21952.821079051@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@freebsd.org Precedence: bulk > Sounds like a good idea. I have two comments, though: First, I think > that the Handbook SHOULD be split in the sense that the first section > NEEDS to be focused for new users (assuming a mixture of readership > between people new to Unix and experienced Unix admins new to FreeBSD). Well, I still don't see that as grounds for a "split" so much as a "beginner's section." I agree that the new users definitely need a blinking neon arrow pointing at *some* section of the handbook. > Second, some chapters are difficult to split in this way. Take "my" > chapter, on Kernel Configuration (btw, John, I reread that for the first OK, so I see that the paradigm breaks down for a few sections. Perhaps that simply points to the need for a (gag-inducing word coming up) meta-paradigm! :-) In english, what I'm saying is that perhaps we should extend the concept of howto/expert level documentation up one level then so that the novice users never even *see* your Kernel configuration document unless they follow a link that leads them over to the `How it works' section material. I mean, we've got this fancy SGML thingie, can't we make several `virtual documents' from the same source material? Why should we confine ourselves to one "top level representation" of The Handbook? Jordan From owner-freebsd-doc Mon Jan 8 08:07:45 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA17754 for doc-outgoing; Mon, 8 Jan 1996 08:07:45 -0800 (PST) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA17748 for ; Mon, 8 Jan 1996 08:07:39 -0800 (PST) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA27238; Mon, 8 Jan 96 10:07:38 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA10265; Mon, 8 Jan 1996 09:07:36 -0700 Date: Mon, 8 Jan 1996 09:07:36 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9601081607.AA10265@emu.fsl.noaa.gov> To: jkh@time.cdrom.com Cc: doc@freebsd.org In-Reply-To: <21683.821075998@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: How do folks feel about legitimizing the `style split' in our docs? Sender: owner-doc@freebsd.org Precedence: bulk >>>>> "Jordan" == Jordan K Hubbard writes: Jordan> "What the hell is he talking about?" they ask. Uh oh ... another Jordan diatribe. At least it'll be an amusing read :-) (Really, I'm kidding!) Jordan> I'm talking about our long-standing problem with having Jordan> docs submitted in one of two fairly different styles: Jordan> 1 "How to do this ..." Jordan> 2 "How this work works ..." Yes, I'll agree with this, to a point. There are some aspects of using and administrating an operating system where education about how it works is a lot more useful than step-by-step instructions on how to do something. Teaching someone how to set up an /etc/exports file goes quite smoothly with: ``1. Using your favorite text editor, ...'' Debugging why the fifth mountd request gets refused after hanging for ten minutes but only if there are two simultaneous X servers is definitely not served by ``1. Ummm, let's see, where could we begin?'' Jordan> Instead, we've smashed beginner's guides and expert docs Jordan> together, resulting in The Handbook. If you try to read Jordan> it from start to finish, you'll be presented with a Jordan> bewildering array of stylistic twists and turns as you Jordan> leave one author's section and move into another's. True. This is part of the reason why Don Knuth's _TeXbook_ fails. Despite the so-called dangerous bends, the beginner cannot determine how to make a report document with tables without skipping around a lot. The expert cannot determine why a marginal note is adding vertical glue to the main vertical list without skipping around a lot. Jordan> I would argue that this is not necessary, nor do we need Jordan> to split the handbook in half. What I would argue for Jordan> instead is a further level of subcategorization for every Jordan> major topic, looking something like this: Jordan> Subject Heading: Jordan> Jordan> Jordan> I like it. But the printed manual really should keep this material separate, lest we make the same TeXbook mistake. We should be able to identify SGML-wise which topics should end up in which book. Jordan> Comments? John, would something like this conflict Jordan> significantly with your proposed reorg? I must've missed the proposed reorg ... what's that all about? -- Sean Kelly NOAA Forecast Systems Laboratory, Boulder Colorado USA My girlfriend asked me how long I was going to be gone on this tour. I said, "the whole time." -- Steven Wright From owner-freebsd-doc Mon Jan 8 08:55:57 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20620 for doc-outgoing; Mon, 8 Jan 1996 08:55:57 -0800 (PST) Received: from cls.net (freeside.cls.de [192.129.50.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA20611 for ; Mon, 8 Jan 1996 08:55:50 -0800 (PST) Received: by mail.cls.net (Smail3.1.29.1) from allegro.lemis.de (192.109.197.134) with smtp id ; Mon, 8 Jan 96 16:55 GMT From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Reply-To: grog@lemis.de (Greg Lehey) Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id SAA00295; Mon, 8 Jan 1996 18:47:38 +0100 Message-Id: <199601081747.SAA00295@allegro.lemis.de> Subject: Re: How do folks feel about legitimizing the `style split' in our docs? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 8 Jan 1996 18:47:38 +0100 (MET) Cc: doc@FreeBSD.org In-Reply-To: <21952.821079051@time.cdrom.com> from "Jordan K. Hubbard" at Jan 7, 96 09:30:51 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-doc@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > (sorry, I was too lazy to copy the original message, but...) This is a thing that I've done a lot of soul-searching about. I agree with Jordan's original concerns, so much that I wouldn't be able to get a really good assessment in in time to be of use to anybody, so I'll give you a rough assessment. Basically, yes, we need both approaches. We probably need a larger number than 2. >> Sounds like a good idea. I have two comments, though: First, I think >> that the Handbook SHOULD be split in the sense that the first section >> NEEDS to be focused for new users (assuming a mixture of readership >> between people new to Unix and experienced Unix admins new to FreeBSD). > > Well, I still don't see that as grounds for a "split" so much as a > "beginner's section." I agree that the new users definitely need > a blinking neon arrow pointing at *some* section of the handbook. Pointers are devices which don't get enough use in books. I had a big fight with O'Reilly about my porting book, and lost. The result is a great loss to the book: I have lots of references in there, and instead of pointing to a page ("See Chapter 15, Signals, page 247" becomes "See Chapter 15, Signals, the section entitled "BSD signal handlers"). The result is that you either have to sequentially search the chapter (once you have found it, not the easiest thing in itself), or you go indirectly via the table of contents, also an inconvenience. In the "Installing FreeBSD" book (latest version, as of yesterday, is on freefall.FreeBSD.org:/incoming/shortbook.tar.gz, *please* review it and complain about everything except the appalling pagination), I have had even more of a problem. Take a look at Appendix A to see a possible way of handling the questions "To install FreeBSD you do if (installing_alone) { if (EIDE) lose (); if (ATAPI) maybe_lose (); if (sharing_disk) { if (MicroSoft ()) lose_lose_lose (); if (disk_already_contains_data ()) { FIPS (); maybe_win (); } } switch (media) { case CDROM: win (); case TAPE: maybe_lose (); case FLOPPY: mega_lose (); ... Well, you get the message. There are too many branches, and the result is that it's difficult to read. I've done what I can, but basically Appendix A really does try to call functions like this. All this verbosity leads in to: >> Second, some chapters are difficult to split in this way. Take "my" >> chapter, on Kernel Configuration (btw, John, I reread that for the first > > OK, so I see that the paradigm breaks down for a few sections. > Perhaps that simply points to the need for a (gag-inducing word coming > up) meta-paradigm! :-) In english, what I'm saying is that perhaps we > should extend the concept of howto/expert level documentation up one > level then so that the novice users never even *see* your Kernel > configuration document unless they follow a link that leads them over > to the `How it works' section material. Maybe you could think of a simpler word :-) > I mean, we've got this fancy SGML thingie, can't we make several > `virtual documents' from the same source material? Why should we > confine ourselves to one "top level representation" of The Handbook? This is the point. I'm not really happy with the way you navigate through HTML documents anyway (maybe I just don't understand them), but it should be possible to define several different ways to follow through, depending on what you want to do. I think a bit of brainstorming could come up with some useful innovation in this area. Greg From owner-freebsd-doc Mon Jan 8 15:07:40 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA16172 for doc-outgoing; Mon, 8 Jan 1996 15:07:40 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16160 for ; Mon, 8 Jan 1996 15:07:31 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id SAA00767; Mon, 8 Jan 1996 18:07:22 -0500 Date: Mon, 8 Jan 1996 18:07:22 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: Greg Lehey cc: "Jordan K. Hubbard" , doc@freebsd.org Subject: Re: How do folks feel about legitimizing the `style split' in our docs? In-Reply-To: <199601081747.SAA00295@allegro.lemis.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Mon, 8 Jan 1996, Greg Lehey wrote: > Jordan K. Hubbard writes: > > > > (sorry, I was too lazy to copy the original message, but...) > > This is a thing that I've done a lot of soul-searching about. I agree > with Jordan's original concerns, so much that I wouldn't be able to > get a really good assessment in in time to be of use to anybody, so > I'll give you a rough assessment. Basically, yes, we need both > approaches. We probably need a larger number than 2. First, as has been stated, The TeXBook approach is horrible. The TeXbook would have worked much better if all the `dangerous bends' were moved to a "part 2". HOWTO documents that provide a recipe for accomplishing a task typically do not provide the user with any transferable knowledge. They are also extremely fragile and can be completely derailed by the slightest complication. Running FreeBSD is certainly not without complications! If you try to take into account the most important complications, you end up with a mess as Greg illustrated with the installation document. At this point, we ponder: "Gee, if we told them how this thing works, they might be able to figure out how to get around these complications on their own!" Then reality intrudes: "People don't read documentation, and they certainly don't read documentation that does not appear to address the problem at hand. In all likelyhood, they might not even identify a how-it-works document as being relevant to their problem at all." In this dilemma, we have job security for technical writers. Although programmers won't hear of it, many documentation problems are really software design problems. For example, kernel configuration. The current state of affairs is similar to a person purchasing a car. On the lot it is configured in such a way that it can be driven off the lot. Once home, the user must then replace the transmission to effectively use the car. The analogy falls apart fairly quickly, but you get the idea. The user suddenly has to know what a transmission is, details about different sorts of transmission, how they work, and how to remove one and install another. Kernel configuration is similar. So, we write a document that explains the process, things that you can put in a file and such. We also warn the user of the more common ways they can shoot themself in the foot. People blunder through and sometimes come out with an operational kernel, but not after bothering everybody on the hackers and questions list. This is the Unix Way. In this case, I would argue that the documentation needs to be built into the process, and the process needs to be clarified. (Why do we rebuild kernels anyway?) Where redesign does not eliminate the need for documentation, the documentation should be supplied on a just-in-time basis. The right document when and where you need it and invisible the rest of the time. To my point, I believe that many of the HOWTO sorts of documents are most effective in this form because they can track what actually happens, making all the contingency plans as transparent as possible to the user.. As for the how it works documents, at this time, I don't think you can beat paper! I'm pessimistic about making anything but incremental improvements on the documentation front because implementing just-in-time documentation requires rethinking tool design, and rethinking it in a way that just might not go over too well with a large population of unix users who have already invested years of time in learning to use the system. > instead of pointing to a page ("See Chapter 15, Signals, page 247" > becomes "See Chapter 15, Signals, the section entitled "BSD signal > handlers"). The result is that you either have to sequentially search :( Blech. Did they give any reason? > This is the point. I'm not really happy with the way you navigate > through HTML documents anyway (maybe I just don't understand them), No, you understand them. It is suboptimal hypertext. Hypertext itself is a bit of a problem for us humans who can only keep 7 or so things in our head at a time. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Mon Jan 8 16:11:59 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA20389 for doc-outgoing; Mon, 8 Jan 1996 16:11:59 -0800 (PST) Received: from vector.jhs.local (slip139-92-42-148.emea.ibm.net [139.92.42.148]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA20374 for ; Mon, 8 Jan 1996 16:11:47 -0800 (PST) Received: (from jhs@localhost) by vector.jhs.local (8.7.3/8.6.9) id LAA01636; Mon, 8 Jan 1996 11:58:11 +0100 (MET) Date: Mon, 8 Jan 1996 11:58:11 +0100 (MET) From: "Julian Stacey jhs@freebsd.org" Message-Id: <199601081058.LAA01636@vector.jhs.local> To: doc@freebsd.org Subject: http://www.freebsd.org/~jhs/freebsd_people.html Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. (Internet Unix & C Consultants) Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (pending reconfig) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH [version 1.6.5 95 12 11] Sender: owner-doc@freebsd.org Precedence: bulk -------- Would now be a good time to adopt http://www.freebsd.org/~jhs/freebsd_people.html into the main tree ? (It's a page of faces, web addresses & email addresses for current@ users) I built it for use (hopefully) as a truly public page, & would like to hand it over. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-doc Mon Jan 8 23:48:30 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA18635 for doc-outgoing; Mon, 8 Jan 1996 23:48:30 -0800 (PST) Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA18595 for ; Mon, 8 Jan 1996 23:48:06 -0800 (PST) Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.7.1/8.6.4) with ESMTP id IAA03115 for ; Tue, 9 Jan 1996 08:48:02 +0100 (MET) Message-Id: <199601090748.IAA03115@lirmm.lirmm.fr> To: doc@freebsd.org Subject: NIS/YP Date: Tue, 09 Jan 1996 08:47:44 +0100 From: "Philippe Charnier" Sender: owner-doc@freebsd.org Precedence: bulk Hi, You will find enclosed an introduction to NIS that comes with a new file (nis.sgml) and 3 small patches needed to incorporate this file into the handbook. Please correct my english. Also note that if you decide to remove the ``Contributed .. '' do not remove the heading

, compilation will fail if you do. Have a nice day. -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ cvs diff: Diffing . Index: Makefile =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/share/doc/handbook/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile 1995/12/07 13:22:12 1.7 +++ Makefile 1996/01/06 23:46:42 @@ -6,7 +6,7 @@ SRCS+= firewalls.sgml glossary.sgml goals.sgml SRCS+= handbook.sgml history.sgml hw.sgml install.sgml kerberos.sgml SRCS+= kernelconfig.sgml kerneldebug.sgml memoryuse.sgml -SRCS+= mirrors.sgml nfs.sgml nutshell.sgml +SRCS+= mirrors.sgml nfs.sgml nis.sgml nutshell.sgml SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml relnotes.sgml SRCS+= routing.sgml scsi.sgml sections.sgml SRCS+= skey.sgml slipc.sgml slips.sgml submitters.sgml sup.sgml Index: handbook.sgml =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/share/doc/handbook/handbook.sgml,v retrieving revision 1.38 diff -u -r1.38 handbook.sgml --- handbook.sgml 1995/12/21 17:16:29 1.38 +++ handbook.sgml 1996/01/07 00:54:55 @@ -121,7 +121,7 @@ &routing; &nfs; &diskless; - * Yellow Pages/NIS + ⋼ * ISDN * Mail Index: sections.sgml =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/share/doc/handbook/sections.sgml,v retrieving revision 1.7 diff -u -r1.7 sections.sgml --- sections.sgml 1995/12/07 13:22:17 1.7 +++ sections.sgml 1996/01/07 00:55:07 @@ -28,6 +28,7 @@ + =================================================================== --- /dev/null Sat Jan 6 02:05:01 1996 +++ nis.sgml Sun Jan 7 02:07:02 1996 @@ -0,0 +1,49 @@ + + + +Yellow Pages/NIS + +

Contributed by Philippe Charnier <charnier@lirmm.fr>. + +The Network Information Service provides a way to distribute certain +system data files to a set of machines which are connected on the same +ethernet. A single copy of these files under YP are centrally +maintained on the YP server, and accessed by clients via the network +when needed. This permits a system administrator to set up NIS client +systems with only minimal configuration data and add, remove or modify +configuration data from a single location. The group of machines +containing the clients, the master server, and zero or more +slave servers (where the distributed files are replicated for +safety and are periodically updated by the master) is called an YP +domain.

+ +Note: on networks with a large number of hosts, it is often a +good idea to use a master server and several slaves rather than just a +single master server.

+ +The files that are commonly distributed through the yellow pages are +/etc/passwd and /etc/group. When a new user is added +in these files on the master server, the internal database must be +updated to take into account the changes. This is done through a +Makefile in /var/yp directory by running make in +that directory. As the changes are not done locally on the clients, +any request from users are transmitted to the server via the +yppasswd command instead of the passwd one. + +Note: on FreeBSD, the passwd command is smart enough +to call yppasswd when needed.

+ +The files /etc/passwd and /etc/group are special +cases: they are considered to be local. They are consulted first and +the YP server is queried for an entry only if they contain a magic +token `+' as the first character of the line (see passwd(5) +for more information about YP/NIS interaction).

+ +Some others files are directly queried from NIS database, ignoring +local copies. Have a look at /var/yp/Makefile for +examples.

+ +NIS master, slaves and clients are enabled on startup when +/etc/rc is run. Configuration is set according to the flags +you define by editing /etc/sysconfig. + From owner-freebsd-doc Tue Jan 9 10:36:01 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27158 for doc-outgoing; Tue, 9 Jan 1996 10:36:01 -0800 (PST) Received: from server.tnp.com (root@server.tnp.com [206.100.110.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27146 for ; Tue, 9 Jan 1996 10:35:49 -0800 (PST) Received: from sandp.tnp.com (tnp148.tnp.com [206.100.111.148]) by server.tnp.com (8.6.12/8.6.9) with SMTP id NAA00668 for ; Tue, 9 Jan 1996 13:57:36 -0500 Message-ID: <30F2B647.4BD7@tnp.com> Date: Tue, 09 Jan 1996 13:39:03 -0500 From: Albert Bryndza X-Mailer: Mozilla 2.0b3 (Win95; I) MIME-Version: 1.0 To: doc@freebsd.org Subject: installation problems X-URL: http://www.freebsd.org/handbook/handbook17.html#19 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk hi, i am trying to install the freebsd that i donwloaded from the net and it locks up at this point: npx0: INT 16 interface then just hangs there. i tried to disable probing npx0: with the -c option at bootup but it hangs after saying: npx0: probe diabled (or something close to that) what could be the problem? i am installing it on an ide drive (which it found) thank you, sandp@tnp.com From owner-freebsd-doc Tue Jan 9 21:09:24 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA06782 for doc-outgoing; Tue, 9 Jan 1996 21:09:24 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA06769 for ; Tue, 9 Jan 1996 21:09:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA03097 for ; Tue, 9 Jan 1996 21:08:32 -0800 Prev-Resent: Tue, 09 Jan 1996 21:08:31 -0800 Prev-Resent: "doc@freebsd.org " Received: from freefall.freebsd.org (freefall.cdrom.com [192.216.222.4]) by time.cdrom.com (8.6.12/8.6.9) with ESMTP id OAA02032 for ; Tue, 9 Jan 1996 14:34:58 -0800 Received: from localhost (daemon@localhost) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA08240 Tue, 9 Jan 1996 13:26:15 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA08201 for current-outgoing; Tue, 9 Jan 1996 13:25:58 -0800 (PST) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA08194 for ; Tue, 9 Jan 1996 13:25:55 -0800 (PST) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id PAA05709 for current@freebsd.org; Tue, 9 Jan 1996 15:25:49 -0600 Date: Tue, 9 Jan 1996 15:25:49 -0600 From: Jim Lowe Message-Id: <199601092125.PAA05709@miller.cs.uwm.edu> To: current@freebsd.org Subject: Overloaded PRINTER variable in bsd.doc.mk? Resent-To: doc@freebsd.org Resent-Date: Tue, 09 Jan 1996 21:08:31 -0800 Resent-Message-ID: <3095.821250511@time.cdrom.com> Resent-From: "Jordan K. Hubbard" Sender: owner-doc@freebsd.org Precedence: bulk It seems that the PRINTER environment variable in bsd.doc.mk has several uses. One use is for the groff/eqn -T and the other is for lpr -P. One other use for this is the way I use the PRINTER environment variable, namely to set up my default printer. If I don't unsetenv PRINTER before a I do a make in the doc src directory, it tries to ``groff -Tlp'' everything -- which of course fails miserably. This problem has been around for a while. Would it be possible to change the name of this environment variable in the bsd.doc.mk file to something other than PRINTER. It could possibly use two types of default devices (one for groff and one for lpr). PRINTER is probably fine for lpr, but not for the default groff/eqn type (possibly PRINTER_TYPE would be a good choice?). -Jim From owner-freebsd-doc Wed Jan 10 02:45:10 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA29313 for doc-outgoing; Wed, 10 Jan 1996 02:45:10 -0800 (PST) Received: from toadflax.cs.ucdavis.edu (toadflax.cs.ucdavis.edu [128.120.56.188]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA29308 for ; Wed, 10 Jan 1996 02:45:05 -0800 (PST) Received: by toadflax.cs.ucdavis.edu (4.1/UCD.CS.2.6) id AA20891; Wed, 10 Jan 96 02:44:55 PST From: obrien@cs.ucdavis.edu (David E. O'Brien) Message-Id: <9601101044.AA20891@toadflax.cs.ucdavis.edu> Subject: Re: Differentiating between 2.0 and 2.1 (fwd) To: doc@freebsd.org Date: Wed, 10 Jan 1996 02:44:54 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8b] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk ----- Forwarded message from J Wunsch ----- >From owner-freebsd-ports@freefall.freebsd.org Wed Jan 10 01:30:51 1996 From: J Wunsch Message-Id: <199601100646.HAA05265@uriah.heep.sax.de> Subject: Re: Differentiating between 2.0 and 2.1 To: dglo@SSEC.WISC.EDU (Dave Glowacki) Date: Wed, 10 Jan 1996 07:46:14 +0100 (MET) Cc: ports@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601100205.UAA03363@tick.SSEC.WISC.EDU> from "Dave Glowacki" at Jan 9, 96 08:05:56 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ports@FreeBSD.org Precedence: bulk [Charset: ISO-8859-1, skipping] ----- End of forwarded message from J Wunsch ----- From owner-freebsd-doc Wed Jan 10 08:24:20 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13871 for doc-outgoing; Wed, 10 Jan 1996 08:24:20 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13853 Wed, 10 Jan 1996 08:24:09 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id LAA05381; Wed, 10 Jan 1996 11:24:06 -0500 Date: Wed, 10 Jan 1996 11:24:05 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: Jim Lowe cc: current@FreeBSD.org, doc@FreeBSD.org Subject: Re: Overloaded PRINTER variable in bsd.doc.mk? In-Reply-To: <199601092125.PAA05709@miller.cs.uwm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.org Precedence: bulk On Tue, 9 Jan 1996, Jim Lowe wrote: > It seems that the PRINTER environment variable in bsd.doc.mk has > several uses. One use is for the groff/eqn -T and the other Yes, another name needs to be used. For bsd.sgml.mk I used FORMATS since not all output formats are intended to be printed. I had planed to change PRINTER to FORMATS in the bsd.doc.mk as well, but I'm certainly willing to entertain other possibilties. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Thu Jan 11 06:28:44 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA25280 for doc-outgoing; Thu, 11 Jan 1996 06:28:44 -0800 (PST) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA25274 Thu, 11 Jan 1996 06:28:41 -0800 (PST) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA24140; Thu, 11 Jan 96 08:28:39 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA04075; Thu, 11 Jan 1996 07:28:38 -0700 Date: Thu, 11 Jan 1996 07:28:38 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9601111428.AA04075@emu.fsl.noaa.gov> To: charlie_conklin@il.us.swissbank.com Cc: questions@freebsd.org, doc@freebsd.org In-Reply-To: <9601111144.AA01349@ln1d279nwk> (message from Charlie Conklin on Thu, 11 Jan 96 11:44:15 GMT) Subject: Re: lpt driver question Sender: owner-doc@freebsd.org Precedence: bulk >>>>> "Charlie" == Charlie Conklin writes: Charlie> Hello all... I have a simple piece of hardware that sits Charlie> on the PC printer port. I also have some C source code Charlie> that compiles and works, and is used to talk to that Charlie> hardware. The code looks fairly simple, basically just Charlie> poking a few values at an io port. Charlie> I am now faced with the task of making the hardware work Charlie> under FreeBSD instead of windows, and I realize that I do Charlie> not have the foggiest notion of how to proceed! You might want to examine /sys/i386/isa/tw.c; that's a device driver that uses the parallel port to talk to an X-10 TW523 power controller. It'd be nicer if it were a loadable kernel module, which is probably what you want your driver to be. There's supposed to be a guide to writing device drivers as part of the FreeBSD handbook, but I just checked the web site and it wasn't there. Does anyone know the status of this document? -- Sean Kelly NOAA Forecast Systems Laboratory, Boulder Colorado USA Even though I was their captive, the Indians allowed me quite a bit of freedom. I could walk about freely, make my own meals, and even hurl large rocks at their heads. It was only later that I discovered they were not Indians at all, but dirty clothes hampers. -- Deep Thoughts, by Jack Handey From owner-freebsd-doc Thu Jan 11 08:53:19 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA03709 for doc-outgoing; Thu, 11 Jan 1996 08:53:19 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA03701 for ; Thu, 11 Jan 1996 08:53:14 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id LAA04632; Thu, 11 Jan 1996 11:53:02 -0500 Date: Thu, 11 Jan 1996 11:53:01 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: Sean Kelly cc: charlie_conklin@il.us.swissbank.com, doc@freebsd.org Subject: Re: lpt driver question In-Reply-To: <9601111428.AA04075@emu.fsl.noaa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 11 Jan 1996, Sean Kelly wrote: > There's supposed to be a guide to writing device drivers as part of > the FreeBSD handbook, but I just checked the web site and it wasn't > there. Does anyone know the status of this document? I'd be glad to pull it into the handbook. Just say the word and provide me with the file! -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Thu Jan 11 11:16:15 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12132 for doc-outgoing; Thu, 11 Jan 1996 11:16:15 -0800 (PST) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12123 for ; Thu, 11 Jan 1996 11:16:07 -0800 (PST) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id UAA01791 for ; Thu, 11 Jan 1996 20:16:12 +0100 Received: by uni4nn.iaf.nl with UUCP id AA15733 (5.67b/IDA-1.5 for doc@freebsd.org); Thu, 11 Jan 1996 20:15:57 +0100 Received: by iafnl.es.iaf.nl with UUCP id AA23149 (5.65c/IDA-1.4.4); Thu, 11 Jan 1996 19:19:39 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.11/8.6.6) id TAA00246 for doc@freebsd.org; Thu, 11 Jan 1996 19:15:37 +0100 From: Wilko Bulte Message-Id: <199601111815.TAA00246@yedi.iaf.nl> Subject: adding to manpage set To: doc@freebsd.org (FreeBSD Doc Project) Date: Thu, 11 Jan 1996 19:15:36 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk Hi all Correct me if I'm wrong but I do have the impression there is something to be added to the set of man pages. I haven't yet seen 2.1R, but I expect the general situation to be similar to earlier releases. To improve on that, I'll volunteer to produce a list of missing pages. After a more or less complete list is compiled, we can than persue filling in the gaps. I myself intend to add to the 4 section, I did a number of driver man pages before. Request: please send me your 'missing' list, preferably with appropriate section and on which FreeBSD 2.x release your are missing it. Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-doc Thu Jan 11 12:07:09 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA15791 for doc-outgoing; Thu, 11 Jan 1996 12:07:09 -0800 (PST) Received: from spot.lodgenet.com (lodgenet.iw.net [204.157.148.88]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA15758 Thu, 11 Jan 1996 12:06:45 -0800 (PST) Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by spot.lodgenet.com (8.6.12/8.6.12) with ESMTP id OAA06864; Thu, 11 Jan 1996 14:06:44 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.12/8.6.12) with SMTP id OAA02906; Thu, 11 Jan 1996 14:18:16 -0600 Message-Id: <199601112018.OAA02906@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: kelly@fsl.noaa.gov (Sean Kelly) cc: charlie_conklin@il.us.swissbank.com, questions@freebsd.org, doc@freebsd.org Subject: Re: lpt driver question In-reply-to: Your message of "Thu, 11 Jan 1996 07:28:38 MST." <9601111428.AA04075@emu.fsl.noaa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 1996 14:18:16 -0600 From: "Eric L. Hernes" Sender: owner-doc@freebsd.org Precedence: bulk > > There's supposed to be a guide to writing device drivers as part of > the FreeBSD handbook, but I just checked the web site and it wasn't > there. Does anyone know the status of this document? > > Sean Kelly i've put yet another updated copy in http://www.freebsd.org/~erich sorry Sean but I don't have any of your edits in yet :(. john, the sgml is in freefall/~erich/public_html/ddwg.sgml It's got even more blanks to fill in, but the structure is better. Oh, yea and I'm sure it's still got plenty of typo/style errors :(, but it could be included in the handbook. btw, do I have commit privs to the docs? I've got 'em for ports, maybe there's no difference. eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-doc Thu Jan 11 13:22:51 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21114 for doc-outgoing; Thu, 11 Jan 1996 13:22:51 -0800 (PST) Received: from wireless.Stanford.EDU (wireless.Stanford.EDU [36.10.0.102]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA21107 for ; Thu, 11 Jan 1996 13:22:48 -0800 (PST) Received: (from akyol@localhost) by wireless.Stanford.EDU (8.6.12/8.6.6) id NAA08640; Thu, 11 Jan 1996 13:22:46 -0800 Date: Thu, 11 Jan 1996 13:22:46 -0800 (PST) From: Bora Akyol To: doc@freebsd.org Subject: Hylafax Configuration In-Reply-To: <199601111815.TAA00246@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk HI everyone, I am new to this mailing list. I have been using UNIX variants for years (including SunOS, IRIX and LINUX) and just switched to FreeBSD. My question is about hylafax, I would like to put together a HOWTO for hylafax while I am trying to get my system to work. So if there is any of you out there that has gotten this to work, please let me know how. Send me instructions, and I will put together a howto and submit it to the FreeBSD project. On the same subject, compared to Linux, the FreeBSD documentation is sparse, what kind of documentation is needed. On what topics? Thanks Bora ------------------------------------------------------------ Bora Aydin Akyol akyol@leland.stanford.edu ------------------------------------------------------------ From owner-freebsd-doc Thu Jan 11 15:36:48 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05579 for doc-outgoing; Thu, 11 Jan 1996 15:36:48 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05565 for ; Thu, 11 Jan 1996 15:36:36 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id SAA00361; Thu, 11 Jan 1996 18:35:21 -0500 Date: Thu, 11 Jan 1996 18:35:17 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: "Eric L. Hernes" cc: doc@freebsd.org Subject: Re: lpt driver question In-Reply-To: <199601112018.OAA02906@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 11 Jan 1996, Eric L. Hernes wrote: > It's got even more blanks to fill in, but the structure > is better. Oh, yea and I'm sure it's still got plenty > of typo/style errors :(, but it could be included in > the handbook. Okay, if you think they are ready for prime time! I'll try to sew it in sometime this weekend. After that you can work on it in place. > btw, do I have commit privs to the docs? > I've got 'em for ports, maybe there's no > difference. No difference that I know of. Just make sure you do a make on the handbook (or FAQ) before committing a change. If something broken goes in, it will automatically spam the WWW pages at 4:00am freefall time. 8*) -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Thu Jan 11 15:39:41 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05825 for doc-outgoing; Thu, 11 Jan 1996 15:39:41 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05813 for ; Thu, 11 Jan 1996 15:39:30 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id SAA00393; Thu, 11 Jan 1996 18:39:13 -0500 Date: Thu, 11 Jan 1996 18:39:13 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: Wilko Bulte cc: FreeBSD Doc Project Subject: Re: adding to manpage set In-Reply-To: <199601111815.TAA00246@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 11 Jan 1996, Wilko Bulte wrote: > Request: please send me your 'missing' list, preferably with appropriate > section and on which FreeBSD 2.x release your are missing it. Maybe this request should go out to hackers? -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Thu Jan 11 19:45:44 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA21721 for doc-outgoing; Thu, 11 Jan 1996 19:45:44 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA21716 for ; Thu, 11 Jan 1996 19:45:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id TAA00561; Thu, 11 Jan 1996 19:43:14 -0800 To: Wilko Bulte cc: doc@freebsd.org (FreeBSD Doc Project) Subject: Re: adding to manpage set In-reply-to: Your message of "Thu, 11 Jan 1996 19:15:36 +0100." <199601111815.TAA00246@yedi.iaf.nl> Date: Thu, 11 Jan 1996 19:43:14 -0800 Message-ID: <559.821418194@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@freebsd.org Precedence: bulk > Correct me if I'm wrong but I do have the impression there is something > to be added to the set of man pages. I haven't yet seen 2.1R, but I Your impression is correct. I and others occassionally add one that's missing, but there's no concerted effort. > Request: please send me your 'missing' list, preferably with appropriate > section and on which FreeBSD 2.x release your are missing it. You probably won't get too many replies to this, however, it being one of those "if we had enough time to search, we'd have enough time to fix them!" sorts of propositions. :-) I really recommend that you simply automate the process by iterating through every command in /sbin, /usr/sbin, /bin, /usr/bin and /usr/libexec, making sure that it has a man page in sections 1 or 8, through every library in /usr/lib and making sure that the functions are documented in sections 2 or 3, and through every file in /etc, making sure that the relevant files have docs in section 5. By the time you've finished that, we'll be pretty well doc'd and ready to take all the man pages and convert them to some other format.. :-) Jordan From owner-freebsd-doc Thu Jan 11 20:00:35 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA22853 for doc-outgoing; Thu, 11 Jan 1996 20:00:35 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA22835 Thu, 11 Jan 1996 20:00:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id TAA02660; Thu, 11 Jan 1996 19:59:47 -0800 To: "Eric L. Hernes" cc: kelly@fsl.noaa.gov (Sean Kelly), charlie_conklin@il.us.swissbank.com, questions@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: lpt driver question In-reply-to: Your message of "Thu, 11 Jan 1996 14:18:16 CST." <199601112018.OAA02906@jake.lodgenet.com> Date: Thu, 11 Jan 1996 19:59:47 -0800 Message-ID: <2658.821419187@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@FreeBSD.ORG Precedence: bulk > i've put yet another updated copy in http://www.freebsd.org/~erich Looking good! A little sparse in parts, and I certainly hope that someone volunteers to bring the PCI and PCCARD specs up to the level of the ISA specs, but it definitely looks to be a good start. > btw, do I have commit privs to the docs? > I've got 'em for ports, maybe there's no > difference. There's no difference. Jordan From owner-freebsd-doc Fri Jan 12 08:09:50 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA18602 for doc-outgoing; Fri, 12 Jan 1996 08:09:50 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA18595 for ; Fri, 12 Jan 1996 08:09:45 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id IAA21077; Fri, 12 Jan 1996 08:09:30 -0800 Date: Fri, 12 Jan 1996 08:09:29 -0800 (PST) From: Dave Walton To: John Fieber cc: Wilko Bulte , FreeBSD Doc Project Subject: Re: adding to manpage set In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 11 Jan 1996, John Fieber wrote: > On Thu, 11 Jan 1996, Wilko Bulte wrote: > > > Request: please send me your 'missing' list, preferably with appropriate > > section and on which FreeBSD 2.x release your are missing it. > > Maybe this request should go out to hackers? Someone in questions was just commenting that there don't seem to be any c++ manpages. Dave ========================================================================== David Walton Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-doc Fri Jan 12 23:23:49 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA11167 for doc-outgoing; Fri, 12 Jan 1996 23:23:49 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA11145 Fri, 12 Jan 1996 23:23:31 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id XAA00657; Fri, 12 Jan 1996 23:22:48 -0800 (PST) Date: Fri, 12 Jan 1996 23:22:48 -0800 (PST) Message-Id: <199601130722.XAA00657@silvia.HIP.Berkeley.EDU> To: jfieber@indiana.edu CC: james@miller.cs.uwm.edu, current@FreeBSD.org, doc@FreeBSD.org In-reply-to: (message from John Fieber on Wed, 10 Jan 1996 11:24:05 -0500 (EST)) Subject: Re: Overloaded PRINTER variable in bsd.doc.mk? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-doc@FreeBSD.org Precedence: bulk * change PRINTER to FORMATS in the bsd.doc.mk as well, but I'm certainly Go for it! Satoshi From owner-freebsd-doc Sat Jan 13 16:24:31 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28690 for doc-outgoing; Sat, 13 Jan 1996 16:24:31 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28664 for doc@freebsd.org; Sat, 13 Jan 1996 16:24:15 -0800 (PST) From: john@starfire.mn.org Message-Id: <199601140024.QAA28664@freefall.freebsd.org> Subject: updating part of the handbook To: doc@freebsd.org Date: Fri, 12 Jan 1996 16:06:00 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk I would like to update my NFS entry for the new mount parameters and to add additional information that I've learned since it was originally written. Should I do diffs against the html, or is there some other SGML DTD that generates the html, or what is the best comparison base? John Lind, Starfire Consulting Services E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417 From owner-freebsd-doc Sat Jan 13 23:44:40 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA19499 for doc-outgoing; Sat, 13 Jan 1996 23:44:40 -0800 (PST) Received: from portmac.midcoast.com.au (root@portmac.midcoast.com.au [203.12.28.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA19494 for ; Sat, 13 Jan 1996 23:44:33 -0800 (PST) Received: from techtrak.midcoast.com.au (techtrak.midcoast.com.au [203.18.218.87]) by portmac.midcoast.com.au (8.6.11/8.6.9) with SMTP id SAA03993 for ; Sun, 14 Jan 1996 18:45:56 +1100 Message-Id: <199601140745.SAA03993@portmac.midcoast.com.au> Date: Sun, 14 Jan 96 18:47:42 -0800 From: "Luis M. Huesch" Organization: TechTrak IT Consulting & Publishing X-Mailer: Mozilla 1.1N (Windows; I; 16bit) MIME-Version: 1.0 To: doc@FreeBSD.ORG Subject: help Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-doc@FreeBSD.ORG Precedence: bulk Hi, I'm new to this UNIX game and would like as much help as possible via pre-existing/emerging doc files. most obliged. Luis