From owner-freebsd-doc Sun Sep 22 07:46:45 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21611 for doc-outgoing; Sun, 22 Sep 1996 07:46:45 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21500 for ; Sun, 22 Sep 1996 07:46:26 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.5/8.6.9) with SMTP id AAA03979; Mon, 23 Sep 1996 00:42:25 GMT Date: Mon, 23 Sep 1996 00:42:24 +0000 () From: David Nugent To: "Jordan K. Hubbard" cc: Darren Davis , doc@FreeBSD.org Subject: Re: What tool to use to generate SGML? - Reply In-Reply-To: <19713.843245803@time.cdrom.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 Fri, 20 Sep 1996, Jordan K. Hubbard wrote: >> I guess the real question is do you do the SGML tags by hand and if so, >> geez I thought we got away from nroff/troff! I saw the posting about using >> an editing mode on EMACS, but was hoping for something a little more like >> a freeware Frame. OK, maybe I am wishing a little too hard. > >Yep. :) If it helps, I'm currently working on an SGML editing mode for jed/xjed based on its existing HTML assist. Full tag highlighting in colour, xterm or text mode. I'll post the announce on this list when it's ready. Regards, David David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-doc Sun Sep 22 09:44:53 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15317 for doc-outgoing; Sun, 22 Sep 1996 09:44:53 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA15263 for ; Sun, 22 Sep 1996 09:44:42 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id SAA12074; Sun, 22 Sep 1996 18:00:43 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id QAA23185; Sun, 22 Sep 1996 16:25:28 +0200 (MET DST) Date: Sun, 22 Sep 1996 16:25:28 +0200 (MET DST) From: Andreas Klemm To: Bill Lloyd cc: doc@freebsd.org Subject: Re: isdn documentation changes In-Reply-To: <32443F29.7604@mpd.ca> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Bill Lloyd wrote: > I have written up a more complete set of pages for the isdn section of > the handbook. I do not subscribe to the doc mailing list, so please cc > feeback to me directly. Ok, fine ! > Currently all (passive) Teles cards and their clones are supported for > the > EuroISDN (DSS1) and 1TR6 protocols. Another card is supported as well: Dr. Neuhaus - Niccy 1016 > The latest source can be found on the above mentioned ftp server under > directory isdn as file bisdn-096.tar.gz. 097 is the latest release. You should mention what the driver supports: Protocol: - raw hdlc framing What's currently not supported / gotchas: - no ppp, so no conection to CISCO's, but Netgw router and such, which support raw hdlc framing - multiple cards are not handeled by the driver - no channel bundling - no bandwidth on demand -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-doc Sun Sep 22 22:18:20 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA28228 for doc-outgoing; Sun, 22 Sep 1996 22:18:20 -0700 (PDT) Received: from natsiq.nunanet.com (root@natsiq.nunanet.com [199.247.47.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA28144 for ; Sun, 22 Sep 1996 22:18:12 -0700 (PDT) Received: from ppp-150.nunanet.com(really [199.247.47.150]) by natsiq.nunanet.com via sendmail with smtp id for ; Mon, 23 Sep 96 01:17:21 -0400 (EDT) (Smail-3.1.93 1996-May-30 #3 built 1996-Jun-18) Message-ID: <324648E1.F49@nunanet.com> Date: Mon, 23 Sep 1996 01:22:57 -0700 From: Peter Baril X-Mailer: Mozilla 3.0b6 (Win95; I; 16bit) MIME-Version: 1.0 To: doc@freebsd.org CC: jim@reptiles.org Subject: crossed link Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Just noticed that on both 2.2.1 and 2.2.2 link to the same page; i.e. 2.2.2 instructions for floppy installation; 2.2.1 should lead to CD-ROM instructions. Someone inadvertently overwrite ../handbook13.html#13 with ../handbook14.html#14 ? Regards, pb From owner-freebsd-doc Mon Sep 23 20:05:15 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22829 for doc-outgoing; Mon, 23 Sep 1996 20:05:15 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22784 for ; Mon, 23 Sep 1996 20:05:09 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id UAA02232; Mon, 23 Sep 1996 20:04:58 -0700 (PDT) Date: Mon, 23 Sep 1996 20:04:58 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Peter Baril cc: doc@FreeBSD.ORG, jim@reptiles.org Subject: Re: crossed link In-Reply-To: <324648E1.F49@nunanet.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 Mon, 23 Sep 1996, Peter Baril wrote: > Just noticed that on > both 2.2.1 and 2.2.2 link to the same page; i.e. 2.2.2 instructions > for floppy installation; > > 2.2.1 should lead to CD-ROM instructions. > > Someone inadvertently overwrite ../handbook13.html#13 with > ../handbook14.html#14 ? It's working fine on www.freebsd.org, and OK on www.ca. too. www.ca is *really* behind (the Handbook is from May!!); I'd recommend using the top level site (http://www.freebsd.org) if you can. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-doc Mon Sep 23 23:19:20 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14943 for doc-outgoing; Mon, 23 Sep 1996 23:19:20 -0700 (PDT) Received: from natsiq.nunanet.com (root@natsiq.nunanet.com [199.247.47.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA14903 for ; Mon, 23 Sep 1996 23:19:15 -0700 (PDT) Received: from ppp-174.nunanet.com(really [199.247.47.174]) by natsiq.nunanet.com via sendmail with smtp id for ; Tue, 24 Sep 96 02:18:17 -0400 (EDT) (Smail-3.1.93 1996-May-30 #3 built 1996-Jun-18) Message-Id: Date: Tue, 24 Sep 96 02:18:17 -0400 (EDT) X-Sender: pbaril@nunanet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: doc@FreeBSD.ORG From: pbaril@nunanet.com (P. BARIL) Subject: Re: crossed link Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Mon, 23 Sep 1996, Doug White (dwhite@gdi.uoregon.edu) wrote: >It's working fine on www.freebsd.org, and OK on www.ca. too. Greetings Doug, I pointed you to the wrong page last night. The error actually forked from http://www.ca.freebsd.org/handbook/handbook7.html#7 not <../handbook/install.html> as mistakenly indicated last night. Though confirmed still that way earlier this evening, I notice it's been fixed as of a few minutes ago. Per your advice, however, I will switch to www.freebsd.org Txs pb ================================================== >On Mon, 23 Sep 1996, Peter Baril wrote: > >> Just noticed that on >> both 2.2.1 and 2.2.2 link to the same page; i.e. instructions >> for floppy installation; >> >> 2.2.1 should lead to CD-ROM instructions. >> >> Someone inadvertently overwrite ../handbook13.html#13 with >> ../handbook14.html#14 ? ================================================== From owner-freebsd-doc Tue Sep 24 00:00:40 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05934 for doc-outgoing; Tue, 24 Sep 1996 00:00:40 -0700 (PDT) Received: from natsiq.nunanet.com (root@natsiq.nunanet.com [199.247.47.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA05897 for ; Tue, 24 Sep 1996 00:00:32 -0700 (PDT) Received: from ppp-174.nunanet.com(really [199.247.47.174]) by natsiq.nunanet.com via sendmail with smtp id for ; Tue, 24 Sep 96 02:59:40 -0400 (EDT) (Smail-3.1.93 1996-May-30 #3 built 1996-Jun-18) Message-Id: Date: Tue, 24 Sep 96 02:59:40 -0400 (EDT) X-Sender: pbaril@nunanet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: dwhite@resnet.uoregon.edu From: pbaril@nunanet.com (P. BARIL) Subject: Re: crossed links Cc: doc@FreeBSD.ORG, jim@reptiles.org Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Doug, Earlier this evening I was certain that: ----------------------------------------------------------- - at http://www.ca.freebsd.org/handbook/handbook.html (in "Part 5") selecting link <<24.7 Unix History>> took me to http://www.ca.freebsd.org/handbook/handbook265.html#563 = Newsgroups. - and similarly, at http://www.ca.freebsd.org/handbook/handbook265.html#563, selecting link <<25.2.3. X-Window system>> took me to http://www.ca.freebsd.org/handbook/handbook268.html#481 = Mailing Lists. ------------------------------------------------------------ However, a few minutes ago, when I went to confirm these anomalies, I first did a 'reload' of the relevant pages and found all is now fixed. Either someone decided to upgrade the www.ca. site today following our exchange last night, or *** I'VE BEEN A CLUCK *** and was accessing old versions that were in my browser's 'cache'. 'nuff said. From owner-freebsd-doc Tue Sep 24 01:17:16 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14005 for doc-outgoing; Tue, 24 Sep 1996 01:17:16 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-59.ut.nl.ibm.net [139.92.42.59]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA13936; Tue, 24 Sep 1996 01:16:58 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id AAA11775; Tue, 24 Sep 1996 00:18:59 +0200 (MET DST) Date: Tue, 24 Sep 1996 00:18:59 +0200 (MET DST) Message-Id: <199609232218.AAA11775@vector.jhs.no_domain> To: hardware@freebsd.org cc: gj@freebsd.org Subject: cache size in cmos From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is sent: To: hardware@freebsd.org bcc: doc@freebsd.org I had an experience with an old AMD BIOS that seems worth telling... The lesson I learned: If a machine seems really slow, try reloading cmos defaults, (after taking careful note of current settings :-) Someone might want to put that tip in the currently empty (as of Sep 1) section 10.3.4 of the handbook. Hence I bcc'd this to doc@ , but suggest follow up on just hardware@ Why the CMOS Reset ? Well ... I had a hardware problem on a newish (to me) system built from old motherboard, old discs etc, & with loose cache chips, I took cache chips out & I guess I ran that system without to deduce if it was the chips causing my previous problem, anyway I cured the cache chip loose socket problem, But I think the cmos resized itself as having no cache (it doesnt show cache chip availability on my old AMD BIOS, I just have the M/board DIPS to set), & when I put the cache chips back in, the system worked, but was slow as treacle, (but I didnt notice as I was chasing other problems on the system, (like synch/asynch on old HP drives, & data corruption). It also, (after the last surgery on board, & until today) used to ignore the turbo switch (which actually acts not as a frequency controller, but as a cache enable/disable switch), & the `spinner' at kernel load time didnt spin, it trudged along slowly. I decided to track down the `treacle' today, I finally (at power time) told it (the AMD bios from DEL) to reload power (slow) defaults & then bios (faster) defaults, It used to take 120 secs to do cd usr/src/*/ls ; make it now takes turbo on 19.20 real 16.66 user 1.71 sys turbo off 51.48 real 45.97 user 4.51 sys the above with sh & then time, & 2nd compile, 'cos 1st loads stuff into freebsd kernel cache (ie disc to ram) so 1st is always slower than #2 & #3 make. Oh, BTW I had to disable F000 64K cache else reboot ceased to work. (The reload with BIOS defaults had enabled it) The environment 33MHz Intel 486 Motherboard `Gigabyte' `GA-486US' 256K cache. UM82C481A, USA, 9140KV016 UM82C482A, USA, 9138KV001 UM82C206F, 9142-C9, C82093 Copyright American Megatrends Inc., 40-0500-D91199-00101111-050591-UMCWB-F various CLK/2 & CLK/5 madse no real difference, A half week old current that had just finished make world (took about half a week or so (Really ! that's why I investigated)) & kernel that reports FreeBSD 2.2-CURRENT #0: Fri Sep 13 22:38:55 MSZ 1996 jhs@vector:/usr2/src/cur-960901/sys/compile/GATE & with an /etc/make.conf CFLAGS= -O2 -m486 -pipe & cc --version 2.6.3 System idle other than test running. Well, that system is 6 times faster now :-) If this tale has merely amused you, it's been worth it, the more so if it digs someone out of a similar hole. Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-doc Tue Sep 24 04:20:00 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA16100 for doc-outgoing; Tue, 24 Sep 1996 04:20:00 -0700 (PDT) Received: from ns.sta.net.cn (ns.sta.net.cn [202.96.199.133]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA16056 for ; Tue, 24 Sep 1996 04:19:48 -0700 (PDT) Received: from ns.szptt.net.cn (ns.szptt.net.cn [202.96.134.133]) by ns.sta.net.cn (8.6.8.1/8.6.6) with SMTP id TAA08662 for ; Tue, 24 Sep 1996 19:18:23 +0800 Received: from public.szptt.net.cn by ns.szptt.net.cn (5.x/SMI-SVR4) id AA07023; Tue, 24 Sep 1996 18:18:29 +0800 Received: from public by public.szptt.net.cn (5.x/SMI-SVR4) id AA08643; Tue, 24 Sep 1996 19:19:29 +0800 Date: Tue, 24 Sep 1996 19:19:29 +0800 (CST) From: Michael Yang X-Sender: szmic@public To: freebsd-doc@FreeBSD.ORG Subject: help and subscribe Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-doc Tue Sep 24 09:20:28 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12071 for doc-outgoing; Tue, 24 Sep 1996 09:20:28 -0700 (PDT) Received: from bigpuppy.newell.arlington.va.us (mcnsisdn.newell.arlington.va.us [206.27.237.14]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA12039 for ; Tue, 24 Sep 1996 09:20:22 -0700 (PDT) Received: (from mnewell@localhost) by bigpuppy.newell.arlington.va.us (8.6.12/8.6.9) id MAA10431; Tue, 24 Sep 1996 12:16:24 -0400 Date: Tue, 24 Sep 1996 12:16:24 -0400 (EDT) From: Mike Newell To: Bill Lloyd cc: doc@freebsd.org Subject: Re: isdn documentation changes In-Reply-To: <32443F29.7604@mpd.ca> 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 Sat, 21 Sep 1996, Bill Lloyd wrote: > A TA will allow you to do Dynamic IP with your Internet provider. > Unless you can get a static IP this is really your only option to do > ISDN with your Internet provider. This is true of ANY connection with an ISP. If you can't get static address assignment you get dynamic. :-) > The real problam with external TA's is like modems you need a good > serial card in your computer. This might could be a tad more specific: The real problem with TA's is that they generally are limited to 115.2Kbs even when connecting at 128Kbs. This means you can't get the full advantage of ISDN. >

