HDTenEightyP/NetNews huggingface dataset:
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: Sorry, everyone, but I'm cpio clueless...
Date: 20 Jul 92 08:30:56 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <14c75pINNh59@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:



>With regards to the 0.1 install program, yes, it only creates one big
>partition for the whole set of files, with a 5MB "b" partition and a "c"
>partition that spans the entire FDISK partition. Sorry no options yet.

>As the INSTALL.NOTE's mention, to install it the prior, manual way by
>writing a disktab entry is *not documented*, although possible with the
>new FIXIT floppy. Crossing between the two mechanisms is also possible
>but not reccomended unless you really know what you are doing (also, since
>totally untested by us, may provoke bugs we are totally unaware of).

>The install program is still under development (this is a surprise?), being
>a recent addition, and one on which we'd like to hear some well considered
>discussion, because of the choices possible. It's hard for a system this
>complex to be installed by a naive user (we have approx 80,000 of these),
>yet it should not be too much of a straight jacket for experienced ones.
>Lynne chose MSDOS's model to begin with, but it's just a start. You'd be
>surprised just how hard she worked just to get that straight.

>Bill.

One notice for all installers:

There is a catch with install. You may run into problems 
with NEWFS (called from INSTALL) when the free space on your partition
is at the beginning of the disk.
newfs reports 
(WDINFO: no such process)
and fails install.


INSTALL may complain about 0 MB free, but this is not true. In this case
you have to set up a partition with id 165 (0A5h) by yourself. This is
accomplished by making an appropriate DOS-Partition with FDISK and then
patching the DOS partition sector (with norton utilities or debug, BE VERY VERY
CAREFUL!!!!!) to contain the proper ID). THIS PARTITION MUSTN'T START AT
CYLINDER 0. The first useful location is cylinder 1, because all FDISKs have
the feature to start the partition at cylinder 0 track 1, not track 0. This
is reasonable, because track 0 starts with the DOS partition sector. But
newfs wants to write its disklabel and does not like starting a partition
at a non-cylinder boundary.

Hope this information is useful.

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: jnpotts@iastate.edu (James N. Potts)
Subject: Help for two error messages [386bsd]...
Organization: Iowa State University, Ames IA
Date: Sun, 26 Jul 1992 22:09:04 GMT

First, when I boot my system, I get the message
  "<whatever the current date is> lpd[50]:/dev/lp: No such file or directory"
when things are initializing.  This just started happening recently, and I'm
wondering what I did to start it, and how I can stop it.

Now for the second question:
When I try to use tip, I get the following:
  % tip com1
  lock open: No such file or directory
  all ports busy

Can anyone help to rectify these situations?


-- 
_____________________________________________________________________
James N. Potts          |  "To err is human.  To get multiple UAE's 
jnpotts@iastate.edu     |   requires MS Windows."
tabp6@isuvax.iastate.edu|                      - Me
Newsgroups: comp.unix.bsd
From: ronald@gate.demon.co.uk (Ronald Khoo)
Organization: Demon Internet Services.
X-Mailer: Mail User's Shell (7.2.4 2/2/92)
Subject: Article numbers (WAS Re: 386bsd 0.1 - Advice on bootstrap debugging needed.)
Cc: Terry Lambert <terry@thisbe.npd.novell.com>
Date: Sun, 26 Jul 1992 20:32:03 +0000

terry@thisbe.npd.Novell.COM (Terry Lambert) wrote:

> Chris Demetriou (cgd@agate.berkeley.edu) has patches
> available for download at agate.berkeley.edu.  Check out article #1912
								^^^^^^^^^
> or simply download the patched boot image for dist.fs and fixit.fs,

Sigh.  I've seen several articles in comp.unix.bsd tonight that refer
to articles by number, and so I just *had* to reply to one.
(sorry Terry, not picking on you specifically!)

