HDTenEightyP/NetNews huggingface dataset:
From: revell@ghidra.UU.NET (James R Revell Jr)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 release
Date: 29 Jul 1992 23:51:12 -0400
Organization: UUNET Technologies Inc, Falls Church, VA
Reply-To: revell@uunet.uu.net (James R Revell Jr)
NNTP-Posting-Host: ghidra.uu.net

In article <14c63bINNh22@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
} Do *not* obtain 386BSD from uunet! BSDI is funded partially from UUNET
} coffers, and those idiots still see 386BSD as a rival to their hopes.
} 
} As with other related situations, they have come up with "plausibly deniable"
} reasons to not provide information that they feel affects their competitive
} advantages.

Well, despite what Bill may say or think, this is not true.

I said before that UUNET would drop our no-binaries policy when I got
the new disks up on the archive, and since I've just finished moving
the archive from uunet.uu.net to the new 9 GB on ftp.uu.net, that
policy is now history.

I have included the rest of the 386BSD distribution in our mirror
-- 
James Revell	Network Services Mgr   <revell@uunet.uu.net>   /8^{~
Newsgroups: comp.unix.bsd
From: kcwellsc@watdragon.uwaterloo.ca (Ken Wellsch)
Subject: Re: 2 Problems: No disk Label, Tip doesn't Work
Organization: University of Waterloo
Date: Tue, 28 Jul 1992 16:02:12 GMT

>	The second problem I had was getting tip to work, and I saw a
> couple of posts about this, but no solution.  When tip is configured
> properly, we get the
>	no file or no lock error.  (sorry, I can't be more precise, but
> I can't get that far again without reinstalling 386BSD on my whole
> system, and then I can't get tip to work to read mail and news for the
> solution :-)

I think you will find that "tip" is setuid "uucp."  Now it wants to create
a lock file under /var/spool/lock I believe.  You'll probably find that
/var/spool/lock is owned by root and mode 0755.  Thus "uucp" is unable to
write/create a lock.  I'm not sure whether "uucp" should own the directory
or if it should be world writeable with the sticky-bit on like /tmp.
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Keywords: BSDI AT&T
Date: 26 Jul 92 13:48:43 GMT
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <l73plcINN10d@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>Frankly, I think the US Congress should be investigating AT&T's attack
>on BSDI because I believe it is an attempt to garner exclusive monopoly 
>control over an important national resource (4.3BSD-NET2 distribution) 
>against the public interest.  

Bravo! Is this the sort of thing that would make election politics in
your country? I could imagine that big corporations are not overly
popular at the moment.

-- 
Greg Lehey                       | Tel: +49-6637-1488              
LEMIS                            | Fax: +49-6637-1489
Schellnhausen 2, W-6324 Feldatal, Germany
*** NOTE ***: Headers are mangled - reply to grog%lemis@Germany.EU.net
Newsgroups: comp.unix.bsd
From: ats@lut.fi (Ari Suutari)
Subject: Do YOU think that this generates correct kernel ?
Date: Tue, 28 Jul 92 15:15:18 GMT
Organization: Lappeenranta University of Technology, Finland
Keywords: kernel config


	Hello again ....

	My 386bsd works fine, but I run into possible problem when I compiled
	new kernels for my machine. I specify disks (lines have been
	taken from GENERICISA configuration file) as follows:

	controller	wd0	at isa? ....
	disk		wd0	at wd0 drive 0
	disk		wd1	at wd0 drive 1

	controller	fd0	at isa?
	disk		fd0	at fd0 drive 0
	disk		fd1	at fd0 drive 1

	This file produces a working kernel. But if I look at the
	wd.h (for example) file at /sys/compile/MY_HOST there is a 
	line which states:

	#define	NWD	3

	I think that this is becouse the config utility ses three lines
	containing "wd". This is incorrect, since I have only 2 disks
	configured. Same problem, of course, exists for "fd" too.

	In release 0.0, I think that I had something like this in
	my configuration file:

	controller	wd0	at	isa?
	disk		dk0	at	wd0 drive 0
	disk		dk1	at	wd0 drive 1

	This doesn't work for release 0.1. When I boot, I got messages
	for swap device not being configured (even if I say "config ...
	swap on dk0").

	I think that the controller name (wd) and disk names (dk in 0.0,
	now wd) should be different and that the later example here
	is more correct (if I look at Ultrix machines at work, they
	name the controller as "sii" and disks "rz").

	This is not a serious problem but it has been puzzling me for
	some time, since I cannot figure out what would be the
	correct way for 386BSD to this (a small problem, no big ones ...
	that means 386BSD is an excellent OS ...)

	I'd like to hear about any suggestions/opinions to this.


	
		Ari

--
	Ari Suutari		ats@lut.fi, ari@hilti.lpr.carel.fi
	Lappeenranta
	Finland
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: I wonder, did AT&T backstab BSDI?
Organization: Kithrup Enterprises, Ltd.
Date: Wed, 29 Jul 1992 20:19:19 GMT
Keywords: AT&T speculation lawsuit BSDI

In article <1992Jul29.174437.18606@gateway.novell.com> terry@thisbe.npd.Novell.COM (Terry Lambert) writes:
>Things AT&T owes to Berkeley:
>2)	VFS
>3)	Memory management strategies