As the cost of low end ISDN routers/bridges approaches that of a > Terminal Adapter, it will likely become a more and more popular choice. > An ISDN router is a small box that plugs directly into your local > ethernet network(or card) and manages it's own connection to the other > bridge/router. It has all the software to do PPP and other protocols > built in. What standalone router/bridges prices are approaching TA's? TA's are in the $300+ range; most brouters are in the $800+ range. That's quite a difference... > A router will allow you much faster thoughput that a standard TA, since > it will be using a full synchronous ISDN connection. A TA can also do this, especially if the TA is implemented as an internal model and hence doesn't have to go through the serial ports. > A router will also usually allow you to have 2 ISDN connections open at > the same time. One on each B channel. This is not supported on most > TA's, except for specific(expensive) models that have two serial ports. Not true - the BitSurfr Pro will use both B channels. Nice document! Much obliged, Mike +--------------------------------------+------------------------------------+ | Mike Newell | The opinions expressed herein | | Affiliation: | are mine. You can take them or | | Address: | leave them. Flames to /dev/null. | +--------------------------------------+------------------------------------+ | Mike@Newell.arlington.va.us | http://www.newell.arlington.va.us | +--------------------------------------+------------------------------------+ | "Peace. It's wonderful!" Father Divine. | +---------------------------------------------------------------------------+ From owner-freebsd-doc Tue Sep 24 10:04:28 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01197 for doc-outgoing; Tue, 24 Sep 1996 10:04:28 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA01111 for ; Tue, 24 Sep 1996 10:04:12 -0700 (PDT) Received: from cdale3.midwest.net by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v5au0-0008xmC; Tue, 24 Sep 96 10:04 PDT Received: from asic.midwest.net (ofallon14.midwest.net [206.158.93.14]) by cdale3.midwest.net (8.7.3/8.7.3) with SMTP id MAA03494 for ; Tue, 24 Sep 1996 12:03:10 -0500 (CDT) Message-Id: <199609241703.MAA03494@cdale3.midwest.net> From: "asic" To: Subject: Free handbook Date: Tue, 24 Sep 1996 11:54:17 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1085 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Please add me to your mailing list! From owner-freebsd-doc Tue Sep 24 11:46:52 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03334 for doc-outgoing; Tue, 24 Sep 1996 11:46:52 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA03313 for ; Tue, 24 Sep 1996 11:46:48 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA28876; Tue, 24 Sep 1996 10:46:43 -0800 Date: Tue, 24 Sep 1996 18:47:51 +0000 () From: hmmm To: doc@freebsd.org Subject: http://www.alaska.net/~hmmm/pcw01.htm Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hey! never heard from you guys! BSDez - been helpful to many BSD users coming over from DOS, and other as well. From owner-freebsd-doc Tue Sep 24 15:30:19 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA25107 for doc-outgoing; Tue, 24 Sep 1996 15:30:19 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA25077 for ; Tue, 24 Sep 1996 15:30:14 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id PAA04611; Tue, 24 Sep 1996 15:29:58 -0700 (PDT) Date: Tue, 24 Sep 1996 15:29:57 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: hmmm cc: doc@FreeBSD.org Subject: Re: http://www.alaska.net/~hmmm/pcw01.htm 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 Tue, 24 Sep 1996, hmmm wrote: > hey! never heard from you guys! Sorry! I've had other things going on here (like moving in). > BSDez - been helpful to many BSD users coming over from DOS, > and other as well. Quite. Thanks for putting it up. I have one suggestion: watch your color combinations. I believe there is a section with bright green on white that I can barely read. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-doc Tue Sep 24 22:13:24 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23891 for doc-outgoing; Tue, 24 Sep 1996 22:13:24 -0700 (PDT) Received: from cool.pvrr.ru (cool.pvrr.ru [194.87.186.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA23765 for ; Tue, 24 Sep 1996 22:13:03 -0700 (PDT) Received: from cool.pvrr.ru (localhost.pvrr.ru [127.0.0.1]) by cool.pvrr.ru (8.6.12/8.6.12) with SMTP id JAA00949 for ; Wed, 25 Sep 1996 09:14:17 +0400 Message-ID: <3248BFA7.41C67EA6@cool.pvrr.ru> Date: Wed, 25 Sep 1996 05:14:15 +0000 From: Alexander McSimov X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: doc@freebsd.org Subject: What about gzipped tar files in TUTORIAL? Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can not get ALL of the gzipped tar files in "tutorials". What goes on with them? From owner-freebsd-doc Wed Sep 25 00:27:43 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04815 for doc-outgoing; Wed, 25 Sep 1996 00:27:43 -0700 (PDT) Received: from foo.netvoyage.net (ip139.lax.primenet.com [204.212.59.139]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA04768 for ; Wed, 25 Sep 1996 00:27:40 -0700 (PDT) Received: from localhost (bkogawa@localhost) by foo.netvoyage.net (8.7.5/8.6.12) with SMTP id AAA01298 for ; Wed, 25 Sep 1996 00:32:31 -0700 (PDT) X-Authentication-Warning: foo.netvoyage.net: bkogawa owned process doing -bs Date: Wed, 25 Sep 1996 00:32:31 -0700 (PDT) From: "Bryan K. Ogawa" X-Sender: bkogawa@foo.netvoyage.net To: freebsd-doc@freebsd.org Subject: Mail section of the handbook? 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 was wondering if anyone had anything written on the email section of the handbook. I was thinking that I was going to try my hand at writing up a section, and that seemed like one that I know a little about (enough, perhaps, to get started). Unfortunately, at the moment, I don't know much about sgml, so I'm not sure I could mark it up properly, but I could (hopefully?) start on something in ascii. what do you guys think? bryan k ogawa http://www.primenet.com/~bkogawa/ From owner-freebsd-doc Wed Sep 25 01:14:13 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09681 for doc-outgoing; Wed, 25 Sep 1996 01:14:13 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA09620 for ; Wed, 25 Sep 1996 01:14:06 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id KAA20547 for doc@FreeBSD.org; Wed, 25 Sep 1996 10:00:49 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.7.6/8.7.3) id KAA01834; Wed, 25 Sep 1996 10:02:07 +0200 (MET DST) Date: Wed, 25 Sep 1996 10:02:07 +0200 (MET DST) Message-Id: <199609250802.KAA01834@klemm.gtn.com> X-Newsreader: knews 0.9.8 From: andreas@klemm.gtn.com (Andreas Klemm) Subject: Re: Thanks to the FreeBSD Team!! (fwd) To: doc@FreeBSD.org MIME-Version: 1.0 Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Sender: owner-doc@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Path: klemm.gtn.com!usenet From: andreas@klemm.gtn.com (Andreas Klemm) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Thanks to the FreeBSD Team!! Date: 25 Sep 1996 08:01:31 GMT Organization: FreeBSD makes fun Lines: 30 Message-ID: <52aosr$nu@klemm.gtn.com> References: <51bgjg$iaf@maverick.tad.eds.com> NNTP-Posting-Host: klemm.gtn.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 In article <51bgjg$iaf@maverick.tad.eds.com>, Phillip Flodin writes: > Hi all, > > I know this is probably not the place for this and Please don't flame me. > > I would just like to thank the entire team working on FreeBSD. I worked > with un*x all throughout my college career and now that I am in the real > world, I missed it. I found out about FreeBSD through a friend of mine > and am now a subscription member of the Walnut Creek CDRom. I love the OS > and all of its robust features. > > I just installed the 2.1.5 CD last weekend and it runs like a dream. I > thought I was never going to get a chance to use un*x again after school, > and now you have given me that chance. That's a real nice posting and I hope, that many FreeBSD hackers and core team members see it. Perhaps we should add a reference List of satisfied customers in the FreeBSD handbook ;-)) Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-doc Wed Sep 25 12:41:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16728 for doc-outgoing; Wed, 25 Sep 1996 12:41:06 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA16695 for ; Wed, 25 Sep 1996 12:41:01 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id OAA17660; Wed, 25 Sep 1996 14:40:54 -0500 (EST) Date: Wed, 25 Sep 1996 14:40:53 -0500 (EST) From: John Fieber To: "Bryan K. Ogawa" cc: freebsd-doc@FreeBSD.org Subject: Re: Mail section of the handbook? 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, 25 Sep 1996, Bryan K. Ogawa wrote: > I was wondering if anyone had anything written on the email section of the > handbook. Not that I've seen. > I was thinking that I was going to try my hand at writing up a section, > and that seemed like one that I know a little about (enough, perhaps, to > get started). The focus should be on the administrative side (eg sendmail), and in particular under what situations the out-of-the-box configuration needs to be tweaked. On the other hand, there are a number of excellent books on mail administration that we do not need to duplicate here. Finding a happy compromise is the task. I think we need at most a brief overview about how to use the standard mail client. I expect that most people use something other than the standard client so an extensive tutorial might be wasted words. We do have a good tutorial for mh, while pine and elm (to their credit) hardly need anything more than their on-line help provides. A brief survey of alternate mail client would be useful, as would some other mail-related packages such as procmail and majordomo. > Unfortunately, at the moment, I don't know much about sgml, so I'm not Don't let that stop you! > sure I could mark it up properly, but I could (hopefully?) start on > something in ascii. Ascii would be fine. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Wed Sep 25 14:38:47 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11803 for doc-outgoing; Wed, 25 Sep 1996 14:38:47 -0700 (PDT) Received: from hod (hod.tera.com [206.215.142.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11760 for ; Wed, 25 Sep 1996 14:38:42 -0700 (PDT) Received: from athena.tera.com (athena.tera.com [206.215.142.62]) by hod (8.7.5/8.7.3) with ESMTP id OAA16595 for ; Wed, 25 Sep 1996 14:38:38 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id OAA18165 for doc@freebsd.org; Wed, 25 Sep 1996 14:38:35 -0700 (PDT) Date: Wed, 25 Sep 1996 14:38:35 -0700 (PDT) Message-Id: <199609252138.OAA18165@athena.tera.com> To: doc@freebsd.org Subject: vi tutorial overview, ASCII version. Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Enclosed is the ASCII version of the overview on vi that I'm working on. Feedback, people?? gary kline @(#) HowVi.ascii. 25sep96 This ``Using vi'' tutorial is intented to be a brief overview; something that, within 20 to 30 minutes, will jump-start you on the road to learning the basics of vi. Read through and work with this once or twice. To launch yourself into a higher orbit of skill and understanding, check out the References toward the bottom. Using vi The vi text editor is a widely available visual, full-screen text editor. vi is a powerful editor, and it is also old--and this shows. vi was created at a time when most terminals did not have arrow keys. Because of this, vi is modal: it has several modes it can be in, with its behavior changing depending on mode. Readers who are at workstations should open a second window and to try out vi commands as they work through this overview. If you have access to only one window or screen, print a hardcopy of this overview. A parenthetical note: ((You can really begin to edit documents with only a few commands: either the arrow-keys or ``h'', ``j'', ``k'', and `l''. Plus the backspace key and ths spacebar. These keys will move you around the screen--if you are in command mode. Then with ``i'' to insert and ``ESC'' to get back into command mode, you can enter text. ``x'' to delete a character and ``r'' to replace a character round out the minimal techniques. But, I'm getting ahead of myself, so on with this tutorial. . . .)) Starting and stopping To start up vi, change to your home directory and type % vi samp This will start vi editing a (theoretically) new file named ``samp.'' If samp already exists it will be loaded and displayed upon your screen. Many different commands can be used to exit vi. Typing :wq will write the file to disk and quit. Typing :q will quit if no changes have been made. If changes have been made then you must type :q! to quit without saving changes. (Note that when you type a colon and are in command mode, the cursor will move to the bottom left corner of your screen.) These few commands are enough to suggest the main frustration new users have with vi--there are many commands to memorize, and many like ``ZZ'' make no sense at all. They have been added often as add-ons, and are simply part of the program. At first, it is probably best to find one way of doing something and sticking with it. You can and will add more skills as you go along. Inserting text Initially vi is in command mode. Most (not all) keys entered are commands to vi itself and will not enter text. Typing ``i'' is the command to enter text-input mode. vi inserts all non-control characters typed while in text-input mode into the document. Some characters in this mode have special meanings; the backspace key, for example, backs over mistakes. ((If you do accidentally change something in your vi session, the ``u'' command will undo it when you are in command mode.)) Text can also inserted by typing ``a''. This will add it following the current character. Press ``ESC'' to get out when you are finished. If you type ``o'' (lower-case), you will open a line immediately below where your cursor is. An upper-case ``O'' will insert an empty line above your cursor. And some parallels here with ``A'' and ``I.'' If you type an ``A'' on any line, the cursor will move to the end of the text and be ready to append text. Typing ``I'' will prepare vi to insert text at the beginning of the line. Try typing something, like four lines from this tutorial if nothing else comes to mind. When you are through typing, to leave text-input mode, press the ``ESC'' key to get back into command mode. Deleting text To delete an entire line, press ``dd''. To delete a character, press ``x''. ``10dd'' will delete 10 lines, and ``5x'' will delete 5 characters. Try these deletion commands now. Undo each, if you wish, by typing ``u''. Once you have used ``dd'', the text is placed in a buffer. To move the text you can place the cursor at the point where you want it to appear and then type ``p''. This is equivalent to a block move. A block is copied by using ``yy'' or ``10yy'' (or use any number instead of 10) to yank into the buffer and then using p normally. ``p''--lower case--places the block below the current line. ``P''--upper case--places the block above the line where your cursor currently is. Typing ``D'' will delete the rest of the line---from wherever you have the cursor to the end of that line. If you want to delete text from wherever you have the cursor is until you find a specific character, ``dfcharacter'' will do that for you. If you place the cursor at the beginning of a word and type ``dw'' vi will delete just that word. Cursor movement Note that in some cases you cannot use the arrow keys while in insert mode. With some kinds of hardware you can. The only way to determine whether you can use your arrow keys in text-input mode is to experiment. As a rule of thumb, the cursor can be moved with the arrow keys as long as you are not in text-input mode. The lower-case letters ``h", ``j'', ``k'' and ``l'' also mimic the arrow keys. Backwards, downward, upward, and forward one space or line respectively. The backspace key moves the cursor one space backwards; the spacebar moves one space forward. ((If you use some straightforward re-mapping tricks you can map the arrow keys to the h,j,k,l keys. Such mapping tricks are beyond the intent of this overview, however. --See the References section below. )) As a rule of thumb, the cursor can be moved with the arrow keys as long as you are not in text-input mode. ``h", ``j'', ``k'' and ``l'' also mimic the arrow keys. Backwards, downward, upward, and forward one space or line respectively. ``0'' (zero) will move the cursor to the beginning of the line, ``$'' will take you to the end. ''G'' will go to the end of a file. Typing ``numberG'' will move you to the line ``number'' And then typing two apostrophes will move you back to where you were. If you were on, say, line 4, then typed ``15G'' followed by '' you would go from line 4 to 15 and back to line 4. Typing :10 will take you to line 10. Any number can be used in place of 10. ``^F'' (cntl-F) will page forward one screen, ``^B'' (cntl-B) goes back one screen. Replacing text (while in command mode) You can replace a single character by typing ``r'' followed by the new value. Use ``R'' to replace a whole group of characters. By placing the cursor on the first letter of a word and typing ``cw'' you are ready to change the entire word. After you have typed in your replacement, hit ``ESC'' to get back into command more. Typing ``C'' from wherever the cursor is to the end of the line will ready vi to let you re-type the line. If you type ``cfcharacter'' where character is an ASCII character, vi will let you change the string from whereever the cursor is until it finds the character. Be sure to type ``ESC'' when you are done replacing. The period or dot ``.'' means ``Repeat the last command''. --So it is possible to make accidental changes to your file while you are still in command mode, but you should not find this too much trouble.-- Typing ``.'' in command mode is an effective means of replacing various sections of text easily and quickly. Finding and replacing text To find a string, type / followed by what you want to find. Note that when you type a slash in vi--in command mode--, your cursor moves to the bottom left-hand corner of your screen. For example, /Pascal finds the next occurrence of the word ``Pascal,'' starting at the current cursor position. ``n'' finds the next occurrence. To replace text, type :s/pascal/Pascal/ This will replace the first occurrence of ``pascal'' with ``Pascal'' And the following: :1,$s/pascal/Pascal/g will do the replace globally throughout the document. (From the 1st line, ``1'' to the end, ``$'') Miscellaneous features Here are some miscellaneous features of vi that both new and skilled users employ. The set commands. Typing ``:set feature'' lets you set a variety of features commonly used in editing and for programming. Here are a few examples. :set autoindent will automatically indent the next line to the same indentation as you typed above. To back out of any indentation, you must type a Control-D. Typing :set noautoindent unsets the autoindent feature. :set showmatch will tell the editor to show you matching cases or parenthesis and braces. This is useful in many programming languages. Using showmatch, vi will blink each matching pair of parens or braces. :set noshowmatch unsets the feature :set nunmber causes vi to display number lines along the left-hand side of your display. :set nonunmber gets rid of the line numbers. Executing a command from within vi. Typing ``:! command'' will temporarily escape you back to your shell and execute ``command''. For example: :!ls -l will present you with a long listing of whatever files are in your current directory. As soon as the listing is complete, you will be back inside vi and a colon prompt will be displayed at the lower left-hand corner of your display. Reading another file into vi Typing ``:r filename'' will cause vi to include the file ``filename'' within your current file at the linenumber of your cursor. For example :r letter_to_jack will cause the file ``letter_to_jack'' to be read into your current file. Here, you need to be sure at exactly what linenumber you want to have ``letter_to_jack'' inserted and be sure that your cursor is at that line. Note that you can always undo the insertion by typing ``ESC u'' References This brief overview will get you going with vi. After you have become familiar with these few commands and want to learn more, there are a number of avenues. One is to simply ask friends or colleagues; another is to read of one the many commercial tutorials on vi. Jerry Peek, Tim O'Reilly and others have a bunch of tricks and techniques for getting the most out of vi in Unix Power Tools. A third is to check out the online documentation on nvi by Keith Bostic. You will find this file in /usr/share/doc/usd/13.viref, paper.ascii.gz. Another online document titled ``An Introduction to Display Editing with vi,'' by Bill Joy and Mark Horton lives in /usr/share/doc/usd/12.vi/paper.ascii.gz This fourth reference is the original paper on vi. You can scroll through these gzip'd docs with the zmore utility. Following are ftp or http sites that have tutorial documentation on using the vi editor. There is an exceptionally well-written vi FAQ available at: http://www.macom.co.il/vi/index.html that has all files in HTML format. This site will give you considerably more information that in this overview. And in Norway at alf.uib.no in /pub/vi, the following files are available for anonymous ftp: -rw-r--r-- 1 20035 5881 Sep 24 1993 HELP -rw-r--r-- 1 20035 15249 May 20 1995 INDEX -rw-r--r-- 1 20035 1123 Jun 23 1992 WHO drwxr-xr-x 2 20035 1536 Jun 19 07:39 comp.editors -rw-r--r-- 1 20035 16247 May 25 20:06 comp.editors.EDS -rw-r--r-- 1 20035 9569 Aug 11 1992 comp.editors.FAQ -rw-r--r-- 1 20035 2822 Feb 28 1994 comp.editors.PNT -rw-r--r-- 1 20035 1416 Jul 25 1993 comp.editors2 -rw-r--r-- 1 20035 990 Aug 8 1993 comp.editors3 drwxr-xr-x 2 20035 2048 Jun 19 07:39 docs drwxr-xr-x 2 20035 1536 Jun 19 06:42 macros drwxr-xr-x 4 20035 512 Jun 19 07:12 programs drwx------ 2 20035 1024 Jun 19 07:39 t 226 Transfer complete. In the docs directory are several dozen compressed files from one to several years old. Several seem worth downloading and reviewing if you really want to hone your vi skills. Bottom line: there is lots of freely available literature on learning vi out there. Concluding remarks If you are determined to learn a particular skill, you will; even something that seems as arcane as the vi editor. vi will almost certainly grow on you. Especially as you become more proficient, vi, with all its tricks and shortcut commands will let you edit a file very efficiently. It will probably help to keep a HowTo file, either on paper or online to keep track of how to do various things in vi. After a few days of using vi, you're on your way toward its mastery. The version of vi in FreeBSD was written by Keith Bostic and named nvi. nvi and nex--the clone of the original ``ex''-- excell in their functionality and concept. Bostic claims that nvi is a ``feature-for-feature, bug-for-bug'' replacement for the original program written by Bill Joy. I have found it to be even a bit better than the original. People who can find at least two such improvements get gold stars by their names! -- This tutorial was begun by Marshall Brain and augmented by Phil Pfeiffer and Brian Sherwood (1993). Gary Kline futher elaborated enhanced this with the kind help of many folks interested in the FreeBSD Project. Gary Kline also put this document into markup format (1996) . If you have ideas on how this brief introduction to vi can be improved, please forward your ideas to kline@tao.thought.org From owner-freebsd-doc Thu Sep 26 08:07:16 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA29904 for doc-outgoing; Thu, 26 Sep 1996 08:07:16 -0700 (PDT) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA29875 for ; Thu, 26 Sep 1996 08:07:13 -0700 (PDT) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id PAA22030; Thu, 26 Sep 1996 15:07:11 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA294540431; Thu, 26 Sep 1996 15:07:11 GMT Message-Id: <324A9C1E.7669@fsl.noaa.gov> Date: Thu, 26 Sep 1996 09:07:10 -0600 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0b8Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: hmmm Cc: doc@FreeBSD.org Subject: Re: http://www.alaska.net/~hmmm/pcw01.htm References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk hmmm wrote: > hey! never heard from you guys Well, you know how it goes ... Anyway, I'd recommend renaming the so-called alphabit scripts longer and more descriptive names. After all, you've got a lot more than the DOS-imposed 8.3 limit, and Unix being hard enough to understand as it is, longer names like "network-monitor" might help the unitiated. I still claim that "mv /usr/bin/vi /usr/bin/vivi" is a no-no! The other thing I'd recommend changing is the colors of the headings ... they're downright unreadable in some places. Otherwise, the hints for newcomers are appropriate and I hope they can get up to speed faster with your example ocnfig files, suggestions, etc. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-doc Thu Sep 26 22:13:00 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17257 for doc-outgoing; Thu, 26 Sep 1996 22:13:00 -0700 (PDT) Received: from nau.antar.bryansk.ru (nau.antar.bryansk.ru [194.87.200.50]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17182 for ; Thu, 26 Sep 1996 22:12:52 -0700 (PDT) Received: from marcon (uucp@localhost) by nau.antar.bryansk.ru (8.6.12/8.6.12) with UUCP id IAA00416 for doc@freebsd.org; Fri, 27 Sep 1996 08:40:20 +0400 Received: by lion.bryansk.ru id EAA02285; (8.6.12/vak/1.9) Sat, 27 Jul 1996 04:31:25 +0400 Date: Sat, 27 Jul 1996 04:31:25 +0400 Message-Id: <199607270031.EAA02285@lion.bryansk.ru> To: doc@freebsd.org X-URL: mailto:doc@freebsd.org X-Mailer: Lynx, Version 2-4-2 X-Personal_name: LIk From: asdf@lion.bryansk.ru Subject: ww Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-doc Thu Sep 26 22:13:25 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17444 for doc-outgoing; Thu, 26 Sep 1996 22:13:25 -0700 (PDT) From: owner-doc Received: from nau.antar.bryansk.ru (nau.antar.bryansk.ru [194.87.200.50]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17183 for ; Thu, 26 Sep 1996 22:12:52 -0700 (PDT) Received: from marcon (uucp@localhost) by nau.antar.bryansk.ru (8.6.12/8.6.12) with UUCP id IAA00420 for doc@freebsd.org; Fri, 27 Sep 1996 08:40:24 +0400 Received: by lion.bryansk.ru id EAA02290; (8.6.12/vak/1.9) Sat, 27 Jul 1996 04:31:36 +0400 Date: Sat, 27 Jul 1996 04:31:36 +0400 Message-Id: <199607270031.EAA02290@lion.bryansk.ru> To: doc@freebsd.org X-URL: mailto:doc@freebsd.org X-Mailer: Lynx, Version 2-4-2 X-Personal_name: LIk Subject: mailto:doc@freebsd.org Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-doc Sat Sep 28 03:54:07 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA00159 for doc-outgoing; Sat, 28 Sep 1996 03:54:07 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA29908 for ; Sat, 28 Sep 1996 03:53:42 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.6/8.6.9) with SMTP id UAA02797 for ; Sat, 28 Sep 1996 20:53:10 GMT Date: Sat, 28 Sep 1996 20:53:09 +0000 () From: David Nugent To: FreeBSD-doc Mailing List Subject: Linuxdoc intro Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does anyone have a nice, concise description of the Linuxdoc DTD they'd be willing to share? I'm after a list of tags, the basic structural syntax supported via the various document types (and a list of those as well). The Linuxdoc guide is fine, but unfortunately very incomplete, and it seems to only cover /some/ of the aspects of the

