HDTenEightyP/NetNews huggingface dataset:
From: vikki@e40-008-9.MIT.EDU (Vikki King)
Subject: 3c503 AUI support?
Organization: Columbia University Center for Telecommunications Research
X-Newsreader: Tin 1.1 PL4
Date: Wed, 26 Aug 1992 05:10:10 GMT
X-Posted-From: e40-008-9.mit.edu
X-Posted-Through: sol.ctr.columbia.edu

Hi!

     Is anyone using a 3c503 ethernet adapter with the AUI port rather than
the coax connector?  Our whole net is 10BT.  I know that when using a 3c503
card in a Novell Netware server you have to explicitly tell the o/s to use the
AUI port if that's your configuration.  Since I seem to be getting notthing but
silence from my 3c503 and 386BSD on our 10BT LAN, I figure that the kernel is
assuming the connection to the LAN is via the coax port.  Anyone have any tips?

-John
jackson@a1.mec.mass.edu
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: [386BSD]: DEPCA support in future?
Date: 31 Aug 92 08:45:03 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Aug28.153333.3797@desire.wright.edu> ejones@desire.wright.edu writes:

>Are there any plans to include a DEC DEPCA ethernet card in the supported
>ethernet contollers? I have a 16 bit DEC card that I really like, but
>in order to use 386BSD I need to swap it with a 3com503 board. Also, will
>it be possible in the future to run X386 on a VGA screen instead of SVGA?
>Thanks for the help.

>	Ed Jones
>	Wright State University
>	ejones@desire.wright.edu

If my memory serves me right, the DEPCA uses an INTEL 82586 LANCE. There was
a recent posting for an "ie_driver" based on this chip. It should work, or it
should be not too difficult to modify it.

X386 will run with a standard VGA card, in 640x480 resolution with an
entry in Xconfig for the 25 or 28 MHz clocks which are always present.

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: tinguely@plains.NoDak.edu (Mark Tinguely)
Newsgroups: comp.unix.bsd
Subject: Re: (386BSD) finger
Date: 24 Aug 92 03:13:12 GMT
Article-I.D.: plains.19854
Organization: North Dakota State University

>In article <AeZf8Pi00WB3EqYkQj@andrew.cmu.edu> Tao Jiang <tj2n+@andrew.cmu.edu> writes:
>>I had a problem in using finger (or users etc.) command in X386.
>>Whenever I execute finger, it says that: No one logged on. But
 [some deleted]
>  Consequently anything that looks at /etc/utmp, including ttyname(3),
>won't find your session.

 utmp has been move but the change was not compiled into X386. Soft link
 /etc/utmp to /var/run/utmp (for  `w' `who' `f').
  
Newsgroups: comp.unix.bsd
From: jlu@mcs213i.cs.umr.edu (Eric Jui-Lin Lu)
Subject: Re: Some questions right after installation ....
Date: Mon, 31 Aug 1992 04:30:24 GMT
Organization: University of Missouri - Rolla

There are some progress during the weekend.  So, the questions are
changed.

In article <1992Aug30.001828.434@umr.edu> I writes:
>
> [some stuff deleted]
>
>1. How to create pseudo ttys'?  What are their major and minor numbers
>   ? And how many will be sufficient to run X window?

I have done this by MAKEDEV in /dev.

>2. I couldn't make "screen" run?  Is this related to (1)?  When I ran
>   screen, it came up a kinda new screen and hang.

Solved when (1) was solved.

>3. I can use kermit when I'm a su, but not when I'm a regular user.
>   In other words, it was installed incorrectly.  Something need to
>

Solved.

>4. Is it possible to have vt100 emulation when I login?  If I remembered
>   coorectly, I didn't see any vt100 entry in /etc/termcap.

Only this is still in question.

Thanks!

>
>I'll halt here. I have more to come.  Thanks in advance!  You can
>either post here or email me at jlu@cs.umr.edu.  Since I didn't
>see any of these problems in FAQ (may be too trivial), it may be
>helpful to post your suggestions here.  If there are sufficient
>interests, I'll post a summary.
>
>   --jlu
>
>-- 
>***************************************---       Grad. student 		---*
>* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
>* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
>***************************************---   Univ. of Missouri-Rolla    ---*


-- 
***************************************---       Grad. student 		---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
From: jlu@cs.umr.edu (Eric Jui-Lin Lu)
Newsgroups: comp.unix.bsd
Subject: Some questions right after installation ....
Date: 30 Aug 92 00:18:28 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213e.cs.umr.edu

Greetings *,

First of all, thanks to William Jolitz and all the contributors to the
success of 386bsd.

