HDTenEightyP/NetNews huggingface dataset:
From: alm@netcom.com (Andrew Moore)
Subject: Re: [386BSD] Problems with a SMC Elite16 (WD8013EPC)
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 7 Nov 1992 02:14:51 GMT

In article <BxAvJG.ByF@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>We have a WD "Elite" 8-bit ethernet board that won't retain its
>settings (as set up by "ezsetup") after power off.
>
>That's not supposed to happen, and believe me, it was a bitch to figure
>out.

Me too. Actually it was an SMC 8003EP.  The real kicker is that I could
ping to and from the bad system if I changed the broadcast to the IP
address of the remote.  I still don't understand this (echo
maybe?), but putting printf's in the we driver revealed that there were no
receive interrupts when it was allegedly receiving.  To the source!
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: jlwright@nyx.cs.du.edu (Jason Wright)
Subject: Which SCSI to get?
Keywords: SCSI
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Tue, 10 Nov 92 21:48:18 GMT

I'm in the market for a SCSI disc and controller for 386bsd, and
have NO idea which adapter to get.  The store I just got off the
phone with told me, "You don't want an Adaptek controlller, get...."

My question is: which SCSI controllers are known to work with 386bsd,
in addition to the Adaptek?  Is anyone using the Always Tech. ISA-2000
board (this is the one the store recommended.)?

Please send reponses be email: wrightj@hamlet.uncg.edu
I'll summarize to the net.

Thank you in advance!

Jason L. Wright
wrightj@hamlet.uncg.edu		wrightj@uncg (BITNET)

Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: [386bsd] patches for bash 1.12
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 7 Nov 1992 02:34:01 GMT

In article <5TZTTB2w165w@tsoft.sf-bay.org> bbs.barfeau@tsoft.sf-bay.org (David Fox) writes:
>Has anyone successfully compiled bash version 1.12 for 386bsd?  Could
>you email me those patches or tell me where I could get them?  I got
>the thing from GNU last night but it doesn't exactly compile correctly.

here's some old postings:

From: cflatter@nrao.edu (Chris Flatters)
Subject: Bash (Was: Help with posting news under BSD/386 wa)
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Thu, 23 Jul 1992 21:55:24 GMT

In article 2902@mks.com, fredw@mks.com (Fred Walter) writes:
>I suggest you replace the Bourne Shell that comes with 386BSD 0.1 with
>GNU's Bash.
>
>No, I don't know if it will easily compile under 386BSD 0.1. 

Yes it will.  The only problem is that the autoconfiguration procedures
mistakenly think that 386BSD is a USGr3 system.  I was too lazy to
find out what the problem was and just fixed up the bash-Makefile
that is generated: just change OS from USG to Bsd; remove the -DUSGr3
and remove -lPW.

Alternatively, I think that there is a bash binary in the etc01 archive.

	Chris Flatters
	cflatter@nrao.edu



From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Subject: Re: Bash (Was: Help with posting news under BSD/386 wa)
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Fri, 24 Jul 92 19:54:32 GMT

In article <1992Jul23.215524.29293@nrao.edu> cflatter@nrao.edu writes:

>Yes it will.  The only problem is that the autoconfiguration procedures
>mistakenly think that 386BSD is a USGr3 system.

(It actually doesn't find anything it recognizes, so it defaults to
`generic' 386 Unix -- System V.3.)

Try adding this to the `i386' section of machines.h (with the rest of
the i386 descriptions).  This is what I currently have for Bash 1.13.

/* BSDI BSD/386 running on a 386 or 486. */
#  if !defined (done386) && defined (bsdi)
#    define done386
#    define M_MACHINE "i386"
#    define M_OS Bsd
#    define HAVE_SYS_SIGLIST
#    define HAVE_SETLINEBUF
#    define HAVE_GETGROUPS
#    define HAVE_VFPRINTF
#    define HAVE_STRERROR
#    define VOID_SIGHANDLER
#    define HAVE_DIRENT
#  endif /* !done386 && bsdi */
-- 
``The use of history as therapy means the corruption of history as history.''
	-- Arthur Schlesinger

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
From: mccrory@uservx.plk.af.mil
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Configuring a new Kernel
Date: 8 Nov 92 19:28:13 GMT
Organization: Phillips Laboratory - Kirtland AFB

