HDTenEightyP/NetNews huggingface dataset:
From: hasty@netcom.com (Amancio Hasty Jr)
Newsgroups: comp.unix.bsd
Subject: Re: (386BSD) Modems and com ports
Keywords: internal or external?
Date: 21 Aug 92 02:53:29 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)


I think that if the com driver is strap to interrupt levels less than 
disk level, then under heavy I/O activities the com drivers will drop
characters. If the com drivers is split into two parts:
(a) a routine at  high level interrupt level less than splhigh and at
 least as high  as diskio that just collects the characters and queues 
 the requests to be processed at a lower priority.

(b) essential the same com driver that de-queues the request from its
    higher level routine

If such a scheme is not implemented, it is conceivable that the system
may lock out spltty interrupts long enough for the uart to drop characters.

The above outlinde strategy has been implemented in Unix systems for pcs
with good results for instance the system being able to drive four
com ports at 9600  without dropping a single character.

Cheers,
Amancio Hasty
Newsgroups: comp.unix.bsd
From: george@gloria.csi.compuserve.com (George M. Jones)
Subject: filesystem dissapears
Reply-To: gjones@csi.CompuServe.com
Organization: CompuServe, Inc.
Distribution: comp
Date: Fri, 21 Aug 1992 13:55:33 GMT

I'm trying to get 386BSD 0.1 installed on a CompuDyne 386/33 (UMC chipset,
AMI BIOS, western digital 120 meg IDE drive (startup probe reports
"WDC AC2120M", Diamond Speedstar 24 VGA).

The problem I am seeing is that the filesystem seems to just
"dissapear" randomly.  I've gotten the system installed on the hard
drive (in a 97 meg partition, letting the install procedure use the
default labeling), it boots, I can do an "ls" of the root directory,
but subsequent "ls"'s show nothing.  "pwd" says "can't exec /bin/pwd"
and so forth.

I had the dissapearing filesystem problem on the floppy during the install a
few times, but once I put it on the hard drive it happens consistenly.

I've turned off anyting in the BIOS that looks like it would remap
memory, I've removed all non-essential cards from the machine, tried a
different IDE controller that has been used to successfully boot
386BSD on another system with no apparent effect.

Clues ?

---George Jones


--
CompuServe, Inc.  5000 Arlington Centre Blvd., Columubs, Ohio, 43220 
EMAIL: gjones@csi.compuserve.com VOICE: +1 614 442 2088
"Progress might have been all right once, but it went on too long."  Ogden Nash

Newsgroups: comp.unix.bsd
From: cchase@watson.ibm.com (Craig Chase)
Subject: (386BSD) Modems and com ports
Date: Thu, 20 Aug 1992 17:15:57 GMT
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: Electrical Engineering, Cornell University, Ithaca NY
Keywords: internal or external?

So, before I go plunk $250+ on a modem I wonder if someone could
clarify the situation with dropped characters on a serial line.

I understand that the 386BSD device drivers have trouble keeping
up with high-speed serial communications, but how much trouble
and how fast?  The FAQ lists 38K bps as higher than you're likely
to be able to go, does this mean the 19.2K would be OK with sl/ip?

(BTW: 19.2K being MNP5 + V.32 and quite doable on a modem
 with V.32bis + V.42bis you can go up to 56K)

My *real* question is, will it matter if I get an internal modem
or an external modem?  From a performance standpoint, it would
seem that an internal modem has a little less hardware between the
phone line and the bus, and so might have less trouble at the
higher performance rates.  But then, I tend to doubt that it 
makes any difference you could notice from a device driver.

On the other side of the coin, an external modem could conceivably
be hooked up to a smart (buffering?) serial card that might
solve the dropped character problem altogether.

Of course, external modems cost about $20-25 more...

Any thoughts?

Craig
cchase@ee.cornell.edu
Newsgroups: comp.unix.bsd
Subject: 386bsd cross-compile environment?
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Date: Fri, 21 Aug 1992 19:56:43 GMT
Reply-To: ewanco@kalvin.enet.dec.com
Organization: Digital Equipment Corporation
Keywords: cross compile 386bsd


Has anyone successfully developed a cross-compilation environment for 386bsd?
Say, on a DECstation?  Can you just unpack the sources and compile the C
compiler, assembler, loader, etc? Any tips?