With the newly arrived 200MB IDE HD, I have successfully installed
386bsd into my HD, though my old WD 40MB IDE still have trouble
to boot up correctly.  After playing with it for 2 nights, I need
help to solve the following problems:

1. How to create pseudo ttys'?  What are their major and minor numbers
   ? And how many will be sufficient to run X window?
2. I couldn't make "screen" run?  Is this related to (1)?  When I ran
   screen, it came up a kinda new screen and hang.
3. I can use kermit when I'm a su, but not when I'm a regular user.
   In other words, it was installed incorrectly.  Something need to
   set.  The error message I got is:
            Error opening /dev/tty
            congm: permission denied
            /var/spool/lock: permission denied

  BTW, there is only one tty in my /dev dir.  How to create more?
  (the major, minor numbers and how many are suff? )
4. Is it possible to have vt100 emulation when I login?  If I remembered
   coorectly, I didn't see any vt100 entry in /etc/termcap.

I'll halt here. I have more to come.  Thanks in advance!  You can
either post here or email me at jlu@cs.umr.edu.  Since I didn't
see any of these problems in FAQ (may be too trivial), it may be
helpful to post your suggestions here.  If there are sufficient
interests, I'll post a summary.

   --jlu

-- 
***************************************---       Grad. student 		---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
From: blile@thesis1.med.uth.tmc.edu (BUD W. LILE)
Newsgroups: comp.unix.bsd
Subject: X386 install
Date: 4 Sep 1992 03:01:05 GMT
Organization: University of Texas Medical School at Houston
Originator: blile@thesis1.med.uth.tmc.edu

I'm posting this question for my roommate.

He has installed X386 on his 386BSD system.   Created the configuration
file.
 
When he tries to start X, he gets a message CONNOT OPEN /dev/vga!  

What is this device, is it just a renamed console or what.  If its 
a special device driver where is the source code?
 
Also, are there any good install intructions or does one go for broke or
did he just miss them?
 
Please just post to the net as he does have RN access.

thanks
B lile
University of Texas Medical School at Houston
Newsgroups: comp.unix.bsd
From: tom@izf.tno.nl (Tom Vijlbrief)
Subject: installing 386bsd-0.1 on a Compaq
Organization: TNO Institute for Perception
Date: Tue, 1 Sep 1992 13:16:25 GMT

Hi,


I have been away for a while and I wondered if the problem
of installing 386bsd-0.1 on a Compaq machine has been solved.
(The machine keeps rebooting from the installation floppy)



Thanks for any hints !!!

Tom
===============================================================================
Tom Vijlbrief
TNO Institute for Perception		Phone: +31 34 63 562 11
P.O. Box 23				Fax:   +31 34 63 539 77
3769 ZG  Soesterberg			E-mail: tom@izf.tno.nl
Newsgroups: comp.unix.bsd
From: sja@world.std.com (Stuart J Adams)
Subject: Where is comp.unix.bsd archived ???
Organization: The World Public Access UNIX, Brookline, MA
Date: Tue, 1 Sep 1992 20:12:02 GMT

Is there an archive site for comp.unix.bsd ???


Thanks,
Stuart Adams
sja@world.std.com

Newsgroups: comp.unix.bsd
From: fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Subject: Re: Where is comp.unix.bsd archived ???
Organization: United States Environmental Protection Agency
Date: Wed, 2 Sep 1992 11:55:55 GMT

In article <Btx1G2.4t2@world.std.com>, Stuart J Adams writes:
Is there an archive site for comp.unix.bsd ???


I maintain a "culled" archive at: 

	sunvis.rtpnc.epa.gov:~/pub/386bsd/culled.news


-- 
-------------------------------------------------
Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
Unisys/U.S. EPA		(919)541-2297

Newsgroups: comp.unix.bsd
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Subject: Re: SCSI-2 tape and disk drives recommendations
Organization: Applied Math, University of Bonn, Germany
Distribution: comp
Date: Wed, 26 Aug 1992 10:58:36 GMT

In article <JOSHUA5.92Aug25222622@csa.bu.edu> joshua5@cs.bu.edu writes:
>I'm looking for recommendations on manufacturers of SCSI disks and tape
>drives that work with an Adaptec 1542b controller.
[...]
>I have been cautioned against
>Figitzsu drives, don't know much about Maxtor and have had no problems with
>Seagate.

I'd stay away from Figitzsu.  On the other hand, I can only recommend that you
get a Fujitsu disk drive :-)  I'm using one with 386BSD.  I bought an IBM disk,
model 0663-L12.  This is a piece of crap.  I sent it back and am now waiting
for Fujitsu to release its announced 3.5" 1 GB disk.