In article <BxEztt.7z5@acsu.buffalo.edu>, visnurpk@ubvmsb.cc.buffalo.edu (Rich Kernin) writes:
> Hi,
> 
>    I've installed the src01 package recently, and want to upgrade the
> kernel, using the patchkit, so I may keep current.  The problem is that
> I haven't found out how to do this yet... :-(  I've read the man page for
> config(8), but didn't get any specifics from it (ie. how do you create a
> file that config will process?).  Could someone please point me in the right
> direction?  I've only been working with BSD for a week or two, and would
> very much like to get kernel experience (previous systems were commercial,
> and Linux was easier to grasp since it is smaller).  Any/all suggestions
> very much appreciated!
> 
> -Rich
> 
> ---------------------------------------------------------------------------
> Richard P. Kernin                  Internet: visnurpk@ubvmsc.cc.buffalo.edu
> Niagara University                   BITNET: visnurpk@ubvmsc.BITNET
> Administrative Computer Center
i> ---------------------------------------------------------------------------
I'm in the same boat., have installed the patches and would appreciate any
assistence.  This is my first attempt at UNIX.  I am a VDDP--very dumb dos
programmer!  <|:-)

             
Roy A. McCrory
Kirtland AFB, NM
INTERNET: MCCRORY@uservx.plk.af.mil
-----------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: Formating 5.25" disk
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Distribution: usa
Date: Fri, 6 Nov 1992 14:36:03 GMT

YEO YEK CHONG (yeoy@a.cs.okstate.edu) wrote:
: 	Question 1:
: 	How do I format a 5.25" floppy?  I have tried using "floppy"
: instead of "floppy3".
floppy=floppy3=3in=3.5in

Use floppy5 or 5in ......
: 
: 	Question 2:
: 	What are fdboot and bootfd?  man specify that they are packid and 

fdboot is the 512 byte which will be loaded to address 0x7c00 on boot-up.

fdboot then executes to load the subsequent sectors 2-13 which is where
bootfd is put. bootfd therefor must be 7.5kbyte in size.

fdboot and bootfd are both binary, no header at all,

: priboot sector respectively, but specifically I meant to ask if "fd" means
: floppy disk.  And for that matter, what are asboot, bootas, wdboot, and 
: bootwd.

as represents adaptec 1542 scsi, wd represents winchester drive.
: 
: 	Question 3:
: 	Are there more then 1 disktype other then "floppy3"?  Where can
: I get a list of disktype?  Or How can I define or creat new disktype?

in file /etc/disktab

floppy5|5in|5.25in High Density Floppy:\
        :ty=floppy:se#512:nt#2:rm#300:ns#15:nc#80:\
        :pb#2400:ob#0:bb#4096:fb#512:
        :pc#2400:oc#0:bc#4096:fc#512:

Note that floppy5 has no pa entry, which means that partition a corresponding
to /dev/fd0a is missing. You can only use /dev/fd0b or /dev/fd0c

You can play with partition info here.
Create pd which must represent the entire drive. In fact pd is the default
partition for disklabel without any partition name.

: 	     
: Many many thanks
: Yeo...

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: mattb@sdd.hp.com (Matt Bonner)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Colorado Jumbo tape drive device driver.
Date: 6 Nov 1992 01:23:24 GMT
Organization: Hewlett-Packard, San Diego Division
Distribution: world
NNTP-Posting-Host: hpsdlg16.sdd.hp.com
Keywords: Colorado, No dice, Tape drive