Please folks, articles numbers are LOCAL TO YOUR OWN MACHINE!  They will
be DIFFERENT on every one else's machines!  So, quoting article numbers
will be at best useless and at worse confusing to everyone else.  If
you have to refer to an article, please use the Message-ID in the header
of the article that you are referring to, (e.g. Terry's article was
	<1992Jul23.213947.22807@gateway.novell.com>
) and your news sysadm should be able to help you work back from that to
the article number as it is on your own machine.


-- 
Ronald Khoo <ronald@demon.co.uk> <ronald@ibmpcug.co.uk> <ronald@robobar.co.uk>
BTNet: +44 71 229 7741                    | Brambles are the order of the day.
Newsgroups: comp.unix.bsd
From: jim@ferkel.ucsb.edu (Jim Lick)
Subject: Re: USL vs. BSDI, and what to do
Organization: University of California, Santa Barbara
Date: Fri, 24 Jul 1992 21:14:56 GMT

In <Brwq6v.1A7@acsu.buffalo.edu> ferrick@acsu.buffalo.edu (Patrick K. Ferrick) writes:
>I know this whole AT&T thing is really important to everyone in the long run,
>but isn't there a more appropriate forum for this discussion?  I look forward
>to reading this group to learn about BSD, and in particular 386bsd.  I'm sure
>many other people would also appreciate less back-and-forth on how we're going
>to retaliate, etc.  Thanks.

So what do you suggest?  alt.usl.vs.bsdi.sue.sue.sue?

I can't think of a group more appropriate than the one we're using.

                            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@case.isla-vista.ca.us
      jim@ferkel.ucsb.edu	|       jim@cave.isla-vista.ca.us
From: chris@lslsun4.epfl.ch (Christian Iseli)
Newsgroups: comp.unix.bsd
Subject: 386BSD-0.1 ftp almost works... but?
Date: 29 Jul 92 09:08:59 GMT
Organization: Ecole Polytechnique Federale de Lausanne

Hi folks,

I'm trying to install 386BSD-0.1 on a random piece of 386 hardware.
I have one of those WD8003E ethercard plus plugged into it. After
fiddling with the jumpers a bit, I finally got the card to send
packets on the wire.

First strange thing is that the card is supposed to be on level 2 IRQ,
but 386BSD insists on finding it on level 9...

The official release gives the 65535 error thing when I try to
ifconfig the card, so I tried both unofficial releases (dist.fs-noIS
on most sites and dist.fs-WD800 on src.doc.ic.ac.uk). In both cases,
ftp works fine to connect to a local host and list some directories
using the cd and dir commands.

However, when I try the get command, the file seems to be
transfered, the line "226 Binary Transfer complete." appears on
the screen and then everything freezes. Cntrl-C doesn't help either.

Anybody knows a trick to help me in this case? Darn, I'm almost there...

Cheers!
-- 

					Christian Iseli
					LSL-DI-EPFL
					Lausanne, Switzerland
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
From: jpk@Ingres.COM (Jon Krueger)
Subject: Re: New group alt.suit.att-bsdi
Reply-To: jpk@Ingres.COM (Jon Krueger)
Organization: Ingres Division, ASK Computer Systems.
Date: 29 Jul 92 01:17:39 GMT

dennis box writes:
> SUGGESTED ADVERTISING SLOGANS FOR AT&T:

But they already have the perfect one:

	"AT&T -- think of the big picture"

From their current "we want you back" campaign.

Good point, I thought.  So I changed my phone service to MCI.
I don't expect to save any money or get better quality lines.
But I'm thinking of the big picture.

-- Jon

Jon Krueger  jpk@ingres.com  
Newsgroups: comp.unix.bsd
From: jbh@aii.com
Subject: Re: patched bootables on agate...
Keywords: BOOT PROBLEMS wd0
Organization: Automation Intelligence
Date: Thu, 23 Jul 1992 11:23:18 GMT