That's funny, I could have sworn that these actually came from SunOS.
Considering that 4.4ish is the first BSD system to have vnodes, and a decent
memory-management scheme, I don't see how SysVr4 (which has been out for a
couple of years now) could have gotten it from 4.4...

>4)	Job control

Other systems had job control long before BSD did.

>5)	csh

I use bash or ksh.  csh has too many problems.

>8)	mail/sendmail/smtp

Other systems had smtp before, no?  sendmail isn't that great, and there are
other systems that deliver mail without the horrible configuration problem
that sendmail is.  And UNIX had mail *long* before UCB ever started playing
with unix!

-- 
Sean Eric Fagan  | "My psychiatrist says I have a messiah
sef@kithrup.COM  |  complex.  But I forgive him."
-----------------+              -- Jim Carrey
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.bsd
From: bambi@bu.oz.au (David J. Hughes)
Subject: Re: Availability of 386BSD_0.1 in Australia
Organization: ITS, Bond University
Date: Thu, 23 Jul 1992 05:24:54 GMT

BSC_PAT@vd.seqeb.gov.au writes:

>Does anyone know where 386BSD_0.1 is available in Australia or the Pacific
>region.


The Australian mirror site for 386BSD is at Bond University and is
accessible as :-

	Hostname	: kirk.bu.oz.au
	IP Address	: 131.244.1.1
	Path		: /pub/OS/386BSD




   ___                                 David J. Hughes     bambi@bu.oz.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __          Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /    Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /       AUSTRALIA  (+61 75 951450)
From: terry@npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: Berkeley Strikes Back?
Date: 30 Jul 92 19:30:17 GMT
Organization: Novell NPD -- Sandy, UT

In article <MIKE.92Jul30085914@majestix.cs.uoregon.edu> mike@majestix.cs.uoregon.edu (Michael John Haertel) writes:
>In article <158frnINN5cn@agate.berkeley.edu> gwh@soda.berkeley.edu (George William Herbert) writes:
>> stone.  Berkeley could conceivably pull the right for USL to
>> resell anything with "Copyright the Regents..." in it,
>> or derived therefrom.
>
>Actually, Berkeley probably can't do this.  I have no idea how
>Berkeley's license agreement with AT&T reads, but at my old school
>one of the conditions on the educational Unix license was that
>AT&T would have access to any modifications made to the software.
>(Or something like that; it's been about 5 years since I read
>that license.)

	What is "access"?  The ability to go "hmmmmm...." or the ability to
incorporate any changes into future AT&T products?  Please, please, if you
can, post the terms of the license.  A superior posting, unless Mike's old
school was UCB, would be for someone at UCB to post the license terms they
were granted by AT&T.

					-- Terry
Newsgroups: comp.unix.bsd
From: smart@wanda.mel.dit.CSIRO.AU (Robert Smart)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Organization: CSIRO, Division of Information Technology, Melbourne
Date: Tue, 21 Jul 92 10:46:27 GMT