In article <1992Nov5.153537.1@vax.sonoma.edu>, levinson@vax.sonoma.edu writes:
|> In article <raz.720786927@ultima>, raz@socs.uts.edu.au (The Inimitable Raz) writes:
|> > Has anyone developed, is anyone working on, has anyone worked on a 
|> > 386bsd driver for utilising Colorado Jumbo 250M, floppy controller
|> > attached, tape drives?
|> > 
|> > Does anyone have any info or code at all for driving these items?
|> > 
|> > raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 906 4681
|> 
|> 
|> It is amazing, that with all the Jumbo systems sold, only you and I are asking
|> about a driver for this tape drive!
|>  
|> If you happen to find one, let me know.  If I find one, I will let you know.
|>  
|> I am still waiting for Colorado Memory Systems to respond to a message I sent
|> to their Compuserv address.  It has been about 3 weeks.
|> 

This was discussed a few months ago, I believe the final answer was
that something in Colorado drive I/O was proprietary, and Colorado 
wouldn't share, so you can't write the driver for them.  I could be
wrong though, I didn't follow the thread too intently.

Regards,
Matt
-- 

Matt Bonner                  |  Email: mattb@sdd.hp.com
Hewlett-Packard Company      |  Snail: 16399 West Bernardo Drive
Ink-jet Components Division  |         San Diego, CA  92127-1899
Newsgroups: comp.unix.bsd
From: dinn@ug.cs.dal.ca (Michael 'Moose' Dinn)
Subject: Where do I get dist.fs for 3.5" drives?
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Date: Fri, 6 Nov 1992 14:23:12 GMT



Anyone know where I can get this beastie?

--
 Michael Dinn, CS Student  |  dinn@ug.cs.dal.ca, dinn@appliedmicro.ns.ca
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Colorado Jumbo tape drive device driver.
From: levinson@vax.sonoma.edu
Date: 10 Nov 92 15:37:49 -0800
Organization: Sonoma State University

In article <1992Nov6.053234.9052@fcom.cc.utah.edu>, terry@cs.weber.edu (A Wizard of Earth C) writes:
> In article <1dchecINN4pk@hpsdlss3.sdd.hp.com>, mattb@sdd.hp.com (Matt Bonner) writes:
> |> In article <1992Nov5.153537.1@vax.sonoma.edu>, levinson@vax.sonoma.edu writes:
> |> |> In article <raz.720786927@ultima>, raz@socs.uts.edu.au (The Inimitable Raz) writes:
> |> |> > Has anyone developed, is anyone working on, has anyone worked on a 
> |> |> > 386bsd driver for utilising Colorado Jumbo 250M, floppy controller
> |> |> > attached, tape drives?
> |> |> > 
> |> |> > Does anyone have any info or code at all for driving these items?
> |> |> > 
> |> |> > raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 906 4681
> |> |> 
> |> |> It is amazing, that with all the Jumbo systems sold, only you and I are
> |> |> asking about a driver for this tape drive!
> |> |>  
> |> |> If you happen to find one, let me know.  If I find one, I will let you
> |> |> know.
> |> |>  
> |> |> I am still waiting for Colorado Memory Systems to respond to a message
> |> |> I sent to their Compuserv address.  It has been about 3 weeks.
> |> 
> |> This was discussed a few months ago, I believe the final answer was
> |> that something in Colorado drive I/O was proprietary, and Colorado 
> |> wouldn't share, so you can't write the driver for them.  I could be
> |> wrong though, I didn't follow the thread too intently.
> 
> Nope.  There *is* a driver.  The person who wrote it hasn't released it yet
> and may not do so for some time.  Apparently they have read streaming but not
> write.  I publicly ate crow on whether or not it was possible without a change
> in the device priority mechanism about 2 months ago when I found out about
> it, so I definitely remember.
> 
> 
> 					Terry Lambert
> 					terry@icarus.weber.edu
> 					terry_lambert@novell.com
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> -- 
> -------------------------------------------------------------------------------
>                                         "I have an 8 user poetic license" - me
>  Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
> -------------------------------------------------------------------------------
-- 
Thanks.  I will wait patiently.  I will however offer a monetary contribution
to whomever releases such a puppy.
--
Eric Levinson
rcisnet2!root@moon.nbn.com	|  Home computer (UUCP)
levinson@vax.sonoma.edu		|  Vax
I can also be reached on my BBS system, Color Galaxy Milky Way (415) 883-0696
From: kim@dde.dk (Kim Andersen)
Newsgroups: comp.unix.bsd
Subject: [386BSD] GCC 2.3.1 and kernel
Keywords: 386BSD GCC kernel
Date: 11 Nov 92 14:14:08 GMT
Organization: Dansk Data Elektronik A/S