In article <1992Jul22.191215.29393@linus.mitre.org> wheeler@jeckle.mitre.org (Brien L. Wheeler) writes:
>In article <explorer.711733580@tbird.cc.iastate.edu>, explorer@iastate.edu (Michael Graff) writes:
>> 
>> I tried these disks, but I still can't install BSD 0.1 on my Zenith 
>> Z-386/25.
>> 
>> Install info:
>> 	install using the patched and non-patched dist.fs disks.  When
>> 	installing, it seems to write to the hard drive fine.  If I
>> 	hit ^C when it wants to reboot, I can mount the filesystem and
>> 	everything seems to work.  However, it locks during reboot.
>> 	The keyboard lights flash, and the floppy light stays on.  It
>> 	requires a power cycle to make it come back to life.
>
>I too have had problems loading 386BSD onto the drive in my Zenith Z-386
>PC.  Unfortunately, I don't know enough about the PC architecture to
>adequately describe my system, but it includes a WD8013 Elite at IRQ 2,
>5 MB RAM, a Paradise VGA card, a 387 FPU, and an 80 MB HD (don't know what
>kind).  I have the same problems as Michael Graff -- It just won't boot
>off the hard disk, even though it appears to be installed correctly.
>
>     Brien
>     
  I had this same problem, did lots of chasing and found the 2nd stage boot
code had a BIG broken in it ! It would work with a real W.D. chipset
controller, but NOT some of the clones. Turns out to be a real NO NO in the
code, using registers explicitly stated as WRITE ONLY, and explicitly stated
as 4 bits big, as a READ for status (trying to read the TOP 4 bits, which
are stated to BE RESERVED and UNDEFINED !!!!).
  To make the long story short, we posted a fix to the net, see article 2608.
This includes diffs and a uuencoded bootwd needed to correct the problem.

Regards,
Jim
======================================================================
Jim Huber   jbh@aii.com or ...!tarpit!jbh Voice (407) 661-7017
Automation Intelligence,Inc.
850 Trafalgar Court
Suite 200
Maitland, FL 32751
======================================================================


Newsgroups: comp.unix.bsd
From: mjm@monu6.cc.monash.edu.au (Mike McBain)
Subject: extract problem
Keywords: bin01.install
Organization: Monash University, Melb., Australia.
Date: Thu, 30 Jul 1992 04:36:44 GMT

I have noted the problem of the missing brackets with the bin01.install 
script. This is a related problem, but moved one step earlier. First, let 
me describe what I *think* happens.

install places the executable extract in /tmp
loadfd can be used to copy the bin01 distribution fragments from DOS floppies
  (question: where is this useful program to be found? it seems to disappear
   when the system goes multi-user)
when extract is run, the extraction never completes. It just runs for ever.

I have tried extracting using cpio, but then /dev/kmem doesn't get made
and a whole bunch of other things don't get done. If the problem is a missing
[ or ] in the shell script, how do I get at the script, which only seems to
appear in /tmp/tmp after extract has been run?

Is there something particularly slow about the cpio on the boot disk? It takes
over two hours to extract the bin01 distribution when I use uncompress and
cpio.

-- 
---
Mike McBain                                 David Syme Faculty of Business
mjm@monu6.cc.monash.edu.au                  Monash University - Caulfield
+61 3 573 2646                              Australia
Newsgroups: comp.unix.bsd
From: scs@iti.org (Steve Simmons)
Subject: Re: USL vs. BSDI, and what to do
Organization: Industrial Technology Institute
Date: Fri, 24 Jul 1992 19:01:51 GMT

tal@Warren.MENTORG.COM (Tom Limoncelli) writes:

>I hate to say this, but [AT&T] has nothing to do with this.  AT&T didn't
>bring the law suit.  USL did.  USL has a different chair person, and
>has their own lawyers (from what I've heard, they don't share lawyers...
>so much for the "army of lawyers").

