From owner-freebsd-doc Sun May 11 08:10:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA01095 for doc-outgoing; Sun, 11 May 1997 08:10:32 -0700 (PDT) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA01090 for ; Sun, 11 May 1997 08:10:28 -0700 (PDT) Received: from elec.isei.jrc.it (elec.jrc.it) by mrelay.jrc.it (4.1/EB-950131-C) id AA27026; Sun, 11 May 97 17:17:04 +0200 Received: from elect6 by elec.isei.jrc.it (4.1/EI-3.0m) id AA21079; Sun, 11 May 97 17:10:08 +0200 Posted-Date: Sun, 11 May 1997 17:09:06 +0200 Message-Id: <3375E112.103F@jrc.it> Date: Sun, 11 May 1997 17:09:06 +0200 From: Dirk-Willem van Gulik Organization: European Wide Service Exchange X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: freebsd-doc@FreeBSD.ORG, brian@awfulhak.org, nik@blueberry.co.uk Subject: PPP (user side) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is someone currently giving the user-side PPP section an over haul ? I just worked my way trhough it; as I was moving form kernel ppp to user ppp; and found the following things a bit lacking... Reading throuhg the ppp, handbook and ppp.conf.example files I missed the very common case of having a FreeBSD box acting as a dialin for a normal flat LAN, and where you want the dialin client to be proxy-ed onto the LAN with no routing or anything fancy. If so; please consider these additions.. (or let me know where to send them...) 13.1.2 If you plan to act as a PPP server or gateway between the machines connected over the PPP lines and your local area (ether)network; you will also have to enable the GATEWAY in the kernel; and quite possible the IPFIREWALL. Just add the lines options GATEWAY # options IPFIREWALL to the kernel configuration file. Unless you need it; do not enable the IPFIREWALL option. However in a lot of situations it is a very effective way to keep the PPP line clear of all kinds of traffic; and to ensure some rudimentory safety. If you add the IPFIREWALL option; do not forget to set the 'firewall' directive in sysconfig to YES; and to 'allow' some sort of traffic in the /etc/rc.firewall file. Uncommenting the line /sbin/ipfw add 65000 pass all from any to any will ensure that after a reboot one actually can make connections to and from the machine by opening up it completely again. * For reasons unclear to me; setting the * 'gateway' flag to YES in the /etc/sysconfig * file does not seem nessesary. 13.1.3 Additional check... Using 'ifconfig -a' should give an entry like tun0: flags=8050 mtu 1500 13.1.X Specific to dial-in user-PPP server on a normal LAN (with not nessesarily routing) where you want the LAN connected machine to fully proxy for the connected PPP box. This proxying implies that you propably do not have any decent routing on your site. And you might find it safer to disable/kill the routed/gated deamons during experimenting :-) Somewhere afterwards in a section ons etting up a user-ppp server; Check out the ppp command man-pages; in particular the section on RECEIVING INCOMING PPP CONNECTIONS Point 1; Some Additional hints for most/hayes modems; add a line like this to /etc/remote mymodem:dv=/dev/cuaa1:br#38400 Now you can easily access the modem with tip mymodem Try 'AT'; most hayes modems will give you an 'OK' back. If this is not the case, try ATZ or AT&F1 or ATE1Q0 This should reset or factory reset the modem or with the last command just enable echo and result strings so you can see what you do. See http://sckb.ucssc.indiana.edu/kb/data/aaqc.html for a summary. And check that you get the OK prompt on an 'AT'. Now switch off the 'echo back' and 'results strings' and set to modem to auto-answer after '5' rings. ATQ1ES0=5 and AT&W0 to program it into permanent memory. That should cause the modem to pick up the phone; even after being switched on and off. Point 2. You propably want to add a label; for example /usr/sbin/ppp -direct dialins and let that correspond to something like dialins: disable pap disable chap enable proxy set ifaddr 100.1.2.3 100.1.2.4 Where 100.1.2.3 is the server's address and 100.1.2.4 is the client. The 'enable proxy' line allows proxy forwarding. (The above is the simplest of examples; but that way it is easy to ensure that things work. Feel free to upgrade to dynamix things....) Now when testing things; a usefull command (after someone has dialed in) is ifconfig -a to see if there is a tunnel; you should see something like 100.0.0.1 -> 100.0.0.2 in the listing for the tun0 device. Furthermore with arp -a | grep proxy One can check/see if the machine is proxying the connected client correctly. Configurations used 1. Server-side kernel config tun 1 , GATEWAY 2. Client-side kernel config tun 1 3. server side /etc/passwd ppp:*:1003:1003:PPP Login User:/home/ppp:/usr/sbin/ppplogin 4. server side /etc/ppp/ppp.conf default: set device /dev/cuaa1 set speed 38400 disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" dialins: disable pap disable chap enable proxy set timeout 1200 set ifaddr 100.0.0.1 100.0.0.2 5. server side /usr/sbin/ppp.login #!/bin/sh /usr/sbin/ppp -direct dialins 6. client side /etc/ppp/ppp/conf default: set device /dev/cuaa1 set speed 38400 disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" set login "TIMEOUT 5 login:-\\r-login: \\U word: \\P PPP" dialup: set authname ppp set authkey mypasswordforppp set timeout 1200 dial 7. client side /etc/ppp/ppp.linkup MYADDR: add 0 0 HISADDR And that is it. Hope this helps someone. Dw. http://ewse.ceo.org http://enrm.ceo.org DWvGulik@Dialis.xs4all.nl Dirk.vanGulik@jrc.it +39 332 78 0014 +39 332 78 9549 fax +39 332 78 9185 ISEI/ESBA; The Center For Earth Observation Joint Research Centre of the European Communities, Ispra, Italy From owner-freebsd-doc Sun May 11 16:43:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA18406 for doc-outgoing; Sun, 11 May 1997 16:43:33 -0700 (PDT) Received: from mailbox.iwaynet.net (root@mailbox.iwaynet.net [198.30.29.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA18401 for ; Sun, 11 May 1997 16:43:30 -0700 (PDT) Received: from willy (port308.iwaynet.net [206.21.106.8]) by mailbox.iwaynet.net (8.8.5/8.7.3) with SMTP id TAA03516 for ; Sun, 11 May 1997 19:42:28 -0400 Message-Id: <199705112342.TAA03516@mailbox.iwaynet.net> Date: Sun, 11 May 97 19:42:13 -0700 From: mike X-Mailer: Mozilla 1.22 (Windows; I; 16bit) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: (no subject) Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-doc Mon May 12 06:43:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA10841 for doc-outgoing; Mon, 12 May 1997 06:43:25 -0700 (PDT) Received: from po.mitene.or.jp (ns1.mitene.or.jp [202.247.58.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10833 for ; Mon, 12 May 1997 06:43:11 -0700 (PDT) Received: from nor2 ([202.225.84.56]) by po.mitene.or.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id WAA04840 for ; Mon, 12 May 1997 22:43:19 +0900 (JST) Message-ID: <33771E62.90FDB65C@mitene.or.jp> Date: Mon, 12 May 1997 22:42:59 +0900 From: Norikazu Okakura X-Mailer: Mozilla 4.0b4 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: About Install-Boot-FD-98 X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-2022-jp Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 岡倉と申します。 現在ＮＥＣＰＣ−９８２１ＡＰ２で、ＦｒｅｅＢＳＤ２．１．０をインストール しようとしております。 そこで質問なのですが、２ＨＣのフロッピィーのようにＦＯＲＭＡＴとは、どう いうことなのでしょうか。 マニュアルには、ＮＥＣ版は、"format a: /5" と書いてありますが、"/5"とい うパラメータが NEC-DOS5.0A-Hには、ありません。"a:"というのがフロッピィーのドライブの意 味だと 言うことは分かりますが。。。 今、２ＨＤのフロッピィで、 nec-dos 1.2M nec-dos 1.44M dos/v(windowsnt4.0) 1.44M で、"rawrite"と入力しましたが、駄目でした。 つまり、２ＨＤのフロッピィで、この２ＨＣのＦＯＲＭＡＴを行いたいのです が、 どうすればよろしいのでしょうか？ From owner-freebsd-doc Mon May 12 09:28:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA19734 for doc-outgoing; Mon, 12 May 1997 09:28:58 -0700 (PDT) Received: from dutton4.it.siu.edu (dutton4.it.siu.edu [131.230.2.151]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19723 for ; Mon, 12 May 1997 09:28:55 -0700 (PDT) Received: from dutton4.it.siu.edu (localhost [127.0.0.1]) by dutton4.it.siu.edu (8.8.5/8.8.5) with ESMTP id LAA06781 for ; Mon, 12 May 1997 11:32:02 -0500 (CDT) Message-Id: <199705121632.LAA06781@dutton4.it.siu.edu> Date: Mon, 12 May 1997 11:31:58 -0500 (CDT) From: Jim Dutton Subject: Fwd: Re: comp.mail.sendmail Frequently Asked Questions (fwd) To: freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to help someone expand their FAQ capabilities similar to what y'all do. What do you use to generate your HTML docs and non-HTML docs? Thanks. ------ Forwarded message ------ From: jimd@slip106.termserv.siu.edu (Jim Dutton) Subject: Re: comp.mail.sendmail Frequently Asked Questions (fwd) Date: Sun, 11 May 1997 22:55:32 CST To: jimd@dutton4.it.siu.edu On May 10, Brad Knowles wrote: |-------------------- text of forwarded message follows --------------------| At 10:27 PM -0400 4/27/1997, Jim Dutton wrote: >I would like to ask that plus/minus signs or asterisks be used in the index to >denote new or changed items it would make the FAQ vastly more useful as then I >don't have to spend a lot of time rereading every "issue", just to find out >what has changed. Thanks. If I did anything with the current format, I'd do it with context diffs. However, I'm going to be doing a complete change of the FAQ when I "port" it over to using SGML-Tools (probably version 0.99.10 or later), so that the web page and text version can be generated from the same SGML source. At that point, since it will get regenerated each time, I don't know whether even context diffs would be able to help. If you can suggest a tool along the lines of SGML-Tools (where I could maintain one canonical source, and have that generate either HTML or text, with modifications to the actual output as appropriate for those formats), but which would also include some ability to retain a notion of what's "changed" since the last version, I'm all ears. -- Brad Knowles, MIME/PGP: brad@his.com comp.mail.sendmail FAQ Maintainer finger brad@his.com for my PGP Public Keys and Geek Code The comp.mail.sendmail FAQ is at |------------------------- end of forwarded message ------------------------| From owner-freebsd-doc Mon May 12 09:33:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA19995 for doc-outgoing; Mon, 12 May 1997 09:33:55 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19980 for ; Mon, 12 May 1997 09:33:48 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost.lan.awfulhak.org [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id RAA10749; Mon, 12 May 1997 17:32:38 +0100 (BST) Message-Id: <199705121632.RAA10749@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Dirk-Willem van Gulik cc: freebsd-doc@FreeBSD.ORG, brian@awfulhak.org, nik@blueberry.co.uk Subject: Re: PPP (user side) In-reply-to: Your message of "Sun, 11 May 1997 17:09:06 +0200." <3375E112.103F@jrc.it> Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 12 May 1997 17:32:38 +0100 From: Brian Somers Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is someone currently giving the user-side PPP section > an over haul ? I just worked my way trhough it; as I > was moving form kernel ppp to user ppp; and found > the following things a bit lacking... I guess I've got the hat on :) > Reading throuhg the ppp, handbook and ppp.conf.example > files I missed the very common case of having a FreeBSD > box acting as a dialin for a normal flat LAN, and where > you want the dialin client to be proxy-ed onto the LAN > with no routing or anything fancy. > > If so; please consider these additions.. (or let me > know where to send them...) The got to the right place :) > 13.1.2 > If you plan to act as a PPP server or gateway > between the machines connected over the PPP > lines and your local area (ether)network; you > will also have to enable the GATEWAY in the > kernel; and quite possible the IPFIREWALL. > > Just add the lines > > options GATEWAY > # options IPFIREWALL [.....] I've added a reference to the firewalls section, but "options GATEWAY" is no longer required. If you want to forward packets (this is what options gateway does), you just need to set the sysconfig (now rc.conf) variable. In your suggested files below, the "enable proxy" circumvents the need for forwarding (enable proxy does the forwarding inside ppp). > 13.1.3 Additional check... > > Using 'ifconfig -a' should give an entry like > > tun0: flags=8050 mtu 1500 Added. > 13.1.X Specific to dial-in user-PPP server on a normal > LAN (with not nessesarily routing) where you want > the LAN connected machine to fully proxy for the > connected PPP box. > [.....] Most of this stuff has turned into links to other bits of the handbook. > Configurations used > 1. Server-side kernel config > tun 1 , GATEWAY > 2. Client-side kernel config [.....] > And that is it. Hope this helps someone. Should do. Thanks for your contribution. > Dw. > > http://ewse.ceo.org http://enrm.ceo.org > DWvGulik@Dialis.xs4all.nl Dirk.vanGulik@jrc.it > +39 332 78 0014 +39 332 78 9549 > fax +39 332 78 9185 > > ISEI/ESBA; The Center For Earth Observation > Joint Research Centre of the European Communities, Ispra, Italy -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-doc Wed May 14 09:07:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16788 for doc-outgoing; Wed, 14 May 1997 09:07:24 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16781; Wed, 14 May 1997 09:07:18 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id LAA24898; Wed, 14 May 1997 11:06:11 -0500 (EST) Date: Wed, 14 May 1997 11:06:10 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Amancio Hasty cc: "Pedro F. Giffuni" , hackers@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Is Thot (WYSIWIG editor) for you? In-Reply-To: <199705140805.BAA03496@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 14 May 1997, Amancio Hasty wrote: > For sure the algorithms used in Thot are worth looking into. > > What I am pitching is for is that if Thot is good we can start advertising it > and hopefully standardize our internal documentation based on its format. > Internal documentation meaning things like : reports, articles, etc... It is important to make clear the difference between standardizing the *data* and standardizing the *application*. The computer industry on the whole has focused on the latter to the benefits of vendors and at great cost to the user. The typical user has a much greater investment in their data than in the software they used to create it, yet the data formats are only of secondary consideration. Breaking this dammaging tradition requires inverting the standard line of "does it work with my favorite application" and thinking about in terms of "does the application work with the data". For this to work, the data standard must be nailed down. This is where SGML, or possibly its recent offspring, XML, come in. SGML is application neutral, yet flexible enough for most any documentation task. It is rapidly gaining momentum as well. Corel WordPerfect, for example, is quite proficient at dealing with SGML documents and is even shipped with the Docbook DTD. Even Microsoft is drifting (slowly) toward SGML support. The critical thing is that SGML documents can be exchanged between all these tools with absolutely *no* markup loss or corruption. The same cannot be said for any other format that I'm aware of. Basically, understand the data, then write the application. My concern is that the focus here is on the application (Thot). About the application, from by brief exposure (via Amaya) the general model that Thot uses is seems to be conceptually compatible with SGML, but I don't know how well the compatibility carries down to the nitty gritty details. If it doesn't it shouldn't be too much of a stretch to fix it. However, a year or two ago I did a little research project on structure enforcing editors for both programming languages and human languages. The problem with all of them is that they tend to impose the structure of a *finish* program or document. The only time the program exists in that state is when you are done editing it. During the editing process, it is absolutely essential that an editor allows the authors to create and fiddle structurally/syntactically incorrect document fragments with ease. If not, the editor will hinder more than it helps. My only experience with Thot is through Amaya and my initial impression was that it would be a royal pain to actually write something with it. Other SGML editors are afflicted with similar problems. In my opinion, emacs+psgml strikes a nice balance by allowing you to check structure/syntax and get help on structure/syntax without actually imposing it in a dictatorial fashion. (...but I personally use nedit most of the time...) -john From owner-freebsd-doc Wed May 14 11:03:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24161 for doc-outgoing; Wed, 14 May 1997 11:03:42 -0700 (PDT) Received: from coconut.blueberry.co.uk ([194.70.52.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24152; Wed, 14 May 1997 11:03:33 -0700 (PDT) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id TAA03103; Wed, 14 May 1997 19:03:02 +0100 (BST) Message-ID: <19970514190302.20618@blueberry.co.uk> Date: Wed, 14 May 1997 19:03:02 +0100 From: Nik Clayton To: questions@freebsd.org Cc: doc@freebsd.org Subject: Re: Is Thot (WYSIWIG editor) for you? References: <14271.863600208@time.cdrom.com> <3379F24B.934@fps.biblos.unal.edu.co> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <3379F24B.934@fps.biblos.unal.edu.co>; from Pedro F. Giffuni on Wed, May 14, 1997 at 10:11:39AM -0700 Organization: Blueberry New Media Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, May 14, 1997 at 10:11:39AM -0700, Pedro F. Giffuni wrote: > Jordan K. Hubbard wrote: > > > > > What I am pitching is for is that if Thot is good we can start advertising it > > > and hopefully standardize our internal documentation based on its format. > > > Internal documentation meaning things like : reports, articles, etc... > > > > But we already have such a standard and it's called SGML.... > > SGML is a format, Thot is a toolset and an editor. Correct me if I'm > wrong, but I haven't seen a good SGML tool in our ports tree. Sort of right, sort of wrong. > Thot produces Latex and HTML. AFAIK HTML is a subset of SGML, so I > guess Thot fits into the "standard". My $0.02 follows. I haven't used Thot (no Motif license) but I have trawled the FTP site, and read the docs. Doubtless John Fieber will jump in if I have any of this wrong. SGML is a meta-language. It describes other languages. HTML is one language that can be described by SGML. There are many others. One of these others is called DocBook. Current thinking on the FreeBSD documentation project (of which I am not a member) is to move from using the LinuxDoc TeX format to writing documents marked up according to the DocBook style. Once this is done, HTML can be produced, as can plain text, PostScript and so on. DocBook is also *much* more expressive than HTML is. For example, a snippet of some docs I'm converting to DocBook (and will then be submitting to the project as a tutorial) is /var/tmp/root now contains all the files that should be placed in appropriate locations below /. You now have to go through each of these files, determining how they differ from your existing files. This is not a task that can be automated (at the moment). Note that some of the files that will have been installed in /var/tmp/root have a leading '.'. Make sure you use As you can see, there is extra markup in there to denote things like commands, and filenames. There are many, many more. This sort of verbosity in the markup is a Good Thing. It allows more useful searches of the information to be carried out. It makes it easier to ensure that information is presented consistently. And it retains as much semantic information about the documentation as possible. Eventually, *all* FreeBSD project documentation will be written with DocBook, in much the same way as it's currently written in LinuxDoc. What is needed, as far as I can tell, is a decent environment for editing these files. Ideally, it should :- 1 Understand an SGML DTD, and prevent you creating invalid documents according to the specification 2 Have an editor that makes editing DocBook as painless as possible. Drop down lists of styles. A sample 'WYSIWYG' display[1], that sort of thing 3 Make it easy to convert DocBook documents to other formats [1] I *know* this term cannot really be applied to semantic markup. However, an editor that supported variable-width fonts, allowed the tags to be hidden, showed different marked up sections in different colours/styles, and was user configurable, would be very handy. We don't have a one stop shop that does all that. Yet. The SGML tools take care of point 1. But they don't do it interactively. It's like writing code, you have the "Edit; Compile; Fix; Compile" cycle. We don't have anything close to 2. The nearest product, as far as I can tell, would be SoftQuad's Author/Editor, which doesn't run on Intel unices anyway (it does, however, work with Win3.1/95, how are the WINE folks getting on :-) ). More info on it at http://www.softquad.co.uk/products/authored/ If my understanding of Thot is correct, *Thot does not do this*. It uses it's own styles and is not SGML aware. Point 3 is handled. At least, I know of (and use) a DocBook -> HTML converter. DocBook -> Text can be kludged with Lynx. Right now, I do all this with Xemacs, the SGML tools that come with 2.2, back fitted to 2.1.7, and a Makefile to automate the conversions. It's not pretty, but it works. John Fieber's documentation at http://fallout.campusview.indiana.edu/‾jfieber/docbook/ was invaluable in getting me kickstarted. IMHO, what's needed is for people with an interest in the documentation to build a nice editing environment (based around whichever editor people feel most comfortable with), all the necessary tools, and some samples of documentation -- a cookbook, if you will -- that makes it simpler for people who have the urge to get involved. Plus, of course, documentation so that people can use this. Make it available as a package/port, and make sure it works across as many versions of FreeBSD as possible. I can do some of this. I could probably port the tools (tho' I've never attempted a port before). I could write some of the first-time user documentation. I could write sample documents to show the range of DocBook markup available. But, I can't do all of it. And I'm probably not qualified to anyway, since I have my own questions for the Doc project gurus to answer. Thoughts? I've cc'd this to the 'doc' mailing list, which is (I guess) where this sort of discussion should really be taking place, instead of on questions-. N -- --+=[ Blueberry Hill Blueberry New Media ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ Those who do not read Dilbert are doomed to repeat it ]ENTP From owner-freebsd-doc Wed May 14 17:29:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16826 for doc-outgoing; Wed, 14 May 1997 17:29:31 -0700 (PDT) Received: from Pkrw.tcn.net (Pkrw.tcn.net [199.166.4.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16818 for ; Wed, 14 May 1997 17:29:22 -0700 (PDT) Received: from localhost (krw@localhost) by Pkrw.tcn.net (8.8.5/8.8.5) with SMTP id UAA13345 for ; Wed, 14 May 1997 20:28:53 -0400 (EDT) X-Authentication-Warning: Pkrw.tcn.net: krw owned process doing -bs Date: Wed, 14 May 1997 20:28:52 -0400 (EDT) From: "Kenneth R. Westerback" To: freebsd-doc@freebsd.org Subject: A Troff Tutorial (usd:22) - hiding or not present Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am interested in poking about in the documentation for FreeBSD, learning how it is all generated. Eventually DocBook, etc. but it seems a lot is in troff (and from postings here DocBook -> troff seems to be preferred) and I can't seem to find any introductory material on troff. Is the document "A Troff Tutorial (usd:22)" as mentioned in /usr/share/doc/usd/contents.ascii.gz installed somewhere? Not to mention other documents from the BSD distribution. If not part of the FreeBSD distribution is the document available for downloading/printing anywhere? Or do I have to buy the O'Reilly 4.4BSD documents. Alternatively is there another Troff document/book that is recommended? ---- Ken From owner-freebsd-doc Wed May 14 20:30:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25297 for doc-outgoing; Wed, 14 May 1997 20:30:34 -0700 (PDT) Received: from yarrina.connect.com.au (yarrina.connect.com.au [192.189.54.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25288 for ; Wed, 14 May 1997 20:30:24 -0700 (PDT) Received: from aardvark (aardvark.apana.org.au [203.12.237.49]) by yarrina.connect.com.au with ESMTP id NAA05379 (8.8.5/IDA-1.6 for ); Thu, 15 May 1997 13:29:55 +1000 (EST) Received: from solsbury-hill.home (dialup-29.aardvark.apana.org.au [203.12.237.59]) by aardvark (8.8.4/8.6.9) with ESMTP id NAA20293 for ; Thu, 15 May 1997 13:29:50 +1000 Received: from solsbury-hill.home (localhost.home [127.0.0.1]) by solsbury-hill.home (8.7.5/8.7.3) with ESMTP id NAA01722 for ; Thu, 15 May 1997 13:29:24 +1000 (EST) Message-Id: <199705150329.NAA01722@solsbury-hill.home> X-Mailer: exmh version 2.0beta 12/23/96 From: Joel Sutton To: doc@FreeBSD.ORG Subject: Adding Colorado Jumbo 350 tape drive to Section 10.5.5.5 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 May 1997 13:29:24 +1000 Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings, I put together this little entry for Section 10.5.5.5 the other day. Could some please consider adding it to the handbook. A reply, no matter how short, on whether this has been accepted or not would be most appreciated. Thanks. Regards, Joel... [snip] Colorado Jumbo 350 The boot message identifier for this drive is "Colorado tape". This is a floppy controller, minicartridge tape drive. Native capacity is 125MB for the 307.51' tape and 170MB for the 425' tape without compression. Data transfer rate is 500Kbps. The drive is compatible with 307.51' QIC-80 tape cartridges with the current version of the ft driver. It is possible to use 425' tapes with a patch to the kernel source. Please email the reporter if you wish to try the 425' patch. Reported by: Joel Sutton From owner-freebsd-doc Thu May 15 11:41:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06696 for doc-outgoing; Thu, 15 May 1997 11:41:38 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06690 for ; Thu, 15 May 1997 11:41:36 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id LAA25956; Thu, 15 May 1997 11:41:25 -0700 (PDT) Date: Thu, 15 May 1997 11:41:24 -0700 (PDT) From: Annelise Anderson To: "Kenneth R. Westerback" cc: freebsd-doc@FreeBSD.ORG Subject: Re: A Troff Tutorial (usd:22) - hiding or not present In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 14 May 1997, Kenneth R. Westerback wrote: > I am interested in poking about in the documentation for FreeBSD, learning > how it is all generated. Eventually DocBook, etc. but > it seems a lot is in troff (and from postings here DocBook -> troff seems > to be preferred) and I can't seem to find any introductory material on > troff. > > Is the document "A Troff Tutorial (usd:22)" as mentioned in > /usr/share/doc/usd/contents.ascii.gz installed somewhere? Not to mention > other documents from the BSD distribution. If not part of the FreeBSD > distribution is the document available for downloading/printing anywhere? > Or do I have to buy the O'Reilly 4.4BSD documents. Alternatively is there > another Troff document/book that is recommended? The referenced troff tutorial doesn't seem to be on my installation of 2.2R either. I found a troff tutorial (by searching with altavista, as I recall) at http://csdeca.cs.missouri.edu/‾manager/LAB/troff.html. I also found another one that seems to be help for students on a particular system; I'll mail you that one if you want it. That was about it. Annelise > > ---- Ken > From owner-freebsd-doc Thu May 15 15:56:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22905 for doc-outgoing; Thu, 15 May 1997 15:56:32 -0700 (PDT) Received: from darius.concentric.net (darius.concentric.net [207.155.184.79]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22897 for ; Thu, 15 May 1997 15:56:29 -0700 (PDT) Received: from mcfeely.concentric.net (mcfeely.concentric.net [207.155.184.83]) by darius.concentric.net (8.8.5/(97/05/14 3.29)) id SAA21115; Thu, 15 May 1997 18:56:28 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from shag (ts002d24.sal-ut.concentric.net [206.173.156.60]) by mcfeely.concentric.net (8.8.5) id SAA10211; Thu, 15 May 1997 18:56:26 -0400 (EDT) Message-ID: <337B9467.6B99C7BC@cris.com> Date: Thu, 15 May 1997 16:55:35 -0600 From: Joshua Fielden Organization: Shaggy Enterprises X-Mailer: Mozilla 4.0b4 [en] (Win95; I) MIME-Version: 1.0 To: doc@FreeBSD.ORG Subject: (no subject) X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-doc Thu May 15 16:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25506 for doc-outgoing; Thu, 15 May 1997 16:57:31 -0700 (PDT) Received: from sonetcom.com (mail.sonetcom.com [207.48.53.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25501 for ; Thu, 15 May 1997 16:57:26 -0700 (PDT) Received: by sonetcom.com from localhost (router,SLmailNT V2.4); Thu, 15 May 1997 19:00:04 Central Daylight Time Received: by sonetcom.com from Carpus3597 (207.48.53.62::mail daemon; unverified,SLmailNT V2.4); Thu, 15 May 1997 19:00:03 Central Daylight Time From: "Carol Smith" To: Subject: please send me you handbood Date: Thu, 15 May 1997 19:01:02 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <19970515190004.09294799.in@sonetcom.com> Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Carpus3597@sonetcom.com From owner-freebsd-doc Fri May 16 03:10:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20321 for doc-outgoing; Fri, 16 May 1997 03:10:15 -0700 (PDT) Received: from nova.ru.com ([195.19.68.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20315 for ; Fri, 16 May 1997 03:10:09 -0700 (PDT) Received: (from root@localhost) by nova.ru.com (8.8.5/8.7.3) id OAA04224; Fri, 16 May 1997 14:10:03 +0400 (MSD) Date: Fri, 16 May 1997 14:10:03 +0400 (MSD) Message-Id: <199705161010.OAA04224@nova.ru.com> To: freebsd-doc@FreeBSD.ORG X-URL: file://localhost/usr/share/doc/handbook/handbook.html X-Mailer: Lynx, Version 2.6 From: aa@nova.ru.com Subject: file://localhost/usr/share/doc/handbook/handbook.html Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-doc Sat May 17 10:04:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02073 for doc-outgoing; Sat, 17 May 1997 10:04:50 -0700 (PDT) Received: from mailhub.cts.com (mailhub.cts.com [204.216.216.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA02066 for ; Sat, 17 May 1997 10:04:48 -0700 (PDT) Received: from crash.cts.com(really [192.188.72.17]) by mailhub.cts.com via smail with smtp id for ; Sat, 17 May 97 10:04:44 -0700 (PDT) (Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21) Received: from darx.dar.tisc.com by crash.cts.com with smtp (Smail3.1.29.1 #5) id m0wSmuN-0000VJC; Sat, 17 May 97 10:04 PDT Message-ID: <337DE542.167EB0E7@cts.com> Date: Sat, 17 May 1997 10:05:06 -0700 From: "David A. Roger" X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: NIS pages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I am looking for help on the setting up of NIS. In older handbook references found doing a search for "NIS FreeBSD" pages showup, but do not contain NIS info. What happened to NIS - Where can I look for help. The O'Reilly Book does not come close.. Please can you help direct me? David A. Roger dar@cts.com