I finally got GCC 2.3.1 compiled (takes some time on a 4Mb machine).

Tried compiling the kernel.
Minor syntax errors found (pccons.c),
Error when linking: symbol ___main undefined in init_main.
    (I guess this symbol comes from libgcc2)
Removed this undefined symbol in assembler input file.

Then I tried booting with this kernel.

Result: Instant reboot.

So my questions are these:
    Have anyone succeeded in using Gcc-2.3.1 for compiling the kernel.

    What am I doing wrong ?

Thanks
kim
-- 
-- 
Kim Andersen @ Dansk Data Elektronik A/S, Herlev, Denmark.
E-mail: kim@dde.dk   or    ...!uunet!mcsun!dkuug!dde!kim
Newsgroups: comp.unix.bsd,comp.sys.dec
From: dgray@menudo.uh.edu (Dennis Gray Jr.)
Subject: VAX BSD tape
Reply-To: DGray@uh.edu
Organization: Academic Computer User Services
Distribution: comp
Date: Fri, 13 Nov 1992 06:30:12 GMT


I have a small Vax workstatio up and running (finally) and I would
like to get VAX BSD on it.  I have been told that I can get a bootable
tape right from Berkeley with BSD on it.

If you know where to send off for information on this, or more
details, please send mail to dgray@uh.edu, or followup to this post.

Thank you very much,
-dennis
From: stephens@ultrix.csc.usf.edu. (Daniel Stephens (CSC))
Newsgroups: comp.unix.bsd
Subject: Problems with SCSI adapter
Date: 4 Nov 92 23:28:48 GMT
Distribution: usa
Organization: Univ. of South Florida, Center for Scientific Computing


	I've posted here before in reference to this problem but, as I'm
new to posting on the net I'm don't believe the note made it out of my
domain.  Anyway,

	I'm having trouble (actually, it's been impossible so far)