>   I'm looking for opinions on speed, noise and reliability.  I'm
>leaning towards a Seagate drive.  

There are several different lines sold under the Seagate name.  Most of them
have problems, or so I've heard.  I've stayed clear of them. 

>I have been told that the BSDi recommended Wangtek Archive 2150s QIC-150
>tape drive is not "current".

I have a Wangtek 5150 which works fine.  Archive streamers are supposed to be
very good as well.

-- Volker

-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
From: tony@hacgate.SCG.HAC.COM (Tony Reeves)
Newsgroups: comp.unix.bsd
Subject: how to get 386bsd
Date: 3 Sep 92 21:50:36 GMT
Reply-To: tony@hacgate.UUCP (Tony Reeves)
Distribution: usa
Organization: Hughes Aircraft Co., El Segundo, CA

I hope this is the right place to ask this, if not I'm sorry (please point me in the
right place)...


I'm trying to find 386bsd to load onto a i386 machine. I thought I found it, I got
bindist and etcdist. However the files appear messed up. They appear to be compressed
cpio files. when I uncompress them and use cpio I get an error reading the files. 
is there a place I can write to, send disks, and get an installable version for a 386
pc?


-- 
Why did the Roman Empire Collapse? What is latin for Office Automation?
---- The opitions expressed here are mine and have nothing to do with Hughes
Aircraft Co. -- So there! tony@hacgate.hac.com
From: paoletti@comp/unix/bsdps.msu.edu (David R. Paoletti)
Newsgroups: comp.unix.bsd
Subject: Re: backup w/ compression for UN*X?
Date: 3 Sep 92 15:52:27 GMT
Organization: Dept. of Computer Science, Michigan State University
Originator: paoletti@pacific.cps.msu.edu

Basically, people have responded to my post by pointing out
that you can pipe through the compress program.  I know to
use tar, compress, cpio, dd, pipes, etc.  I should have
included the following point in my original post:

If you pipe through the compress program, doesn't it write
its compression/translation table at the beginning of the
output that it produces?  What happens if the beginning of
the tape or the first disk is damaged?  Or am I incorrect
in assuming that compress works this way?

Dave Paoletti :)
From: smg@physiology.oxford.ac.uk (Steve Gough)
Newsgroups: comp.unix.bsd
Subject: Booting 386BSD from second IDE drive?
Date: 1 Sep 92 14:46:58 GMT
Organization: Physiology Department, Oxford University, Oxford, UK.
Originator: smg@motor.physiol


I have installed 386BSD on a whole drive (which was surprisingly easy,
thanks to the install program).  At the moment to switch between 
booting DOS or BSD, I swap drive cables, change the CMOS drive parameters
and reboot---there has to be an easier way!

The FAQ mentions setting active partitions on a single drive, but
nothing about booting from a second drive.

Presumably I'd have to boot from a floppy and then load unix from
the IDE drive.  Is there the equivalent of Sun's `b (,,)' monitor
command?

I also thought that reboot/shutdown/halt might offer a solution,
but haven't found one yet.

Steve.
-- 
 Stephen Gough               McDonnell-Pew Centre For Cognitive Neuroscience
 smg@physiol.ox.ac.uk        University Laboratory Of Physiology
 tel: +44 865 272514         Parks Road
 fax: +44 865 272469         Oxford OX1 3PT
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: [386BSD] init leaves improper signal mask
Keywords: init, signals
Reply-To: pk@cs.few.eur.nl
Organization: Erasmus University Rotterdam
Date: Fri, 4 Sep 1992 16:01:46 GMT

init doesn't set up the proper signal disposition for the process (sh) it
creates to run /etc/rc. While all signal handlers are reset to SIG_DFL, the
signal mask is left unchanged causing SIGHUP and SIGTERM to be masked in
all daemons started from /etc/rc.