doctype. I'm an SGML newbie, and while I can follow the DTD with difficulty, I'd like to become productive a little more quickly, which really doesn't require the level of detail required to, say, actually write a new DTD. Apologies if this is an FAQ, but I've searched the web high and low, only to bury myself in a mass of data that I'm NOT looking for. :-) From owner-freebsd-doc Sat Sep 28 10:56:10 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00189 for doc-outgoing; Sat, 28 Sep 1996 10:56:10 -0700 (PDT) Received: from tolstoy.mpd.ca (wlloyd.HIP.CAM.ORG [199.84.42.209]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA29892 for ; Sat, 28 Sep 1996 10:55:58 -0700 (PDT) Received: from plato (plato.mpd.ca [206.123.11.34]) by tolstoy.mpd.ca (8.7.5/8.7.3) with SMTP id NAA15711 for ; Sat, 28 Sep 1996 13:54:17 -0400 (EDT) Message-ID: <324D6669.1845@mpd.ca> Date: Sat, 28 Sep 1996 13:54:49 -0400 From: Bill Lloyd X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4c) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: ISDN handbook changes. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have incorperated all feedback into a new document. The following is a drop in replacement for /usr/src/share/doc/handbook/isdn.sgml There is no signature at the end. -bill wlloyd@mpd.ca -----Start Here----- ISDN