Thanks
Eric
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
From: satmech@ecst.csuchico.edu (satmech)
Newsgroups: comp.unix.bsd
Subject: Diamond 24, stealth, vi, X
Date: 19 Aug 92 07:10:02 GMT
Organization: California State University, Chico

How are the drivers going for the Diamond Stealth and 24bit cards? Has
anyone completed them?  Also, will X386 work with a logitech bus mouse?
 
Whoever asked about kermit, it's on utkux1.utk.edu in /pub/386BSD/...
somewhere, you can use archie to find it.

I've found a small bug in vi or pccons that showed up while I was adding  
the new lp driver, vi will blank out a line when lines are deleted,
the line is still there, just not on the screen.  Anyone fix this?

satmech@cscihp.ecst.csuchico.edu
Newsgroups: comp.unix.bsd
From: drenze@icaen.uiowa.edu (Douglass J. Renze)
Subject: FAQ?
Date: Thu, 13 Aug 1992 22:50:28 GMT
Organization: University of Iowa, Iowa City, IA, USA
Keywords: where?

I only just began reading this group.  Where is the FAQ (before I start asking
questions which may/bay not be in it)?  Please e-mail me directly.


-- 
| Douglas J Renze            | "Jerry [Brown] is the equivalent of a          |
| drenze@icaen.uiowa.edu     |  drive-by shooting."                           |
| drenze@chop.isca.uiowa.edu |                                                |
| drenze@aol.com             |         * NPR's Morning Edition, 13 July 1992  |


Newsgroups: comp.unix.bsd
From: grefen@wilbur.uni-mainz.de (Stefan Grefen)
Subject: Re: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??]
Organization: Johannes Gutenberg Universitaet Mainz
Date: Fri, 21 Aug 1992 07:12:37 GMT

In article <9208192322.28@rmkhome.UUCP>, rmk@rmkhome.UUCP (Rick Kelly) writes:
|> In article <1992Aug19.093937.14857@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes:
|> >
|> >>What platform did you have in mind?
|> >
|> >Atari TT or Falcon (68030).  But what I consider most important is the fact
Thats ok an Atari TT too I think.
|> >that - when done right - the binaries of all 680x0 implementations will be 
|> >interchangeable, just like the Minix versions for Atari, Mac and Amiga.
|> 
|> 
|> There is a 680x0 binary standard for SVR4 systems, but I'm not sure who
|> is supporting it besides Commodore.
Atari, their ASV (SVR4) uses it.(I know you can't buy in shop too day, 
but I have one :-) )
|> Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Stefan
-- 
Stefan Grefen   ---   Johannes Gutenberg University Mainz   ---    Germany
Email: grefen@goofy.zdv.uni-mainz.de       ---        Phone:  06131/392415

Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Taronga Park BBS
Date: Tue, 18 Aug 1992 13:11:04 GMT

In article <PHR.92Aug17195902@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>    True, we don't see examples of shrinkwrapped copylefted stuff at
>    the software houses.  Maybe a publisher should give it a try!

>Yes, we do.  See the ads in BYTE and other places from the Austin
>Code Works, for example.

I haven't seen any shrinkwrapped stuff from the ACW at Softwarehouse lately.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: bill@unixland.natick.ma.us (Bill Heiser)
Subject: adding a partition
Organization: Unixland Public Access Unix  (508) 655-3848
Date: Sat, 15 Aug 1992 16:10:43 GMT

I have 386BSD 0.1 running on a 386/25 with a 140mb Toshiba SCSI disk.
I have a dos5.0 partition (32mb), an extended 5.0 partition (32mb), and
a 77mb 386BSD partition.  If I were to decide I don't need the 32mb
extended dos partition, is there a way I can safely delete it and
mount it as a 386BSD filesystem?

Before I blow away my whole disk ... is it as simple as just using
dos fdisk to delete the extended partition, then using newfs to create
the filesystem on 386BSD?  What would the device name be?

Thanks,
Bill

-- 
bill@unixland.natick.ma.us                      ESIX Mailing List Moderator
Public Access UNIX/USENET/E-MAIL!  UUCP Accounts Available!  (508) 655-3848
5 lines  -  Located in Natick, MA   USA    Supporting V.32/PEP/V.42bis, etc.
Newsgroups: comp.unix.bsd
Subject: Is it possible to use FIFOs (named pipes) in 386BSD 0.1?
Reply-To: scott@lopez.marquette.MI.US
From: scott@clmqt.marquette.MI.US (Scott Reynolds)
Date: Sun, 16 Aug 1992 01:59:43 EDT