Many years ago I heard a talk by an AT&T employee, Denis Ritchie, in
which he said that the objective in distributing unix free to universities
was so that people could learn about the operating system ideas contained
therein and apply them to commercial operating systems (which unix then 
wasn't). It does not seem fair to then claim that everybody who has seen
those ideas is contaminated and can't apply them. It is ridiculous to
claim that by licensing source free to every place where future inventors
are likely to be you have acquired protection of that source which is
better than a patent! It doesn't even have a time limit or have to
conform to the patent offices strict (if often misapplied) standards.
This is insanity. Surely this will be thrown out of court.

Bob Smart
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: ksh
Date: 22 Jul 92 05:15:33 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Jul19.164817.6465@chinet.chi.il.us>,
randy@chinet.chi.il.us (Randy Suess) writes:
>
>	Well, I may not be able to get a second disk to work on 0.1,
>	but at least ksh compiles and runs cleanly.  With ksh, I am
>	in heaven.

Is that a PD version of KSH? If it is, where did you get it and how good is it?
-- 
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.
Newsgroups: comp.unix.bsd
From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: Re: using mtools to access dos partitions
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Sat, 25 Jul 1992 17:57:11 GMT

In <2eLv02wc1bJx01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:


>In article <1373@sousa.ltn.dec.com> you write:
>>mitchemt@silver.ucs.indiana.edu (Terrence Mitchem) writes:
>>: 
>>: 	Can anyone tell me how to set up the devices.c file that comes with
>>: mtools in order to access dos partitions on  hard drive? Which
>devices in /dev
>>: correspond to the partitions on the disk?  Does it make any
>difference if Im
>>: using a scsi controller (adaptec 1542b)?  All help is appreciated.

[stuff deleted]

>Can't you just create a new device to access the DOS partitions without
>recompiling the kernel?  The /etc/disktab file probably does not match 
>your actual disk label but this can be gotten using the 'disklabel'
>program.

Yes you can. I yesterday succdeded with the configuration of mtools to
read the MSDOS partition on my IDE disk.
  You can edit the disklabel with the -e option. Add a new partition
entry at the end of the editor wich covers the MS-DOS partition and
don't forget to increase the number of partitions right before the
list of partitions.  

> It looks like the locations of the partitions are specified in 
>sectors from the *beginning of the hard disk*, not the beginning of the
>386BSD partition.  

This definitely is true

>You should be able to update the /etc/disktab 
>from the output of 'disklabel', add the new entry describing the DOS 
>partition location (multiply it out from the cylinder info supplied from 
>MS-DOG's 'fdisk' program), rebuild the disk label using 'disklabel', and
>create another device, say /dev/as0g, using 'mknod' (the meaning of the 
>minor device number is at the beginning of the file 'as.c').

I did this for an IDE drive but this method is likely to work with
SCSI as well.

>This is what I was going to try.  Am I missing something?

Don't forget to set the correct offset in the mtools/devices.c file.
In my case I have the DOS partition at the beginning of the disk, Cyl.
0 - 80. However the first 8704 bytes contain the fdisk partition table
and the system boot code. These must be skipped by mtools. Thus the
line in devices.c looks like:
  {'C', "/dev/wd0d", 8704L, .. followed by the other parameters all
set to 0. }, so you don't need to supply the disk geometry to mtools.
There is an example for this line in ther devices.c file already.
Watch out for any such line containing an offset other than 0L.

good luck
-Gunther




--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
Newsgroups: comp.unix.bsd
From: wollman@trantor.emba.uvm.edu (Garrett Wollman)
Subject: [386BSD success] My configuration...
Organization: University of Vermont, EMBA Computer Facility
Date: Mon, 27 Jul 1992 00:47:34 GMT

I thought that some people might be interested in various systems and
configurations that work.  I'm running 0.1 on an AT&T(sorry) 6386E/20
system with a busted internal async port and two 135-Meg ESDI hard
disks that are in the process of developing bad sectors that I can't
get rid of now because sector forwarding was not turned on when I
first set up the disks.  The system seems to work quite well, but for
lots of slio overflows (the working com port uses an 8250) when
running SLIP.  I haven't yet finished writing the StarLAN/i82586
Ethernet driver, but I hope to have it done by the end of next week.

Here is the configuration I use.  Someday, maybe I'll hack `config' to
get the disk drives right (or at least add a message ``don't forget to
add your extra drive in ioconf.c'')...  MFS works quite well,
especially since I configured *way* too much swap for this machine (32
Meg, four times ram size) so I have plenty of space to spare.

#
# TSORNIN - my machine
#
machine		"i386"
cpu		"i386"
ident		TSORNIN
timezone	5 dst
maxusers	10
options		INET,MFS,NFS
options		"COMPAT_43"
options		"TCP_COMPAT_42"
# do we still need this?

config		"386bsd"	root on wd0 swap on wd0

controller	isa0
controller	wd0	at isa? port "IO_WD1" bio irq 14 vector wdintr
disk		wd0	at wd0 drive 0
disk		wd1	at wd0 drive 1
# grrr... someday, maybe this will work automatically...

controller	fd0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk		fd0	at fd0 drive 0

device		pc0	at isa? port "IO_KBD" tty irq 1 vector pcrint
device		npx0	at isa? port "IO_NPX" irq 13 vector npxintr
device		com1	at isa? port "IO_COM1" tty irq 4 vector comintr
device		com2	at isa? port "IO_COM2" tty irq 3 vector comintr

pseudo-device	loop
pseudo-device	ether
pseudo-device	sl	1
pseudo-device	log
#pseudo-device	ddb
pseudo-device	pty	4

pseudo-device	swappager
pseudo-device	vnodepager
pseudo-device	devpager

-GAWollman

-- 
   Garrett A. Wollman  = wollman@emba.uvm.edu = UVM is welcome to my opinions
                       =    uvm-gen!wollman   =
   That's what being alive is all about.  No deity, no higher goal
   exists, than to bring joy to another person.    - Elf Sternberg
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: wdbootblk.c
Organization: Supercomputing Research Center (Bowie, MD)
Date: Fri, 24 Jul 1992 17:30:03 GMT


on 0.0, i was looking at wdbootblk.c to see why i could not boot a 
> 400k kernel. Now this may not apply to 0.1 source, i don't have that up
yet, but it is interesting. My copy of wdbootblk.c copies itself up to 0x70000
so that there is room for the kernel, but:
reloc:
        movl    $ BIOSRELOC,%esi
        movl    $ RELOC,%edi
        movl    $512,%ecx
        rep
        movsb
 movl $0x60000,%esp
        pushl   $dodisk
        ret

note that the stack is set up at 0x60000, which is below the end address
of a kernel bigger than 393216 bytes! once we read in the kernel 
the stack is now hash. I expect that this is the cause of my 
woe. Anyone see a problem putting the stack at RELOC? i.e. stack top is 
at RELOC, which is ok as the first thing we do is a pushl. 

so it might look like:
reloc:
        movl    $ BIOSRELOC,%esi
        movl    $ RELOC,%edi
        movl    $512,%ecx
        rep
        movsb
	movl $ RELOC, %esp
        pushl   $dodisk
        ret


ron
-- 
--------------------------------------------------------------------------------
satisfaction: the feeling you get when you        | rminnich@super.org
run newfs on a DOS disk so you can install 386BSD.| (301)-805-7451
Now if only I could do this to AIX on the RS/6k ...|
Newsgroups: comp.unix.bsd
From: leisner@trianguli (Marty Leisner 311/? x?)
Subject: Re: Installing boot disks on a sun sparcstation
Reply-To: leisner.henr801c@xerox.com
Organization: Xerox
X-Newsreader: Tin 1.1 PL4
Date: Thu, 23 Jul 1992 12:21:07 GMT

leisner@trianguli (Marty Leisner 311/? x?) writes:
: Well, I don't know what I'm doing wrong, but whenever I insert a boot disk into a compaq, it starts to read the 
: disk, then reboots (displays the ram count)...in an infinite loop.
: 

I just bought a cheopo PC to have at home (KLH clone, 1 meg/386 for now, 40 meg Hard)

My 386BSD disk boots on this machine (doesn't do anything, complains about the lack of ram...should it come up with a prompt?)

It prints the initial half a screen and just doesn't seem to do anything (but I ddin't expect this machine to run Unix).

Anyone know what wrong withthe Compaq?  I tried several machines (with up to 16 meg of ram) with the same (negative) results.

--
marty
leisner.henr801c@xerox.com  
Member of the League for Programming Freedom
Newsgroups: comp.unix.bsd
From: dealwisb@cognos.com (Brian de Alwis)
Subject: Re: Beginner's problems with 386BSD
Organization: Cognos Incorporated, Ottawa CANADA
Date: Sun, 26 Jul 1992 23:22:40 GMT

In article <1992Jul26.174358.29102@coe.montana.edu> osynw@warp.mhd.montana.edu (Nate Williams) writes:
>In article <712169547snx@rama.demon.co.uk> steve@rama.demon.co.uk (Steve Entwistle) writes:
>>4) How do I configure the system for UK local time ? I tried symlinking
>>   /etc/localtime to /usr/share/zoneinfo/GB-Eire, but this puts the clock
>>   about 8 hours ahead.
>
>I wish someone could tell me how to get my clock correct too.  I have tried
>various combinations of things, including re-linking the kernel with
>the correct offset in the config file [...]

Have you tried recompiling from scratch? (You may shudder, but make
can't check files that are dependent on compilation flags - of which
the offset is one!).
-- 
+++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: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: what are the bugs in 0.1 (READ THIS!!!)
Date: 22 Jul 1992 00:11:23 -0700
Organization: Kernel Hackers 'r' Us
Distribution: world
NNTP-Posting-Host: agate.berkeley.edu
Summary: want a comprehensive list, and people willing to test fixes
Keywords: 386bsd 0.1, bugs, foo, patches, testing

Bill Jolitz asked me to ask the people of the net what
their "favorite" bugs in 0.1 were -- basically, what exact problems
are you having?

Please, send me mail, with a subject line of "BUGS" (please, make it
all caps), with a detailed description of the problems you've had,
and as much information as you can about them.

In addition, please indicate whether or not you'd be willing to
test any potential fixes for that bug...

Thanks much,

Chris Demetriou
cgd@agate.berkeley.edu
-- 
                            Chris G. Demetriou
                             cgd@berkeley.edu

     I'm not from the computer center, and I'm *NOT* here to help *YOU*!
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.unix.bsd
Subject: 386BSD: Anyone using gcc-2.x on 0.1?
Date: 29 Jul 92 15:56:31 GMT
Organization: Jet Propulsion Lab, Pasadena, CA

While working my way around the system, I discovered that the version
of gcc shipped in 0.1 is 1.39, at least as reported by 'gcc -v'.

I'm highly interested in moving to the latest version of gcc-2.x,
(currently 2.2.2) because:

a) I'd like to take advantage of it's ability to emit 486 specific
   code (instruction scheduling, primarily)