Last modicified by .

ISDN for FreeBSD is still largely under developement. Specifically, there are a lack of drivers for PC ISDN cards.

A good resource for information on ISDN technology and hardware is . A quick simple roadmap to ISDN follows: If you live in Europe I suggest you investigate the ISDN card section. If you are planning to use ISDN primarily to connect to the internet with an Internet Provider on a dialup non-dedicated basis, I suggest you look into Terminal Adapters. This will give you the most flexibility, with the fewest problems, if you change providers. If you are conecting two lans together, or connecting to the internet with a dedicated ISDN connection, I suggest you consider the Standalone router/bridge option.

Cost is a significant factor in determining what solution you will choose. The following options are listed from least expensive to most expensive. ISDN Cards

Originally Contribution by &a.hm;.

This section is really only relevant to European ISDN users. The cards supported are not yet(?) availible for North American ISDN standards.

PC ISDN cards support the full bandwidth of ISDN, 128Kbs. These cards are often the least expensive type of ISDN equipment.

There is the bisdn ISDN package available from supporting FreeBSD 2.1R, FreeBSD-current and NetBSD. The latest source can be found on the above mentioned ftp server under directory isdn as file bisdn-097.tar.gz. There are drivers for the following cards: Currently all (passive) Teles cards and their clones are supported for the EuroISDN (DSS1) and 1TR6 protocols. Dr. Neuhaus - Niccy 1016 There are several limitations with the bisdn stuff. Specifically the following features usually associated with ISDN are not supported. No PPP support, only raw hdlc. This means you cannot connect to a some standalone routers, such as a Cisco unit. Bridging Control Protocol not supported. Multiple cards are not supported. No bandwidth on demand. No channel bundling. A majordomo maintained mailing list is available, to subscribe, send the usual majordomo requests to . ISDN Terminal Adapters