I added the FIFO option, hand twiddled the .depend file so that the
appropriate files, e.g. fifo_vnops.c would be compiled properly,
linked and installed the new kernel, and made a fifo with mkfifo(1).
I did a "cat fifoname &" and then said "echo hello >fifoname" -- and
wouldn't you know it, the machine hung.  Dead in the water, so to speak.
So now I wonder -- can it be done?  I have an application that would
prefer to use fifos as a portability consideration (it was written in a
XENIX environment).

If this can't be done, or my concept of fifos is totally wrong (which
could be true, admittedly) please let me know.  I'd appreciate hearing
whether or not this is possible.  Thanks!
--
Scott Reynolds
scott@{clmqt,lopez}.Marquette.MI.US
A094@NMUMUS.BITNET
From: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Newsgroups: comp.unix.bsd
Subject: A few questions on 386 BSD
Date: 18 Aug 92 18:36:32 GMT
Reply-To: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Organization: Columbia University

Hi, 

	I have a few questions about 386 BSD. Any response will be greatly
appreciated.

	(1) Has anyone installed 386 BSD along with OS/2 2.0 on the
	    same drive ? If so, how did you do it ?
	(2) Is it better to have 386 BSD on a dedicated system ?
	(3) What kind of SCSI adapters does 386 BSD support ?
	(4) Is it possible to boot 386 BSD off the second hard drive ?
	    Is possible to use a second hard drive at all ?
	(5) How much RAM will be adequate for program development, including
	    X windows ?

That's it for now !


       		                     	***********************
--cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
--cl45@cunixf.cc.columbia.edu		***********************
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: resize swap space?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Tue, 18 Aug 1992 14:36:45 GMT

If one of us had access to the source to the install program it
seems like it would not be all that difficult to have it ask
just one more question (``How much swap space do you want?'')
and perform the necessary calculations; and create a new
dist.fs with this install program...

I recall that someone asked for the source.  What became of this?