getting 386bsd-0.1 to recognize my SCSI adapter.  I've got a Future
Domain adapter connected to either an 80 meg Quantum or a 120 meg Conner
at this point.  If anyone has suggestions, please do tell me and the
many others I've noticed with similar problems.  If there's a patch
somewhere that allows these adapters to be used, please direct me
there.  I believe the problem may lie in this adapters IRQ address which
is somewhat stuck at 5.  There was mention of a mandatory IRQ 11, but
I've yet to find an adapter that'll switch to that.  
`	Please help!   
	O, and tell me where I cand find Jerry's Patches as I keep
hearing about them on the net but can't locate any through anonymous
FTP.

	Thanks muchly,

Dan Stephens
Center for Scientific Computing
University of South Florida
stephens@ultrix.csc.usf.edu
Newsgroups: comp.unix.bsd
From: johnh@ficus.cs.ucla.edu (John Heidemann)
Subject: VFS interfaces [Was: Re: 386BSD or LINUX?]
Organization: UCLA, Computer Science Department
Date:  7 Nov 92 00:34:58 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:
>Linux supports the VFS interface (which is not a very good developement
>system; read:
>ftp.cs.ucla.edu:/pub/ficus/ucla_csd_910056.ps
>which is John Heidemann's master's thesis, available via anonymous FTP
>for details).

I would not want to suggest that the VFS interface is not "good"
(to mis-quote you slightly).  It's far better than what came before it.
I just happen to think there are some ways to make it better.

For those who are interested, the in-kernel portions of the stackable
file system interface discussed in the document referred to are
available in BSD 4.4.

>VFS does not equate automatically with a POSIX file system; UFS as it is
>distributes in 386BSD is *mostly* POSIX compliant.  All of the UFS features
>mentioned are, however, good points in 386BSD's favor.

With this I will heartily agree.  The interface has relatively little 
to do with the semantics of a particular file system.  Consider "/proc":
I doubt that it will respond to my POSIX-compliant "creat" call.

   -John Heidemann
    UCLA Ficus Project

Newsgroups: comp.unix.bsd
From: harry@atlas.socsci.umn.edu (Kuo-Chen Chang)
Subject: X server never up >>>  HELP
Organization: University of Minnesota
Date: Sat, 7 Nov 1992 21:06:23 GMT

It's been a very frustrated weekend.  I have been using linux for over 4 
months.  Last night I decided to give 386BSD a shot.  I cleaned up 2 partitions
on my Maxtor LXT340.  Everything seemed to be fine until I tried to install
XFree86.  As what I did within Linux, I tried "startx".  But this time
386BSD would not buy it.  I received several complaints:

userclientrc=/root/.xinitrc: Command not found
userserverrc=/root/.xserverr: Command not found
..
..

I tried to use "xinit".  THis time the window came for 1 second and deminished
with another error message:

XIO: fatal IO error 32 (Broken pipe) on X server "0:0"
     after o requests (0 known processed) with 0 events remaining.
     The connection was probably broken by a server shutdown or KillClient.

Any idea?

I also have some questions about 386BSD:
	1. Is there any screen saver available?  I don't want to burn my
	   SVGA monitor, though it's only 14".  On Linux, the screen black
	   out after 2-5 minutes idle.
	2. I do love the key buffer provided by Linux.  Where I can find
	   something with the same function?
	3. The mtools only allows me to access floppy drives.  I wish I
	   can access my data on DOS partitions.  Of course, then I can
	   exchange data between DOS, Linux and 386BSD.
	4. I wrote some programs dynamically allocate memory for huge
	   matrices, varying from 40x40x10 to 150x150x150.  I have no problem
	  within Linux.  But 386BSD won't let allocate memory larger than
	  3MB (maybe even even less.)  I ahve 20MB RAM on board and my Linux
	   kernel can handle up to 32MB.  What's the maximum amount of memory
	   386BSD can handle?

Thanks!

Harry
From: tpl20@pswd.amdahl.com (Thanh Luu)
Newsgroups: comp.unix.bsd
Subject: How to apply the binary GENERICA path for XFree86?
Date: 12 Nov 92 20:45:13 GMT
Organization: Amdahl Corporation, Sunnyvale CA

I got the 386bsd.kernel-1.0.3.tar.Z, unarchived it and got an executable
file, 386bsd.  I ran it and got an error message: 'Cannot allocate memory'.
My question is how do I correctly apply this binary patch?
Newsgroups: comp.unix.bsd
From: gregb@murphy.com (Greg Banschbach (Unigroup of New York))
Subject: 386BSD 0.2 ??
Organization: Murphy & Durieu, New York, NY
Date: Mon, 9 Nov 1992 14:59:29 GMT



	Dear fellow netters,

		I realize this is a little bit much to ask, but in the interest
	of saving some people the extra labor, I'll ask:

		With approximately 58 patches to 0.1,  isn't it time to 
	release a 0.2 with all of these installed ?    I am not being 
	sarcastic - but I was going to try to get the code from the Austin 
	Code works until I saw how many patches there were.   Now I am thinking
	of waiting.    

		Any advice ?  Anyone already planning to do this ??  I guess
	that if the patches don't take long to install,  I'll go for it.  



		Thanks for listening!


		Greg  (  gregb@murphy.com  ) 

	.....These are my own opinions, not anyone elses, but I'll gladly 
	rent them for a small fee.......
	
Newsgroups: comp.unix.bsd
From: tdphette@mke.ab.com (Thad Phetteplace x4461)
Subject: Xview props and Pcomm ported 
Organization: Allen-Bradley Co.
X-Newsreader: Tin 1.1 PL4
Date: Fri, 13 Nov 1992 16:34:47 GMT

I have created a /pub/386bsd/ports directory on my anonymous ftp server
tinman.mke.ab.com.  It currently has two ported programs in it.

1. The OpenWindows Properties program (props)
2. A port of the lates version of Pcomm

They are in the form of compressed tar files as well as unarchived
directories.  The excecutables are included for people who don't
want to recompile it themselves.

A warning: The hacks I made are rather ugly and infrequently documented.
No diffs are included though I intend to add them later.  Please email
me if you have any problems or comments.

--
Thad Phetteplace
Network Systems Analyst, Allen-Bradley Co.
Phone: (414)382-4461
Email: tdphette@mke.ab.com

The opinions expressed here are entirely my own and not that of my employer.
I am not a slob, I am simply doing an experiment in domestic entropy!

Newsgroups: comp.unix.bsd
From: richardl@iat.holonet.net (Richard Levenberg)
Subject: some info on EtherExpress
Organization: HoloNet (BBS: 510-704-1058)
Date: Sun, 8 Nov 1992 07:16:50 GMT

hi,

first let me say how impressed i was with the response that i got from my
last article post.  i got it working first try and sent the info on to
another user.

second, i thought that i saw some messages on EtherExpress but i dont seem
to find them.  i have an EE card in my machine but i dont think BSD
recognizes it.  how do i set it up to recognize it?

again in order 
richardl@orac.holonet.net
richardl@la.tis.com
1 800 767 8005 x 302
1 510 420 8777 x 302
From: giakas@chopin.udel.edu (Robert M Giakas)
Newsgroups: comp.unix.bsd
Subject: Help with printing....
Date: 12 Nov 92 22:09:01 GMT
Distribution: na
Organization: University of Delaware



I've gotten 386BSD set up (only installed bin01, though).  I have a 
laserjet connected to my parallel port on a DELL 325.  I haven't been
able to use the lpr command to print.  It basically tells me that
there is no such device /dev/lp.  To make a long story short, how do
I go about setting up for a printer?  

Thanks all!

-- 
-------------------------------------------------
Rob Giakas
University of Delaware
From: hurtubis@a.chem.upenn.edu (Vincent Hurtubise)
Newsgroups: comp.unix.bsd
Subject: Re: BSD on SUN-3?
Date: 12 Nov 92 17:35:47 GMT
Followup-To: comp.unix.bsd
Organization: University of Pennsylvania

In article <1992Nov12.104709.11414@csqx.cs.rhbnc.ac.uk> markd@csqx.cs.rhbnc.ac.uk (Mark Damerell) writes:
>
>
>Please does anybody know if there are any plans afoot to adapt
>the BSD system to either SUN-3 or HP-9000/800 series machines?
rest of post deleted

Please post or e-mail your responses to me also.  I'm interested in BSD
for Sun3's.
   Thanks 
---
   Vincent Hurtubise
      hurtubis@a.chem.upenn.edu
      hurtubis@sun0.chem.upenn.edu
From: karl@NeoSoft.com (Karl Lehenbauer)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Problems with a SMC Elite16 (WD8013EPC)
Date: 6 Nov 92 15:11:38 GMT
Article-I.D.: NeoSoft.BxAvJG.ByF
Organization: NeoSoft Communications Services -- (713) 684-5900

We have a WD "Elite" 8-bit ethernet board that won't retain its
settings (as set up by "ezsetup") after power off.

That's not supposed to happen, and believe me, it was a bitch to figure
out.

We sent it back and got another one that didn't have the problem.  Your
alternative is to use one of the two hard-wired setups that are strappable
on the card.
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
"It took no computation to dance to the rock 'n roll station."
-- VU
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.unix.bsd
Subject: ftp inc has bsd on cd-rom 
Distribution: world
Date: Fri, 06 Nov 92 02:23:23 GMT
Organization: Crynwr Software

In article <83uRTB2w165w@student.business.uwo.ca> mark@student.business.uwo.ca writes:

   all of the RFC files.
   Complete MIT X11 tree
   MS-DOS directory containg NCSA, clarkson packet drivers, analyzer,

Crynwr packet drivers.  Crynwr.  It says so on the disk label.
Crynwr, not Clarkson.

[ The preceding message was brought to you by Clarkson's legal department. ]

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.