HDTenEightyP/NetNews huggingface dataset:
From: obi@gumby.ocs.com (Kuryan "Obi" Thomas)
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
Reply-To: obi@gumby.ocs.com
Organization: Online Computer Systems, Inc.
Date: Sat, 25 Jul 1992 19:21:02 GMT

I've been following this thread with some interest. I have some questions
to those in the know:

1. (Ignorant.) What exactly IS NET/2 anyway?
2. Does BSDI make only Intel ports of BSD?
3. Why is only this vendor targeted by USL? Why not Sun Microsystems or
   any of the numerous other vendors who produce BSD-type systems?
4. Any thoughts on what the effect of a win/loss by USL will be on other
   vendors?
From: jaap@alice.att.com (jaap)
Newsgroups: comp.unix.bsd
Subject: Re: libcompat.a missing?
Date: 31 Jul 92 19:02:35 GMT
Reply-To: jaap@alice.UUCP ()
Organization: AT&T, Bell Labs

In article <sxjcb-300792181914@sxjcb.uacn.alaska.edu> sxjcb@orca.alaska.edu (Jay C. Beavers) writes:
 > Ok, I've just installed the etc and src distributions and I've been trying
 > to compile the games that come with etc, however, on a number of games I've
 > run into an error that libcompat.a is missing.  I checked /usr/lib and it
 > isn't there nor is the source located in /usr/src/lib.  What am I missing?
 > 

The fact that the compat library allowed you to run programs compiled
on the pdp-11 using the -11 compatibility mode.  So If you really want
to do this on a 386, you have to roll your own to get the 386 in -11
compat mode, or alternatively, simulate a VAX on the 386 and then use
libcompat.a on that simulator to run in -11 compat mode.

	jaap
Newsgroups: comp.unix.bsd
From: dealwisb@cognos.com (Brian de Alwis)
Subject: Re: I wonder, did AT&T backstab BSDI?
Summary: Mach & BSD & NextStep
Keywords: AT&T speculation lawsuit BSDI
Organization: Cognos Incorporated, Ottawa CANADA
Date: Tue, 28 Jul 1992 22:09:27 GMT

In article <1992Jul28.153750.8395@mintaka.lcs.mit.edu> knight@hal.gnu.ai.mit.edu (Knight of the Living Dead) writes:
>If so, Steve Jobs at NeXT may find MACH being charged with having
>unlicenced BSD-like code that is property of AT&T.

If memory serves me correctly, NeXTStep is based on Mach 2.5 (or
2.3?), which requires an AT&T license. So NeXT should be safe. 
 
+++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: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 31 Jul 92 17:42:30 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

In article <1992Jul30.173606.28357@kas.helios.mn.org> rhealey@kas.helios.mn.org (Rob Healey) writes:
|	Just to remind the non-US audience, this legal action is being
|	done in the US so by definition of the US legal system NOTHING
|	is insane or absurd because the US "legal" system IS insane and
|	absurd. This comes from lawyers controlling the legal, judicial,
|	legistative and executive branches of the US government, i.e. a
|	complete monopoly, to make the government and law infinitely complex
|	and absurd.
|
|	Be glad you don't have to deal with our excuse for a legal system...
|
|		-Rob

As a matter of interest, since this case is taking place in the US, what
effect will it have on us non-US users. For instance, I don't see how
they could possibly get back copies of NET-2 from non-US sites or for
that matter, recall copies of BSDI from outside the US. Since I know
nothing about law, let alone international law, I could be completely
and utterly wrong of course.

As far as 386bsd is concerned, even if the Jolitz's are sued the project
could always be based around sites outside the US so its future seems
pretty safe. Of course I could be wrong about this too.
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@thor.cf.UUCP or ...!uunet!mcsun!ukc!cf!thor!spedpr
+++
From: T.D.G.Sandford@bradford.ac.uk (TDG SANDFORD)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 lpt.c - anyone got it to work?
Date: 31 Jul 92 11:49:16 GMT
Organization: University of Bradford, UK
Originator: 90908106@muser

Has anyone managed to get the lpt.c (parallel printer driver) supplied
in the 0.1 kernel sources to work? I've managed to get it to compile :-)
but it won't even find my lpt1: port at 0x378.

BTW several modifications to source and to kernel configuration files are
required even to get that far!!

I'll keep working at it, but if someone else has done it, it'll save me
duplicating effort.