b) Its ability to emit PIC (Position Independent Code) seems to be
   a pre-requisite for shared libraries.

Has anyone else "bootstrapped" up to 2.2.2 yet?  Has anyone who
has, rebuilt the kernel with it yet?  Does anyone have any reasons
why this might not be a good idea?

I'll be trying it anyway -- I've got nothing to loose, the worst thing
that could happen is I'd have to reload a few disks :-)

-- 

Kaleb Keithley                          kaleb@thyme.jpl.nasa.gov

Not authorized, in any way, shape, or form, to speak for anyone.
From: jtsilla@damon.ccs.northeastern.edu (James Tsillas)
Newsgroups: comp.unix.bsd
Subject: Interleving supported on 386BSD?
Date: 27 Jul 92 14:43:46 GMT
Distribution: comp
Organization: Northeastern University, Boston, MA


I am running a 386SX-16 Mhz based system with an RLL drive. Tesing has
shown that maximum drive performance can only be achieved using a 2:1
interleve. I noticed there was no mention of interleve anywhere in the
installation procedure. Does 386BSD lack support for interleving or is
this handled by the low level format?

cheers,
-Jim.
--
***                                                      ***
***  James Tsillas  jtsilla@damon.ccs.northeastern.edu   ***
*** ..see you at Korova Milk Bar brothers and sisters..  ***
***                                                      ***
From: wcerveny@cbnewsk.cb.att.com (william.j.cerveny)
Newsgroups: comp.unix.bsd
Subject: Booting 386BSD, tape drives
Keywords: mouse video tape drive 386BSD
Date: 24 Jul 92 14:41:49 GMT
Distribution: usa
Organization: AT&T