But AT&T is the majority owner of USL.  You can bet any extremity you
care to name that if AT&T is hurt by the actions of USL, something will
get done about it.
-- 
"I was disqualified when I mooed at a propane tank mistaking it for a cow."
    Patrick E Fleming, pfleming@magnus.acs.ohio-state.edu
Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: Adaptec SCSI bug?
Organization: Novell NPD -- Sandy, UT
Date: Fri, 31 Jul 1992 00:22:59 GMT

In article <1992Jul30.210037.9265@ninja.zso.dec.com> mbs@fungus.zso.dec.com (Michael Schmitz) writes:
>In trying to figure out why my 386BSD 0.1 sometimes hangs during
>heavy disk I/O, I noticed the following in the adaptec driver:


	I noticed this as well with a WD1007 EDSI controller, only much more
frequently (like the disk locked up during install).  I think this has to
be either a more general problem in UFS, or in the paging code, which is how
UFS does it's disk writes.  If anyone has a soloution, I am sure you would
have both Michael and my thanks.

	I will try to repeat this on the floppy alone, by copying to /dev/null,
but this will only locate it if it's in the read code, since devices use
the spec_vfsops, and the pager won't be used for real data transfers *to*
/dev/null, only for reads from the disk.  If it's a read latency problem,
it still won't be identified, because floopies are slower.  More on this
tomorrow.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: kris@tpki.toppoint.de (Kristian Koehntopp)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
X-Copyright: (C) Copyright 1992 Kristian Koehntopp -- All rights reserved.
		 Reproduktion, auch auszugsweise, ausserhalb elektronischer,
		 nichtkommerzieller Datennetze nur mit ausdruecklichem,
		 schriftlichem Einverstaendnis des Autors.
Organization: Toppoint Mailbox e.V.
Date: Fri, 31 Jul 1992 14:27:16 GMT
X-Excuse: X-Copyright wegen Emma, Suedwestpresse und /C'T/DISKUSSIONEN.

In <1992Jul28.213156.15525@flatlin.ka.sub.org> bad@flatlin.ka.sub.org (Christoph Badura) writes:
>-- 
>				Christoph Badura  ---  bad@flatlin.ka.sub.org

>UNIX is a trademark of LEBEDA & Co, Ges.m.b.H, Vienna, Austria

On the grounds of this copyright discussion: Can you tell us
about your .signature?

Kristian
-- 
Kristian Koehntopp, Harmsstrasse 98, FRG W-2300 Kiel, +49 431 676689
"AT&T --- anything better is illegal."
	-- Keith Lofstrom, comp.unix.bsd, "AT&T sues BSDI" thread
From: jtsilla@damon.ccs.northeastern.edu (James Tsillas)
Newsgroups: comp.unix.bsd
Subject: 386BSD - Installation Problem
Date: 27 Jul 92 04:24:30 GMT
Distribution: comp
Organization: Northeastern University, Boston, MA


System:
	386SX-16 C&T Chipset (onboard IDE disabled) and Phoenix Bios
	1.10
	4 Meg memory
	DTC RLL controller with two Mitsubishi 65 Meg RLL drives
	WD8003E

Problem:

	Boots the Tiny386BSD without any problems. Since I wish to
	use the entire disk(s) for 386BSD I run install and select
	the "use all" feature. It appears to install everything on a
	newly created partition. Unfortunately it fails to boot from
	disk, freezing early in the boot code (floppy light stays on).
	The machine used to run ISC 2.2. Do I need to do something
	special to the boot sector?

thanks for any help,
-Jim.

PS. Any CFD's for a comp.os.386bsd? CFV?
--
***                                                      ***
***  James Tsillas  jtsilla@damon.ccs.northeastern.edu   ***
*** ..see you at Korova Milk Bar brothers and sisters..  ***
***                                                      ***
From: larose@thud.cs.utk.edu (Brian LaRose)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI (!!!!BOYCOTT AT&T!!!!!)
Followup-To: larose@cs.utk.edu
Date: 22 Jul 92 18:00:37 GMT
Organization: University of Tennessee, Knoxville - Department of Computer Science
Distribution: world
Reply-To: larose@thud.cs.utk.edu (Brian LaRose)
NNTP-Posting-Host: thud.cs.utk.edu
Keywords: AT&T