Terminal adapters(TA), are to ISDN what modems are to regular phone lines.

Most TA's use the standard hayes modem AT command set, and can be used as a drop in replacement for a modem. A TA will operate basically the same as a modem except connection and throughput speeds will be much faster than your old modem. You will need to configure exactly the same as for a modem setup. Make sure you set your serial speed as high as possible. The main advantage of using a TA to connect to an Internet Provider is that you can do Dynamic PPP. As IP address space becomes more and more scarce, most providers are not willing to provide you with a static IP anymore. Most standalone routers are not able to accomidate dynamic IP allocation. TA's completely rely on the PPP daemon that you are running for their features and stabiliy of connection. This allows you to upgrade easily from using a modem to ISDN on a FreeBSD machine, if you already have PPP setup. However, at the same time any problems you experienced with the PPP program and are going to persist. If you want maximum stability, use the kernel option, not the user-land .

The following TA's are know to work with FreeBSD. Motorola BitSurfer and Bitsurfer Pro Adtran Most other TA's will probably work as well, TA vendors try to make sure their product can accept most of the standard modem AT command set. The real problam with external TA's is like modems you need a good serial card in your computer. You should read the section in the handbook for a detailed understanding of serial devices, and the differences between asynchronous and synchronous serial ports. A TA running off a standard PC serial port (asynchronous) limits you to 115.2Kbs, even though you have a 128Kbs connection. To fully utilize the 128Kbs that ISDN is capable of, you must move the TA to a synchronous serial card. Do not be fooled into buying an internal TA and thinking you have avoided the synchronous/asynchronous issue. Internal TA's simply have a standard PC serial port chip built into them. All this will do, is save you having to buy another serial cable, and find another empty electrical socket. A synchronous card with a TA is at least as fast as a standalone router, and with a simple 386 FreeBSD box driving it, probably more flexible. The choice of sync/TA vs standalone router is largely a religious issue. There has been some discussion of this in the mailing lists. I suggest you search the for the complete discussion. Standalone ISDN Bridges/Routers