Couple of questions:

1)  Every time I attempt to boot 386BSD off an AT&T 6386/25, I get flashing
characters on the screen (same thing happened with 0.0 as with 0.1).  There
is a mouse port on this machine with no clear method for disabling it.
The PC has an AT&T VDC 600 VGA card also.  I've been thinking that the problem
is with the mouse port, but I won't rule out the possibility that VGA card
is at fault (VGA card uses Paradise chipset).

I do have 386BSD 0.1 up and running on a Zeos 486-DX2-50.  No problems
installing, although I did panic a little when 386BSD would not accept 
keyboard input after the first reboot when the binary installation completed.
I rebooted and 386BSD went into a panic on boot-up twice.  Finally 386BSD 
booted normally and everything has been stable since.

2)  What tape drives have people been having success with?  I want to get one
ASAP, but I dont't want one which doesn't work and I would like to spend as
few bucks as possible.

Bill Cerveny
w.j.cerveny@att.com
Opinions expressed are not necessarily those of my employer.
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: 386BSD 0.1 kernel sources ?
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Wed, 29 Jul 1992 19:21:57 GMT

In article 20710@cs.hw.ac.uk, donaldh@cs.hw.ac.uk (Donald I. Hunter) writes:
>To get the 386BSD kernel sources do I have to download the entire
>source distribution ?  I don't have the space (nor will I ever have) to
>take the whole distribution so I was wondering if someone would be kind
>enough to provide just the Kernel sources for anonymous FTP.
 
The kernel sources are conveniently at the beginning or the src01 archive.
If you just want the kernel pick up the first 12 or so parts of the archive
and unpack them as follows:

cd /
cat $foo/src01.* | uncompress | cpio -idalmuv

where $foo is the directory where you put the src01 files.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: kwan@netcom.com (Kwan-Seng Low)
Subject: Re: Removing 386BSD from the hard disk
Date: Thu, 23 Jul 92 00:39:13 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: 386BSD

low level format your hard disk.
Kwan