!!!!BOYCOTT AT&T!!!!!

I just called AT&T and I'm switching to MCI.  This lawsuit is a bunch of
horseshit.  I'm quite sure AT&T doesn't care about the Public Unix community,
so I'll just not care as I DON'T DO BUSINESS WITH THEM ANYMORE!!

Get 'em where it hurts 'em most, their pockets.  Besides I've always liked
Murphy Brown (uhhh.  I mean Candice Bergman)  she is sort of the 
anti-quayle-e.  Yea, that's it....  

Switch to MCI.   NO MORE QUAYLE.
                 NO MORE AT&T.

!!!!BOYCOTT AT&T!!!!!
-- 
    -------------------------------------
    | Brian LaRose |  974-3647          |
    | Ayres 217    |  larose@cs.utk.edu |
    -------------------------------------
    
Newsgroups: comp.unix.bsd
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
Subject: Re: AT&T sues BSDI
Organization: Mentor Graphics, Silicon Design Division
Date: Fri, 24 Jul 1992 17:18:28 GMT

[ I can't resist one more post ]

In <14ojorINNlm5@disaster.Germany.EU.net> bs@Germany.EU.net (Bernard Steiner) writes:

>Does that mean that anyone having seen a Ford and then goes off designing
>hir own car will be sued by Ford for the reason of having been exposed
>to Ford cars ?

There is a difference between reading the source, and using the
program.

HAS ANYONE COMPARED THE CODE THEMSELVES?  Could someone with a source
license FTP the damn NET2 release, pass them through "indent" and then
compare them?

Tom
-- 
Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.uucp (play)
      Maybe Bush will follow Perot's lead.
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: Beginner's problems with 386BSD
Date: Mon, 27 Jul 1992 12:37:33 GMT
Organization: Chinet - Public Access UNIX

In article <1992Jul27.011712.27704@coe.montana.edu> osynw@warp.mhd.montana.edu (Nate Williams) writes:
>>>I wish someone could tell me how to get my clock correct too.  I have tried
>Yep, I have tried everything I could think of.  I removed /usr/share/zoneinfo
>and remade everything from scratch.  My machine is still one hour faster
>than my real time clock.  

	I gave up, too.  So, I just changed the CMOS time so 386bsd
	came out right. Worked great.

-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us
From: peter@micromuse.co.uk (Peter Galbavy)
Newsgroups: comp.unix.bsd
Subject: Floating Exception while trying install... no 387, help !
Date: 22 Jul 92 17:30:35 GMT
Organization: MicroMuse Limited, London, England.

Hi netters,

This is a very quick post, since I have to go out and drink alot (it my
birthday - send presents please :-).

0.1 boots fine on a 486/25 - excellent package it is too, but trying it
on a real bare 386/33 with aha1542, vga and serial board gives an attempted
core dump and floating exception when running install. I thought the 0.1
version did emulation.

BTW - I guess that npx0 is the floating point chip ??? I get that in the
486 startup, but not the 386.

Thanks all, must go now,
-- 
Peter Galbavy
Tech Support, Micromuse Ltd
Phone: +44 71 352 7774		E-Mail: P.Galbavy@micromuse.co.uk
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: Adding users
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Fri, 24 Jul 1992 21:51:39 GMT

In article AA06522@nms1.abb.com, MLUCI@fuel.abb.com (Mark Lucia 2915) writes:
>       I tried the following:
>       	1. looking for a 'adduser' etc program/script
>       
>       	2. makeing an entry in the /etc/passwd file
>       	   makeing am entry in the /etc/master.passwd file
>           adding the home directory in /usr
>       
>       	3. rebooting the machine after 2

The correct procedure is:

	1 - Run the vipw(8) command.  This will allow you to edit the password
            file and will automatically rebuild the master.passwd file when
            you exit.  It may also do some other magic (I haven't looked at
            it too closely yet).  

	2 - (Optional) If you want the new user to be able to use the su 
            command add his user name to the wheel group in /etc/group.

        3 - Create a home directory for the new user.  This should match
            the one given in /etc/passwd.  It appears to be conventional
            to use /usr/<username> in 386BSD.  Change its ownership to
	    and group using chown(8) and chgrp(8).  Unless you specified
            otherwise in /etc/passwd the new user's group will be staff
	    (gid = 20).


	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: dealwisb@cognos.com (Brian de Alwis)
Subject: Re: Do YOU think that this generates correct kernel ?
Keywords: kernel config
Organization: Cognos Incorporated, Ottawa CANADA
Date: Wed, 29 Jul 1992 17:38:25 GMT

In article <1992Jul29.091608.10321@lut.fi> ats@lut.fi (Ari Suutari) writes:
>dealwisb@cognos.com (Brian de Alwis) writes:
>>controller wd0 at isa?
>>disk       dk0 at wd0 drive 0
>>disk       dk1 at wd0 drive 1
>
>	I think that config works correctly, it just that naming of
>	devices should be different. How about doing it like this:
>
	[example using a different controller name deleted]
>
>	This would, of cource, require some changes. wd.c should be wdc.c
>	and files.i386 should be modified also. All references to NWD
>	should also be checked and modified to NWDC if required.

But config should be able to determine the number of attached devices
by the referenced controller - there are two disks (from the above)
attached at wd0 - hence NWD should be two, not one (as config would
do). And, using only one disk entry (commenting out the other), why
would config generate a swap-struct referencing makedev(1,1), instead
of makedev(0,1)?

+++BdA
-- 
+++BdA  Brian de Alwis. Brain on loan to Cognos Inc, Ottawa, Ontario.
	dealwisb@cognos.com, or bsdealwi@napier.{waterloo.edu,uwaterloo.ca}
	"Nine out of ten men who tried camels said they preferred women"
From: ralph@falcon.SLAC.Stanford.EDU (Ralph Becker-Szendy)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 23 Jul 92 22:50:26 GMT
Organization: Stanford Linear Accelerator Center

In article <1992Jul23.204845.28978@ddsw1.mcs.com> karl@ddsw1.mcs.com (Karl 
Denninger) writes (abbreviated):
>I think we should organize a boycott of AT&T products and services, and 
>tell 'em why.  This means that MCI gets my long-distance service.

I (as a private individual) am already boycotting AT&T (due to XWindow
backing store). My long-distance carrier is MCI. The phone at home is
made by Panasonic. I have no plans to purchase phone equipment. I
could try to steer purchases at work away from AT&T, but that would be
a horrible crime of tampering with Federal Government Purchasing.
Note: our group does purchase about $3K of phone service from AT&T per
month, and we are about to add a satellite international link which
will cost close to $10K/month, also from AT&T; in both cases there is
no competition to AT&T, so there are no other options. I could start
boycotting all Un*x systems (since they all eventually go back to an
AT&T license), but that would be a very unreasonable hardship (I would
get no work done any longer).

So the question is: What can I do (as a private individual) to help
BSDI, and intellectual freedom? Looks pretty bleak, doesn't it. The
only option is to directly donate money to BSDI, or (equivalent) buy a
copy of BSDI's Unix which I don't need right now.

This is not a rhetorical question (if there is something one can do to
help, I'd like to know), although it really looks like there is
nothing one can do. Short of tossing Molotov-cocktails into the
nearest AT&T facility (which again is not suggested and a crime, for
good reason).

-- 
Ralph Becker-Szendy                          RALPH@SLACVM.SLAC.STANFORD.EDU
Stanford Linear Accelerator Center                      RALPH@SLACVM.BITNET
M.S. 95, P.O. Box 4349, Stanford, CA 94309                    (415)926-2701
My opinion. This is not SLAC, Stanford U, or the US DoE speaking. Just me.
Newsgroups: comp.unix.bsd