This can be fixed by adding a `sigsetmask(0)' to the macro SIGNALSFORCHILD
in init.c. This makes "kill -HUP `cat /var/run/syslog.pid`" work again.

-pk

Diffs of my current init.c against the original distribution:

------- init.c -------
83c83,84
< 	signal(SIGTTIN, SIG_DFL); signal(SIGTTOU, SIG_DFL);
---
> 	signal(SIGTTIN, SIG_DFL); signal(SIGTTOU, SIG_DFL); \
> 	sigsetmask(0);
217c218
< 		while(wait(&status) != pid)
---
> 		while(wait(&status) != pid);
399c400
< 	exit(1);
---
> 	_exit(1);
From: ccml@hippo.ru.ac.za (Mike Lawrie)
Newsgroups: comp.unix.bsd
Subject: 386bsd: {src,etc}dist won't extract
Date: 30 Aug 92 08:46:04 GMT
Article-I.D.: hippo.1992Aug30.084604.18558
Organization: Rhodes University, Grahamstown, South Africa

The message "too many open files" occurs when I extract srcdist and
bindist, but there is no problem with bindist.

There is 560+ Mbytes available in the 386bsd partition.

Can anyone advise how they managed to do the extractions?

Mike
--
Mike Lawrie                                    <ccml@hippo.ru.ac.za>
Director, Computing Services                   ph +27 461 22023 x 279
Rhodes University, Drostdy Rd                  fx +27 461 25049
Grahamstown 6140, South Africa
-- 
Mike Lawrie                                    <ccml@hippo.ru.ac.za>
Director, Computing Services                   ph +27 461 22023 x 279
Rhodes University, Drostdy Rd                  fx +27 461 25049
Grahamstown 6140, South Africa
Newsgroups: comp.unix.bsd
From: jwilliam@stsci.EDU (John Williams)
Subject: 386BSD and the 486DX2
Reply-To: jwilliam@stsci.EDU (John Williams)
Organization: Space Telescope Science Institute
Date: Wed, 2 Sep 1992 12:55:15 GMT

--
In the September 15, 1992 issue of PC Magazine, they reviewed 63 DX2's.  My 
question is: Of those in the 2k - 3k price range, do any seem like particularly good
candidates for running 386BSD or on the other hand particularly poor choices?

*****************************************************************************
*John Williams - jwilliam@stsci.edu      The universe is full of magical *
*Space Telescope Science Institute       things patiently waiting for	   *
*Baltimore, MD.			our wits to grow sharper.	   *
From: hongman@cathedral.cerc.wvu.wvnet.edu (Guo Hongman)
Newsgroups: comp.unix.bsd
Subject: need FAQ.
Date: 29 Aug 92 15:12:59 GMT


 Can anyone tell where is FAQ or email it to me ?

 Thanks in advance !
Newsgroups: comp.unix.bsd
From: tih@barsoom.nhh.no (Tom Ivar Helbekkmo)
Subject: Re: 386BSD: New wd driver handles multiple disks, bad sectoring.
Organization: Norwegian School of Economics
Date: Wed, 26 Aug 1992 06:49:29 GMT

I wrote:

>For those who are interested, my heavily modified wd driver for
>386bsd is now available by anonymous ftp from barsoom.nhh.no.

And I've already made changes!  :-)  It was brought to my attention
that my changes to mkioconf.c (part of config) weren't compatible
with Chris Demetriou's driver flags patches, which I hadn't installed.
So, I've cleaned up my stuff a bit, fixed the indentation I stupidly
changed in fd.c and mkioconf.c, and made two versions of the relevant
files available -- with or without Chris's patches installed.

(Chris' and my changes can't be made into mutually exclusive patches,
since they change some of the same things.)

As before, the new stuff is available by anonymous ftp to my DS5000,
barsoom.nhh.no.  The README file explains things, and the files that
have names ending in .COM.CGD include the driver flags patches.

-tih
--
Tom Ivar Helbekkmo, NHH, Bergen, Norway.  Telephone: +47-5-959205
Postmaster for domain nhh.no.   Internet mail: tih@barsoom.nhh.no
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: oneko does work under 386BSD with X386
Keywords: oneko, X386
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Sun, 23 Aug 1992 16:53:19 GMT

Hello,

  export.lcs.mit.edu: ~ftp/contrib/oneko-1.1b.tar.Z does work under 386BSD
with X386 without any modification.

It's easy to get it running, but it's hard to stop it :-)

Henry

-- 
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
juengst@saph2.physik.uni-bonn.de [131.220.221.12]
juengst@pib1.physik.uni-bonn.de  [131.220.221.2] (strange particle)

I'm only speaking for myself, but not for anybody else !
From: wfs@blancmange.ma.utexas.edu (Bill Schelter)
Newsgroups: comp.unix.bsd
Subject: 386bsd on notebooks?
Date: 25 Aug 92 16:56:45 GMT
Reply-To: wfs@nicolas.ma.utexas.edu
Distribution: comp.unix.bsd
Organization: /u/wfs/.organization


I would like to get a notebook 386 or 486 for use with 386bsd.

If anyone has experience with particular hardware, I would like
to hear about it.

I will summarize the results and post them to this list.

Bill Schelter

--


      \_|_/
   - /     \ -                
   - \ _ _ / -            el brib'on viva.
      / | \
Newsgroups: comp.unix.bsd
From: bob@MorningStar.Com (Bob Sutterfield)
Subject: getnetmaskent()?
Organization: Morning Star Technologies
Date: Fri, 4 Sep 1992 16:04:38 GMT

BSD's getnetent() family of routines works with the contents of
/etc/networks.  Is there a similar getnetmaskent() family for the
information contained in /etc/netmasks?  I note that the Tahoe (or is
it Reno?) <netdb.h> has no mention of a subnet mask, nor of a file
where it might be found.

Must I actually open() the file and parse it myself?  How barbaric! :-)
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: Incorrect Install Procedure in FAQ
Date: 31 Aug 92 01:33:10 GMT
Followup-To: comp.unix.bsd
Organization: University of Alaska Computer Network

In the 386BSD 0.1 FAQ revision date 09 Aug 92 there is an error in one of
the installation procedures.  In section 2.04, 'How do I get 0.1 installed
with "real" partitionning?', there is a description of how to install BIN01
without using the happy fun EXTRACT program.  The procedure neglects to
mention that you have to run a device install script after step 21, the
decompression of the bin01.* files.  The result of this is that /dev/kmem
doesn't get created, the rc script complains of its absence, and telnetd
refuses to allow incoming telnet sessions.

The original discussion on installing 386BSD 0.1 on a 40 mb hard drive by
using the script:
# (for i in /tmp/bin01.*; do
> cat $i && rm $1
> done
> ) | uncompress | cpio -iadm
also negelcts to mention this.

I have done this in the past once and had to reinstall 386BSD to get it to
work correctly.  I've just done this a second time (fool me once, shame on
you, fool me twice....) and I'm going to try and recover the original
script from the bin01 files to see if running it afterwards will help.  If
it doesn't, I'll post the additional file you need to run that these
procedures leave out.

In the mean time, is there an easier way to patch this and does anyone know
off the top of his/her head what I did wrong.

 - jcb

______________________________________________________________________________
                                        |    jay@seaspray.uacn.alaska.edu
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD]
Date: 29 Aug 92 19:46:00 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

stripes@pix.com (Josh Osborne) writes:

>But I don't think 386BSD _currently_ has support for PPP, or AX.25 (and
>there may be a few other things 386BSD doesn't have), also NOS seems to
>lose way fewer charactors at high speeds.  Hopefully we can fix all that,
>but for the moment "NOS is not needed" isn't quite true...

Character loss is normally in the device-level code.  If you're using
a normal PC serial interface, the kernel must respond to an interrupt
for each character before the next is ready.  At 9600 bps this
requires an interrupt latency somewhat less than 1 msec.  It took
several months of tweaking the I/O on Linux to get SLIP to work
reliably there on a slow machine.  Moving the actual TCP
implementation into the kernel would not have helped.  Indeed it may
make things worse, as there's more code in the kernel that could
potentially slow down interrupt latency.  I don't know how 386BSD is
doing its interrupt handling, but the most likely problems would be
that code called from the clock interrupt handler (which could include
all the TCP protocol processing if somebody wasn't careful) could be
taking longer than 1 msec to complete).  That's because the clock is
the device that's most likely to be at a higher priority than the
serial interrupt.

It is by no means clear to me that doing TCP in the kernel is going to
result in the best performance with SLIP.  KA9Q under Linux with VJ
header compression gives interactive response that feels like a
terminal (except when I let the modem use MNP5, when I can feel the
delay caused by that protocol).  Under SunOS 4.1.1 with the standard
kernel SLIP implementation I find SLIP painful.  Of course Sun has
notoriously bad serial handling, so it may be that 386BSD will do
better.  But if you think about how the data is being handled, how
many context switches are being done, etc., it's not obvious to me
that there's a performance advantage to doing TCP/IP in the kernel.
Where it does win is in the ability to run TCP application from
multiple processes.  Thus you can have telnet sessions in several
windows, servers that are independent of your telnet sessions, etc.
This is obviously a great advantage, and certainly justifies doing the
kernel implementation.  But for a PC at home, where you want a couple
of telnet sessions and some FTP's now or then, the advantage is not as
dramatic.  Depending upon how carefully the implementors have thought
about interrupt handling, you could actually get better performance
with KA9Q for SLIP.

This posting seems to imply that 386BSD is losing characters in SLIP.
Even with a 368SX/16, there is no reason that you should ever lose
characters, if your interrupt handling is properly done.
Newsgroups: comp.unix.bsd