P.S. Don't send it to me.  I am saving my pennys to get a larger
disk drive so's I can unload the source tape and compile.... ;-(

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Disktab entries requested (was: Re: Tiny 386BSD boot problem w/IDE and Adaptec SCSI
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Wed, 19 Aug 1992 14:58:24 GMT

andrew@zone4.ocunix.on.ca (Andrew Low) writes:

>In article <1992Aug14.050157.10658@i88.isc.com> 
>mikebo@i88.isc.com (Michael Borowiec) writes:
[ Some text deleted - NB. ]

>All: I'm still confused about the bad sector allocation - can a mini
>tutorial for "designing a disktab entry" be placed in the faq?  That
>and how this relates to Bad144..
I would like to get the tutorial on "how to design a disktab entry", too.

Otherwise, is there an entry for the Fujitsu 520 MB (Model M2624SA) SCSI disk ?
And, I need one for the Conner CP3100 (100 MB SCSI), too.

Thanks for your help.

I can't wait for my 486/33 Mhz system to arrive next week to install 386BSD
on it.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
From: phr@soda.berkeley.edu (Paul Rubin)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Date: 17 Aug 92 11:20:28
Organization: CSUA/UCB
	<PHR.92Aug15214245@soda.berkeley.edu> <YSDIBS4@taronga.com>
	<9208162341.30@rmkhome.UUCP>
NNTP-Posting-Host: soda.berkeley.edu
In-reply-to: rmk@rmkhome.UUCP's message of 17 Aug 92 04:41:28 GMT

    >... Next, Sun (In Solaris 2), and I believe MIPS ship GCC with
    >their products, in some cases as the primary compilers.  This
    >sort of distribution is not practical for an operating system.

    And from reading comp.unix.solaris, I get the idea that a number
    of development shops will buy compilers for Solaris 2.0 because of
    the GNU Copyleft.

The copyleft does not prevent development shops from using GCC.
If they think it does, they haven't been paying attention, or they are
letting their decisions be controlled by paranoid knee-jerk reactions
instead of by intelligence.  I'm sure this makes Sun happy; there's
one born every minute, as the saying goes.  I don't see this as a
reason to let Sun and others make proprietary GCC's.  I can't see
any benefit of a non-copyleft GCC that could outweigh sacrificing
the hundreds of improvements, ports, etc. that people have been
allowed to contribute because the marketroids they work for weren't 
permitted to grab the improvements for themselves.

We saw the same situation with Unix, but it didn't work out so well.
Dozens of companies made proprietary improvements and fixes, so you
had your choice of N incompatible Unixes, each with a different subset
of the original bugs fixed.  One of the hopes of the GNU OS and its
copyleft is to prevent this from happening again.
Newsgroups: comp.unix.bsd
From: bzs@ussr.std.com (Barry Shein)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: The World
	<14809@ksr.com>
Date: Fri, 14 Aug 1992 23:28:19 GMT


John Woods brings out a good point that's worth underscoring.

Copyright is not only a binary condition, that is, something is either
copyright or it's not.

Based on how you've treated your copyright there are various shades of
limitations as to what you can do in the event of it being violated.

For starters, if you do not register a copyright with the US Copyright
Office (for US copyrights of course) you are pretty much limited to
cease and desist. Damages become difficult to impossible to sue for
under that law.

There are similar considerations for not handling your copyright
properly, I'm not comfortable enough with the details to try to
outline them.

Cease and desist can of course be powerful (how would you like to be
stuck with a warehouse full of books or whatever?) and can of course
be a basis for negotiating some valuable reconsideration (hey, i'll
give you a $25K if I can sell those books rather than junk them,
deal?), but you still may be very limited in your recourse (we weren't
selling any of those books anyhow, I'll call the recyclers, sorry
about that, <click>.)

--
        -Barry Shein

Software Tool & Die    | bzs@world.std.com          | uunet!world!bzs
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
Newsgroups: comp.unix.bsd
From: jim@ferkel.ucsb.edu (Jim Lick)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: University of California, Santa Barbara
Date: Tue, 18 Aug 1992 05:22:08 GMT

In <1992Aug18.020754.8683@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>How do you synchronize this with the $100 and/or "reasonable copying fee"
>from the GPL?  Charge $300 for the book?

You are under a false impression.  The GPL does NOT put a limit on what
someone may charge for an FSF product.  The limitation of a charge which
covers the cost of duplication applies only to source code for the product
in the case that source code was not provided in the sale product.  Thus,
you could easily sell a FSF product at a price where you could profit.
Let's say you want to sell GCC for $500.  If you include source code with
this, then you are done.  If you don't include source code, any customer can
come up later and ask for a copy of the source which you must provide at
cost.  In general if there is a savings in media costs for the main product
without source as opposed to with source, it would probably be more cost
effective in the long run to sell it without source.  But if you sell on
some large capacity media like tape or CD-ROM, you probably have plenty of
room left over, so you might as well throw it in and save the hassles later.

                            Jim Lick		       
Work: University of California	| Play: 1236 Camino Meleno
      Santa Barbara		|       Santa Barbara, CA 93111-1007
      Dept. of Mechanical Engr. |	(805) 964-2088 voice/msg
      2311 Engr II Building     |	(805) MUD-SPY1 data
      (805) 893-4113            |       jim@tcp.com
      jim@ferkel.ucsb.edu	| This space intentionally left blank
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: how to shutdown -todos?
Keywords: shutdown, booting
Date: 20 Aug 92 03:50:32 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <22231@venera.isi.edu>, allard@isi.edu (Dennis Allard) writes:
> I notice two shutdown programs.
> /usr/distbin/shutdown and /sbin/shutdown.
> 
> The distbin/ one understands -todos, the sbin/ one does not.
> 
> Why two shutdown programs?  What's the difference?  Why doesn't
> the sbin/ one understand -todos?

The net was discussing this quite a while ago - I do not think it was
ever quite understood.  IMHO, the -todos option should be included in 
/sbin/shutdown.  I thought the /usr/distbin programs were supposed to
be stripped down versions of the full function versions in the bin01 
distribution and were no longer necessary after installation.

> When I do /sbin/shutdown, it does a bunch of stuff and leaves me at
> the # prompt.  Then, if I execute it again, it does some more stuff
> and leaves me at login:.  Man shutdown does not really tell me enough
> to understand this behaviour.  What's going on?

Try "/sbin/shutdown -h now".  Its in that man page somewhere.

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
Xref: sparky comp.unix.bsd:4506 comp.bugs.4bsd:207
From: ws@tools.de (Wolfgang Solfrank)
Newsgroups: comp.unix.bsd,comp.bugs.4bsd
Subject: Re: 386BSD kernel bugs w/fixes
Date: 20 Aug 92 17:15:54 GMT
Followup-To: comp.unix.bsd
Organization: TooLs GmbH, Bonn, Germany
In-reply-to: davidg@agora.rain.com's message of 20 Aug 92 10:57:12 GMT


While I didn't check the other fixes, at least point 4 is incorrect.

In article <1992Aug20.105712.26856@agora.uucp> davidg@agora.rain.com (David Greenman) writes:

   4) The virtual memory system has a bug that will prevent a process from
	   growing in its virtual size greater than 6MB data/stack. This is
	   caused by the incorrect process limit being checked in /sys/vm/
	   vm_unix.c. As they are defined in /sys/i386/include/vmparam.h,
	   the constants DFLDSIZ and DFLSSIZ specify the initial limit (the
	   limit when the process is created in execve()) for a process. The
	   constants MAXTSIZ and MAXSSIZ specify the maximum that a process
	   can grow. These constants are copied into process zero's proc->
	   p_limit[] and are used as a prototype for all processes. rlim_cur
	   contains DFLDSIZ/DFLSSIZ, and rlim_max contains MAXDSIZ/MAXSSIZ.
	   rlim_max should therefore be used to limit the process's virtual
	   size growth. However, the check is against rlim_cur. The fix is
	   to change the check to rlim_max. One might also note that 6MB for
	   DFLDSIZ/DFLSSIZ in vmparam.h is very low and should be increased
	   to something more reasonable. Most vendors specify an initial
	   limit of 32MB.