Another point: what is the method used to create the diff-like patches
that are posted to this group - and what is the way to apply them to the
files automatically, rather than typing them in by hand :-( ?
--
Thomas Sandford | t.d.g.sandford@bradford.ac.uk
Newsgroups: comp.unix.bsd
From: keithl@klic.rain.com (Keith Lofstrom)
Subject: Re: AT&T sues BSDI
Keywords: BSDI AT&T
Organization: Keith Lofstrom Integrated Circuits
Date: Wed, 22 Jul 1992 02:07:58 GMT

I think AT&T ought to get a new motto:

"AT&T - anything better is illegal!"


-- 
Keith Lofstrom         keithl@klic.rain.com       Voice (503)-520-1993
KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon"
Design Contracting in Bipolar and CMOS - Analog, Digital, and Power ICs
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Thu, 23 Jul 1992 20:04:18 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Jul22.221515.23550@tfs.com> paigen@tfs.com (David Paigen) writes:
>wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>
>>In article <1821@adagio.UUCP> grog@adagio.UUCP (Greg Lehey) writes:
>>>....
>>>The real issue here is, of course, not the source. AT&T must know
>>>about Bill Jolitz; according to the text here, he's guilty of the same
>>>`crime'....
>
>[deleted]
>
>>Please refrain from using inflammatory words such as "crime" with respect to
>>386BSD and the developers, as we are not involved in this matter.  We have 
>>no relationship with BSDi or CSRG, nor do we condone the actions of any
>>party involved in this dispute.
>
>I think you have missed the point, Bill.  If BSDI is guilty of the 'crime'
>of developing an OS from the NET 2 tape, so are you.  I do not condone
>the classification of BSDI's actions as a crime, nor do I condone the
>actions of AT&T.
>
>I think someone should give BSDI a medal for doing their work.  More to
>the point, we should start contributing to the "BSDI legal defense fund."


I don't think that AT&T really wants to win.  They just want to tie BSDI
up in court, and make them spend some money, while they rush Destiny out
the door.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: using mtools to access dos partitions
Date: 24 Jul 92 08:07:38 GMT
Organization: Amdahl Corporation, Sunnyvale CA


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.
>
>With the new "wd" driver that uses the "a5" partition for the BSD
artition...
>none of the devices in "/dev" correspond to the DOS partition.[ 
>HOWEVER:  the escape hatch is via /dev/wd0d.  The "d" partitio covers
the
>*WHOLE* hard disk, whereas the "c" partition covers only the *whole*
>386bsd area.
>
>To build a devices.c file that lets you access the DOS partition, you
>need to know the byte offset of the DOS partition from the start of
>the hard disk.  You would then add an entry to the devices[] array
>as follows:
[ furthur explanation 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.  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.  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').

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

-- 
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.
From: mellon@ncd.com (Ted Lemon)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 23 Jul 92 22:12:23 GMT
Organization: Network Computing Devices, Inc.
In-reply-to: mcuddy@fensende.Rational.COM's message of 22 Jul 92 09:00:34 GMT


>Boycott AT&T, don't use the phone. ;-)
Actually, it's a lot easier than that.   Switch long distance
carriers, and then give AT&T a call and tell them why (or write them a
letter).   AT&T makes virtually *no* money on licensing compared to
what it makes on phone services.   A boycott of AT&T phone services
would probably be taken very seriously; you need only watch TV to see
how seriously.

Of course, it would take a lot of people complaining to make an
impression...

			       _MelloN_
--
mellon@ncd.com
Member, League for Programming Freedom | To learn how software patents could
cost you your right to program, contact the LPF - league@prep.ai.mit.edu
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 kernel sources ?
Date: 31 Jul 92 19:12:23 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <712539144snx@close.demon.co.uk>, peter@close.demon.co.uk
(Peter Curran) writes:

> I have a similar need, but I don't think this will work for me.  I have 
> discovered that if the bin01 is extracted onto a disk <40MB (mine is 39
> and a bit) then it will not all fit on.  The manuals are missing and 
> stuff like termcap out of /usr/share/misc are missing.  Is there any way
> that I can extract only the last few files only from the floppies?

FYI, I noticed the other day that agate has a new subdirectory called
'filesystem' in the distribution directory (/pub/386BSD/386bsd-0.1)
that seems to have the files already extracted.

Also, you can extract specific files by:
  cd /; cat tmp/bin01.* | uncompress | cpio -idalmu <file1> <file2> ...

You can obtain the names of all files on the bin01 distribution by:
  cat /tmp/bin01.* | uncompress | cpio -it >bin01.filelist

Unfortunately, you still must have all of the files in the bin01 distribution
online.

An interesting solution to disk space problems might be:
  (for i in /tmp/bin01.*; do cat $i; rm $i; done) | uncompress | cpio -idalmu
Since this removes the distribution files as it goes, freeing up disk space
for the cpio extracted files.
Use this at your own risk.
#include <std/disclaimer.h>
-- 
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.
From: mikel@demax.uucp (Mikel Lechner)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd-0.1: primary bootstrap (wdbootblk.c) problem & fix.
Keywords: 386bsd boot bootstrap wdbootblk.c
Date: 30 Jul 92 01:43:56 GMT
Organization: Demax Software Inc.

In <greg.712267214@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:

>  When I first read about the other patch, I did try checking wd_alsts
>rather than wd_status. Not knowing didley about the disk controller,
>I'm not sure what the difference between these two registers are.

The only real difference is that the alternate status register does not
clear the pending interrupt flag.  This can be used to check the disk
controller status outside of the interrept handler without affecting
any I/O operation in progress.

I don't know if this is related, but I fixed a problem in the wd.c code
which caused by system to hang when I added a second hard disk.  The
problem was the disk initialization code was not checking that the
controller was ready before command it to perform a restore.  Apparently,
the disk controller is not ready quite as quickly when there is only
one disk.  Therefore the disk command is not started and the interrupt
for the disk never appears.

I fixed this problem for myself by putting all the disk controller register
manipulation into a single function which performs the important checks
before commanding the controller.  I also added a timeout in case the
interrupt never appears, but haven't needed it.

I haven't yet looked at 0.1.


-- Mikel
-- 
Mikel Lechner				E-mail:		demax!mikel
Demax Software, Inc.			Phone:		(415) 341-9017
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 25 Jul 92 11:51:07 GMT
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <1992Jul24.171828.11246@Warren.MENTORG.COM> tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
>[ 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?

Well, considering some aspects of the suit, I hope that nobody who has
seen AT&T code will admit to the fact on the net, but I can state that
somebody close to me has compared some selected BSDI and SVR4 sources
and has found very little similarity. Where there was similarity, the
AT&T sources also contained copyright notices from the Regents of the
University of California. The dissimilarity goes to the point that the
parameters to certain key functions are different in number, type and
meaning. With the exception of AT&T borrowing from UCB, they would
appear to be different implementations of an operating system of the
kind defined by POSIX.
-- 
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
From: lmjm@doc.ic.ac.uk (Lee M J McLoughlin)
Newsgroups: comp.unix.bsd
Subject: Re: More WD8003E... with some info... help?
Date: 21 Jul 92 16:18:11 GMT
Organization: Dept. of Computing, Imperial College, London. U.K.

In src.doc.ic.ac.uk:386BSD/386bsd-0.1/unoffical/dist.fs-WE800 is a
version of the dist.fs that *should* work with a WE8003 type card.
Well it works for me.

This was created with a totally disgusting hack (gnu emacs of the
/386bsd binary).

Well ftp now works for me!

	Lee
--
--
Lee McLoughlin.                          Phone: +44 71 589 5111 X 5085
Dept of Computing, Imperial College,     Fax: +44 71 581 8024
180 Queens Gate, London, SW7 2BZ, UK.    Email: L.McLoughlin@doc.ic.ac.uk
Newsgroups: comp.unix.bsd
From: raeburn@cambridge.cygnus.com (Ken Raeburn)
Subject: Re: 386BSD: Dinky little socket(?) bug -- ^V as escape character?
Organization: Cygnus Support, Cambridge MA
	<1992Jul30.081047.16575@news.tu-graz.ac.at>
	<1992Jul30.113545.23558@pasteur.Berkeley.EDU>
Date: Thu, 30 Jul 1992 18:56:23 GMT

In article <1992Jul30.113545.23558@pasteur.Berkeley.EDU> sim@cory.Berkeley.EDU (Peng-Toh Sim) writes:

   To get the "correct" behaviour, we can fix 386bsd or screen etc. or both!!!
   I think 386bsd should be fixed such that when ICANON is not set, IEXTEN
   functions are ignored.  This still follows the above definition and yet 
   will work well in practice because other POSIX programs that uses RAW mode
   will "forget" to turn off IEXTEN anyway.

"Fixing" only 386bsd will get you the desired behavior, but the
program would still be wrong.  The "screen" code should be fixed to
turn off IEXTEN, regardless of whether the kernel is changed.

Leaving 386bsd as is will help catch other broken programs, so they
can be repaired as well.  I think that's reasonable, but I expect some
aren't willing to put up with the annoyance.
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: Ouch...The System Reboots...
Date: 29 Jul 1992 10:32:33 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <39900@gremlin.nrtc.northrop.com>, dec@lazarus.nrtc.northrop.com (Dwight E. Cass) writes:
> Does the following happen on your system?
> 	4. Restart rogue and this time, allow yourself to be killed
> 	   by a monster - causing a score record to change
> 	Does your system reboot?  Mine does - no panic, no messages,
> no crash dump, just a reboot.
> Anyone got any ideas

Yup.
Same thing on my machine.
Solution: Don't play rogue.

;-)

Bernard

-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: bambi@bu.oz.au (David J. Hughes)
Subject: 0.1 on a Compaq Deskpro 386/20 ????
Organization: ITS, Bond University
Date: Mon, 27 Jul 1992 04:33:56 GMT

Seeing as we provide the Australian archive for 386BSD, I thought it was
about time I got a box up and running.  The only "spare" non-PS/2 box I
could get my hands on was a Compaq Deskpro 386/20 with a 300Meg ESDI and
6 Megs of RAM.

Well, things get about as far as the "boot beep" and that's it.  The
boot process starts but last about 2 seconds (ie. loading the bootstrap.
Nothing makes it to the screen).  At that point, the system reboots.

I have tried the same floppy on a Deskpro 386/25 with the same results.
Booting the floppy in a Toshiba 5100 laptop comes up fine.

Has anyone got 0.1 to boot on a Compaq Deskpro?  



   ___                                 David J. Hughes     bambi@bu.oz.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __          Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /    Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /       AUSTRALIA  (+61 75 951450)
From: donaldh@cs.hw.ac.uk (Donald I. Hunter)
Newsgroups: comp.unix.bsd
Subject: Booting 386BSD 0.1 Tiny
Date: 23 Jul 92 14:33:37 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland


I've been trying to boot the 0.1 Tiny distribution disk. It boots the whole
way and then hangs when the # prompt appears.

I know the machine has an ethernet controller and I think it is still set for irq 3. Does this have to be changed before 386BSD will boot correctly?

Cheers, Donald.
-- 

 +--------------------------------------------------------+
 | Donald I. Hunter                   donaldh@uk.ac.hw.cs |
 +--------------------------------------------------------+
 | Hello. Just walk along and try NOT to think about your |
 |    INTESTINES being almost FORTY YARDS LONG!!          |
 +--------------------------------------------------------+
Newsgroups: comp.unix.bsd
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: Re: Questions/problems with 386BSD 0.1
Organization: Massachusetts Institute of Technology
Date: Wed, 29 Jul 1992 04:55:20 GMT

>> 	I've been trying to get RNto compile on 386BSD 0.1. It dies on
>> linking with a undefined _stty and _gtty. I've dug through everything I
>> can think of and can't find a way around/fix for this. Has anyone gotten
>> RN to work?
There was a posting about a week ago, here's the relevant part:

>From: rivers@ponds.uucp (Thomas David Rivers)
Subject: General problems (serial line, spontaneous reboots)
Summary: Reboots, serial probs
Date: 21 Jul 92 02:51:30 GMT
...
So, now, after complaining so much :-), let me offer one trivial
helpful hint.  To compile trek (in the etc01 distribution) you need
to remove the -lcompat from the Makefile line (there is no compat library
for 386bsd), and properly define gtty() in main.c.  I added the following
two lines just before main():

#define gtty(fd, argp) ioctl(fd, TIOCGETP, argp)
#define stty(fd, argp) ioctl(fd, TIOCSETP, argp)

Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: 2 Problems: No disk Label, Tip doesn't Work
Date: 29 Jul 92 08:24:24 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <Bs3wJp.88I@watdragon.uwaterloo.ca> kcwellsc@watdragon.uwaterloo.ca (Ken Wellsch) writes:

>>	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.

I looked at SunOS to see what they did. They have 

-rws--x--x  1 acu      daemon      73728 Feb  8  1990 /usr/bin/tip

and

drwxr-sr-x 13 bin      bin           512 Jul 25 11:31 /var/spool
drwxr-sr-x  2 acu      uucp          512 Jul 23 18:03 /var/spool/locks

This looks quite reasonable. Look if something like this works under 386bsd
(perhaps replace acu with uucp, or create an entry).

Hope that helps.

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: ferrick@acsu.buffalo.edu (Patrick K. Ferrick)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd security enhancements are needed before using INTERNET!
Date: 27 Jul 92 17:29:51 GMT
Organization: UB


On the subject of security, let me mention a package that I played around with
a while back that claims to perform a check of a system's overall integrity.

The file is cops_104.tar.Z (sorry, I forget where I got it originally) and
it's 409395 bytes worth of perl scripts and assorted explanation.  (I suspect
that it might be more appropriate for commercial OSs, 'cause I doubt it can
find any security problems inherent in the code :-)

For what it's worth...

pat
Newsgroups: comp.unix.bsd