ISDN bridges or routers are not at all specific to FreeBSD or any other operating system. For a more complete description of routing and bridging technology, please refer to a Networking reference book. In the context of this page, I will use router and bridge interchangeably.

As the cost of low end ISDN routers/bridges comes down, it will likely become a more and more popular choice. An ISDN router is a small box that plugs directly into your local ethernet network(or card), and manages it's own connection to the other bridge/router. It has all the software to do PPP and other protocols built in. A router will allow you much faster thoughput that a standard TA, since it will be using a full synchronous ISDN connection. The main problem with ISDN routers and bridges is that interoperability between manufacturers can still be a problem. If you are planning to connect to an Internet provider, I recommend that you discuss your needs with them.

If you are planning to connect two lan segments together, ie: home lan to the office lan, this is the simplest lowest maintenance solution. Since you are buying the equipment for both sides of the connection you can be assured that the link will work. For example to connect a home computer or branch office network to a head office network the following setup could be used. Branch office or Home network Network is 10 Base T ethernet. Connect router to network cable with AUI/10bT transciever if necessary. ---Sun workstation | ---FreeBSD box | ---Windows 95 (Don't admit to owning it) | Standalone router | ISDN BRI line If your home/branch office is only one computer you can use a twisted pair crossover cable to connect to the standalone router directly. Head office or other lan Network is Twisted Pair ethernet. -------Novell Server | H | | ---Sun | | | U ---FreeBSD | | | ---Windows 95 | B | |___---Standalone router | ISDN BRI line One large advantage of most routers/bridges is that they allow you to have 2 SEPERATE INDEPENDANT PPP connections to 2 seperate sites at the SAME time. This is not supported on most TA's, except for specific(expensive) models that have two serial ports. Do not confuse this with channel bonding. This is a very usefull feature for example if you have an dedicated internet ISDN connection at your office and would like to tap into it, but don't want to get another ISDN line at work. A router at the office location can manage a dedicated B channel connection (64Kbs) to the internet as well as a use the other B channel for anything else, including dialin or dialout to another location or dynamically bonding it with the internet connection for more bandwidth. An alternate use of this is to connect to 2 different branch offices at the same time from the same ISDN line at your central office. From owner-freebsd-doc Sat Sep 28 12:51:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02624 for doc-outgoing; Sat, 28 Sep 1996 12:51:06 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02536 for ; Sat, 28 Sep 1996 12:50:59 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.8.0/8.7.3) id FAA19688; Sun, 29 Sep 1996 05:19:30 +0930 (CST) Date: Sun, 29 Sep 1996 05:19:30 +0930 (CST) From: Peter Childs Message-Id: <199609281949.FAA19688@al.imforei.apana.org.au> To: wlloyd@mpd.ca (Bill Lloyd), freebsd-doc@freebsd.org Subject: Re: ISDN handbook changes. X-Newsreader: TIN [version 1.2 PL2] Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : I have incorperated all feedback into a new document. The following is : a drop in replacement for /usr/src/share/doc/handbook/isdn.sgml Great stuff. What is the general way-to-get-it-done with the docs project? Is it a case of posting here, or submitting via send-pr? The tutorials section is starting to look pretty neat BTW, although Doug's sgml'ised ppp stuff should really get stuck in there. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-doc Sat Sep 28 18:43:46 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05991 for doc-outgoing; Sat, 28 Sep 1996 18:43:46 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05952 for ; Sat, 28 Sep 1996 18:43:42 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.6/3.4W4-SMTP) with ESMTP id KAA00325; Sun, 29 Sep 1996 10:42:44 +0900 (JST) Message-Id: <199609290142.KAA00325@mail.tky007.tth.expo96.ad.jp> To: freebsd-doc@freebsd.org Cc: max@wide.ad.jp Subject: English version of IIJ-PPP doc From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 29 Sep 1996 10:42:43 +0900 Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, With a lot of help, I have translated the IIJ-PPP User's Reference to English. (It was originally written in Japanese.) Although there is one LaTeX problem left, I decided to make it available to the public. If you are interested, get it from: http://www.sfc.wide.ad.jp/~max/iijppp-doc.tar.gz --- LaTeX source http://www.sfc.wide.ad.jp/~max/iijppp-doc.ps.gz --- PostScript version It is a little more than 70 pages. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : max@wide.ad.jp / max@FreeBSD.ORG [URL] : http://www.sfc.wide.ad.jp/~max/ From owner-freebsd-doc Sat Sep 28 19:12:56 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27120 for doc-outgoing; Sat, 28 Sep 1996 19:12:56 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA27087 for ; Sat, 28 Sep 1996 19:12:52 -0700 (PDT) Received: from channel.eng.umd.edu (channel.eng.umd.edu [129.2.98.186]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id WAA01136; Sat, 28 Sep 1996 22:12:49 -0400 (EDT) Received: from localhost (chuckr@localhost) by channel.eng.umd.edu (8.7.5/8.7.3) with SMTP id WAA08168; Sat, 28 Sep 1996 22:12:48 -0400 (EDT) X-Authentication-Warning: channel.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 28 Sep 1996 22:12:48 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@channel.eng.umd.edu To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: freebsd-doc@freebsd.org Subject: Re: English version of IIJ-PPP doc In-Reply-To: <199609290142.KAA00325@mail.tky007.tth.expo96.ad.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 29 Sep 1996, Masafumi NAKANE/[ISO-2022-JP] 中根雅文 wrote: > Hi, > > With a lot of help, I have translated the IIJ-PPP User's > Reference to English. (It was originally written in Japanese.) > Although there is one LaTeX problem left, I decided to make it > available to the public. This is funny. It's a great service, but after struggling for 2 years, I finally get my ppp working correctly. 2 hours later the manual shows up. Murphy is somewhere laughing himself silly. This isn't to detract from what you did, which is a signal service to FreeBSDers. > > If you are interested, get it from: > > http://www.sfc.wide.ad.jp/~max/iijppp-doc.tar.gz --- LaTeX source > http://www.sfc.wide.ad.jp/~max/iijppp-doc.ps.gz --- PostScript version > > It is a little more than 70 pages. > > ----------------------------------------------------------------------- > Masafumi NAKANE, Keio Univ., Dept. of Environmental Information > E-Mail : max@wide.ad.jp / max@FreeBSD.ORG > [URL] : http://www.sfc.wide.ad.jp/~max/ > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-doc Sat Sep 28 19:34:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA08933 for doc-outgoing; Sat, 28 Sep 1996 19:34:06 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA08875 for ; Sat, 28 Sep 1996 19:33:58 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id TAA00357; Sat, 28 Sep 1996 19:33:35 -0700 (PDT) Date: Sat, 28 Sep 1996 19:33:35 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Peter Childs cc: freebsd-doc@freebsd.org Subject: Re: ISDN handbook changes. In-Reply-To: <199609281949.FAA19688@al.imforei.apana.org.au> 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 Sun, 29 Sep 1996, Peter Childs wrote: > : I have incorperated all feedback into a new document. The following is > : a drop in replacement for /usr/src/share/doc/handbook/isdn.sgml > > Great stuff. > > What is the general way-to-get-it-done with the docs > project? Is it a case of posting here, or submitting via > send-pr? Now see, this is something we need to work on: documenting how to submit documentation. :-) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-doc Sat Sep 28 19:38:13 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10326 for doc-outgoing; Sat, 28 Sep 1996 19:38:13 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10279 for ; Sat, 28 Sep 1996 19:38:06 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id TAA00373; Sat, 28 Sep 1996 19:37:06 -0700 (PDT) Date: Sat, 28 Sep 1996 19:37:06 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: David Nugent cc: FreeBSD-doc Mailing List Subject: Re: Linuxdoc intro 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 Sat, 28 Sep 1996, David Nugent wrote: > Does anyone have a nice, concise description of the Linuxdoc DTD they'd > be willing to share? I'm after a list of tags, the basic structural > syntax supported via the various document types (and a list of those as > well). /usr/share/handbook/*.sgml That's what I did. :-) BTW, The linuxdoc DTD is on it's way out. At last check, the project is considering going over to the docbook (sp?) format, which is much better designed for electronic conversion. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-doc Sat Sep 28 20:01:01 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22267 for doc-outgoing; Sat, 28 Sep 1996 20:01:01 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22232 for ; Sat, 28 Sep 1996 20:00:55 -0700 (PDT) Received: from fiber.eng.umd.edu (fiber.eng.umd.edu [129.2.98.185]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id XAA01566; Sat, 28 Sep 1996 23:00:52 -0400 (EDT) Received: from localhost (chuckr@localhost) by fiber.eng.umd.edu (8.7.5/8.7.3) with SMTP id XAA02540; Sat, 28 Sep 1996 23:00:52 -0400 (EDT) X-Authentication-Warning: fiber.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 28 Sep 1996 23:00:51 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@fiber.eng.umd.edu To: dwhite@resnet.uoregon.edu cc: Peter Childs , freebsd-doc@FreeBSD.ORG Subject: Re: ISDN handbook changes. 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 Sat, 28 Sep 1996, Doug White wrote: > On Sun, 29 Sep 1996, Peter Childs wrote: > > > : I have incorperated all feedback into a new document. The following is > > : a drop in replacement for /usr/src/share/doc/handbook/isdn.sgml > > > > Great stuff. > > > > What is the general way-to-get-it-done with the docs > > project? Is it a case of posting here, or submitting via > > send-pr? If you document what and where you put stuff using send-pr, it's MUCH less likely to be forgotten! > > Now see, this is something we need to work on: documenting how to submit > documentation. :-) > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-doc Sat Sep 28 23:28:21 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA07851 for doc-outgoing; Sat, 28 Sep 1996 23:28:21 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA07823 for ; Sat, 28 Sep 1996 23:28:18 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA02436; Sat, 28 Sep 1996 22:27:43 -0800 Date: Sun, 29 Sep 1996 06:28:52 +0000 () From: hmmm To: doc@freebsd.org Subject: implemented 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 got some suggestions, and wanted to let you know that i implemented them. (no more mv vi or bad colors ... :) http://www.alaska.net/~hmmm/pcw01.htm