The behavior of 386BSD is correct. All limits are always checked against
the current limits (rlim_cur). That's the purpose of these variables.
The maximum limits (rlim_max) are only there for limiting the normal user's
ability to increase the limits. These are checked when you try to increase
the current limit (see setrlimit(2)). Only the superuser can increase these.

--
ws@tools.de     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Motif on X386???
Organization: Weber State University  (Ogden, UT)
Date: Wed, 19 Aug 92 02:37:26 GMT

In article <1992Aug18.174802.9845@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes:
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>>I also saw problems with menus not coming active unless you let go of the
>>button popping up the menu, then quickly pressed it again (not in the menu
>>area) to get the menu selection bar to follow the mouse.
>
>Make sure you are using the latest com.c driver (with select()
>bug fixed).  But even then there is some problem with the mouse
>code in X386 as the very first button press is not seen until
>after you either release the button or move the mouse a bit.
>
>If you wish to track this problem down, check out file
>$X11R5/mit/server/ddx/x386/x386Io.c.  Routine x386MseEvents()
>seems to be the culprit.

Naw.  It recognized the mouse event; Motif, due to the register pop-order bug,
just didn't get the correct result from an X toolkit routine.  Adding a line
like ptr++; ptr--; forces the problem to go away (as does any lvalue reference
in the routine; the pop-order bug only occurs in routines where a register
is used as an lvalue of itself).

Using Motif 1.2's patched Xt routines fixed it.

I've had /dev/tty00 and /dev/tty01 instead of /dev/com1 and /dev/com2 since
about day 1, so I never had the select() problem personally, mostly because
I serendipitously fixed the select() in the com driver at the same time I
made it conform to my idea of "pretty".


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
From: gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 18 Aug 92 15:59:58 GMT
Organization: University of Virginia

In article <GTFIR8A@taronga.com> peter@taronga.com (Peter da Silva) writes:
#And while it's [MSDOS] a screaming horror from
#the sewers of hell, it *does* run out of the box without any diddling, and
#has a zillion applications for it.

Then how come every time my brother wants to install a new program, I
have to use EDLIN to edit the config.sys file on his pc?


--
-Greg Hennessy, University of Virginia
 USPS Mail:     Astronomy Department, Charlottesville, VA 22903-2475 USA
 Internet:      gsh7w@virginia.edu  
 UUCP:		...!uunet!virginia!gsh7w
Newsgroups: comp.unix.bsd