HDTenEightyP/NetNews huggingface dataset:
From: greg@ecse.rpi.edu (Greg)
Subject: Re: 386bsd-0.1: primary bootstrap (wdbootblk.c) problem & fix.
Keywords: 386bsd boot bootstrap wdbootblk.c
Date: Mon, 27 Jul 1992 18:21:35 GMT

terry@npd.Novell.COM (Terry Lambert) writes:

>In article <greg.712111605@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>>   In a recent post I described a booting problem I was having: I could only
>>boot about 20% of the time in high speed mode. I tried all the latest patches,
>>but the problem persisted. By putting a printf at the top of boot.c, I          determined that it was not making it out of wdbootblk.c.

>[ ... code describing delay loop deleted ... ]

>Folks, *DON'T FIX IT THIS WAY!*

>the correct fix is to either use the patched boot files in the "unofficial"
>directory on Agate (new "dist.fs"), or to do the following (which only
>partially recreates the patch):

[ patch to wd.c deleted ]

Terry, please reread my message. THIS IS NOT THE SAME BUG!!!!!!
This problem is in wdbootblk.c. The code contained in wd.c has not
even been loaded off the disk at the point when this hang occurs! 
To understand what is going on, study wdbootblk.c.

I agree that this may not be the best fix, as it treats the symptoms rather
than curing the cause of the problem, but it does work. I believe that
Bill Jolitz is working on a more insightful solution to this problem. 
But for those of us who want it now, this serves as an adaquate temporary
fix.

So, to everyone having booting problems: Try the lastest bootables on 
agate.berkeley.edu, but if that doesn't help, feel free to try a
solution like mine. You can determine whether the primary bootstrap is 
successful by putting a printf in main() of boot.c. If you never see it,
then it is hanging in wdbootblk.c

Terry, please take some time to study wdbootblk.c and to understand the
boostrap process before you make such forceful recommendations.


                    Greg - greg@megas.ecse.rpi.edu
Newsgroups: comp.unix.bsd
From: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Subject: 386BSD and the DEC EtherWORKS Turbo Ethernet Controller
Reply-To: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Organization: Digital Equipment Corporation
Date: Tue, 21 Jul 1992 13:29:45 GMT

Has anyone got a installation floppy that will work with the DEC
EtherWORKS Turbo 
Ethernet Controller. After waiting patiently for a system which didn't
require a
FPU, it has been a bitter blow to find that the blasted ethernet card
doesn't show up
at boot time.

regards Francis J. Hitchens
Newsgroups: comp.unix.bsd
From: roe@Unibase.SK.CA (Roe Peterson)
Subject: Bugfix for mountd
Keywords: mountd
Organization: Unibase Telecom Ltd.
Date: Fri, 24 Jul 1992 05:51:36 GMT

Hi.

Congratulations and kudos to the Jolitz's for 386BSD 0.1.  Hell of a nice
job, and our contribution will be winging its' way toward them right quick.

Found a little bug in mountd:  If /etc/exports contained:

	/usr/src -root=0

And /usr was not a file system unto itself, mountd went into an infinite
loop and stayed there.

The fix:  in /usr/src/sbin/mountd/mountd.c, line 592 reads:
	while (*cp == '/' && cp > ep->ex_dirp)
and should read:
	while (*(cp-1) == '/' && cp > ep->ex_dirp)
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI tape drive not accessible
Date: 25 Jul 92 06:41:24 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <TMH.92Jul23041936@keks.first.gmd.de>, tmh@keks.first.gmd.de
(Thomas Hoberg) writes:
>I managed to get the "Tiny BSD" floppy accross the modem and got
>386BSD installed on my system (486/33, 16MB, ET4000/8514, AHA1542, 1GB
>Wren VII + 88MB Syquest SCSI drives, Tandberg TDC3800 QIC 525 SCSI
>Streamer). The SCSI disks are at targets 0+1, the tape drive is at
>target 4. On boot up, only the first disk is recognized. Trying to
>read off /dev/ras1a seems to attach the Syquest drive. Any attempt to
>read /dev/ras4a results in an error. cat </dev/ras4a returns "bad file
>descriptor", cpio -itvc </dev/ras4a returns "error 9". All other
>targets return "sense errors" with lots of status data (mostly zeros).
>Does 386 support only certain tape drives? The drive works fine with
>ISC UNIX, DOS (various programs) and OS/2 (modified GTAR).

The SCSI tape drive I was using had the same problem.  Try
configuring it as lunit 2.  It seems to work at 2 with one or
two SCSI drives.  I have not traced down why it will not work as
unit 4, but I suspect it could be changed in the kernel configuration.

I believe you are correct in that most other O/Ss expect it as unit 4.
If Bill is reading this and it is possible to change in the configuration,
maybe the first set of official patches will change this.

>BTW: I use a small partition booter wholly contained within the master
>boot block. Works like a charm! I can select any OS to boot at
>startup. In theory I could even boot off a second disk drive (the OS's
>secondary bootstrap has to support that, though (e.g. DOS doesn't). If
>there is interest, I could post it together with a (DOS based)
>installation program.

I'm interested.  Especially in the part that allows possible booting from
a second disk.  The partition booter I was using is not compatible with
386BSD.

-- 
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: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.unix.bsd
Subject: Re: Another 0.1 success
Date: 21 Jul 92 12:53:14 GMT
Organization: Naval Medical Research & Development Command

In article <1992Jul20.171559.22562@cunews.carleton.ca> ebx@scs.carleton.ca writes:
>In article 17787@usl.edu, pml@cacs.usl.edu (Patrick M. Landry) writes:
>
>> ...
>>I have one newbie question. Since the install only creates
>>one partition by default where does the system do swapping?
>> ...
>
>Another one with the same question.
>
>I noticed that du reported a smaller file system capicity than the space
>I left to 386bsd. Is that implying those MBs going to swapping? Since I
>could see only one partition, if any swapping, it must be file swapping or
>in an invisible partition. Am I right?
>
>I didn't see any 'sw' in /etc/fstab neither.
>
By default, the install procedure creates a 10000 sec (5Mb) wd0b partition.
This can be seen with a disklabel -r wd0.  To use the swap device, add the
following line to /etc/fstab:

/dev/wd0b	/	swap sw

It should be used automaticly at bootime or you can activate it with
"swapon -a".

Mike

-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
Newsgroups: comp.unix.bsd
From: Havard.Eidnes@runit.sintef.no (Havard Eidnes)
Subject: iostat -- missing kernel pieces
Originator: he@spurv.runit.sintef.no
Organization: Computing Center at the University of Trondheim, Norway
Date: Wed, 22 Jul 92 22:19:49 GMT

Hi,

this evening's project of 386bsd 0.1 hacking was planned to be a port of
iostat from NET2. I've modified the names.c file in usr.bin/vmstat to read
in the device structs from _isa_devtab_bio, and on "my" system it finds fd0
and as0 just fine.  I noted one odd thing, and that was that the isa_device
struct lacks a id_dk field, which on the other systems names.c support
apparently is to be used as a global index of some sort. I worked around
this by using a local index, and counting it up as I went through the bdev
(?) device table.  The rest of iostat compiled more or less effortlessly.

However: iostat does not show any values other than 0 for the "sps", "tps"
or "msps" fields for all drives. These values are supposed to be fetched
from various arrays in the kernel: dk_xfer, dk_wds, dk_seek etc.  After
grepping through the kernel sources, it appears that the only place these
variables are ever mentioned is in the sys/dkstat.h include file -- noone ever
bothers to update these arrays.  I did in particular investigate the device
drivers for wd, as and fd, and came up emptyhanded.

Without a global "disk index" in the block (?) device table and without device 
drivers updating these statistics, it appears that it is going to be difficult 
to create an iostat which shows any useful info.

Unfortunately, hacking in the global disk index and modifying the device
drivers are currently above my skill level, and I don't have the available
time (sorry -- vacation soon too...), so I'm going to shelve this project
for now.  If someone decides to put in the disk index and the device drivers
are modified accordingly, I'll happily pick it up again. ;-)

- Havard
Newsgroups: comp.unix.bsd
From: walter@insu1.etec.uni-karlsruhe.de (Reiner Walter)
Subject: Graphical debugger for X11
Organization: Institut fuer Nachrichtensysteme, Uni Karlsruhe
Date: Fri, 24 Jul 1992 12:01:48 GMT


I search a graphical debugger for X11.

Can anybody suggest me one.
Where can I get it.

Thank you

-- Reiner

Newsgroups: comp.unix.bsd
From: sitongia@ozzel.hao.ucar.edu (Leonard Sitongia)
Subject: 386BSD: rawrite says "address mark not found"
Reply-To: sitongia@ozzel.hao.ucar.edu (Leonard Sitongia)
Organization: High Altitude Observatory/NCAR, Boulder CO
Distribution: usa
Date: Thu, 23 Jul 1992 21:02:43 GMT

I've been trying to build a Tiny 386BSD floppy from 386BSD 0.1 to use to
qualify a PC to buy.

I've ftp'd the executable rawrite and various dist.fs files, Kermit'd them
to a Gateway 2000 386, and I run rawrite there.

If I write a 3.5" floppy, rawrite gives no complaints, but then I dont have
a PC around that I can boot off the 3.5 drive.

If I write dist.fs to a 5.25" floppy (1.2M floppy), it gets to head 80
and stops with the message "address mark not found".

The floppy will not boot on any of serveral different 386's I've tried
around here.

Thanks for your help.

-- 
--Leonard E. Sitongia           HAO System Manager                 
sitongia@ncar.ucar.edu          voice: (303)497-1509   fax: (303)497-1589
High Altitude Observatory       P.O. Box 3000 Boulder CO  80307
From: athos@eyrie.img.com.au (David Burren)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 scsi tape problem
Date: 30 Jul 92 04:13:16 GMT
Organization: img Consultants, Melbourne, Australia

In <1992Jul28.033036.18989@raid.dell.com> james@raid.dell.com (James Van Artsdalen) writes:

>I am running 386BSD 0.1 on a Dell 433P with 16 MB of DRAM, using an
>Adaptec 1542B with a 660 MB Micropolis SCSI disk and an HP 2 GB SCSI
>DAT tape drive.  I am having trouble writing to the tape drive.

>   changing root device to as0a
>   as0: attached tgt 0 <MICROP 1588-15MB1036511 AS0C> winchester disk 
>   as0: attached tgt 4 <HP HP35480A A> tape 
>   as4a: controller error 0x12 writing fsbn 0-19
>   scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
>   as4a: controller error 0x12 writing fsbn 20-39
>   scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 

>... more controller errors and scsi sense lines...

>Any guesses as to what's wrong?

I was getting similar sense messages on all SCSI devices until I realised
the 1540's BIOS wasn't enabled.  I haven't had a chance to look at the
as driver yet, but I think it's possible it's relying on part of the
board being initialised by the BIOS on boot.

Your disk is apparently behaving, so this might not be your problem, but
what the hell...

- David B.
  athos@img.com.au
From: peter@micromuse.co.uk (Peter Galbavy)
Newsgroups: comp.unix.bsd
Subject: It's OK now, was: Re: Floating Exception while trying install... no 387, help !
Date: 23 Jul 92 16:28:11 GMT
Organization: MicroMuse Limited, London, England.

In article <1992Jul22.183035@micromuse.co.uk>, peter@micromuse.co.uk (Peter Galbavy) writes:
> 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.

OK. I suppose I should have tried waiting a bit... but the problem was caused
by the disk not being 'FDISK'ed first. Running "fdisk /mbr" made it all go
OK.

I think though that the thing shouldn't core dump though. Thanks all.

I am hoping to buy a Tosh 4400SXP laptop to go with it - does this work
OK ?

And double thank you's to Bill & Lynne and all the others, great system,
-- 
Peter Galbavy
Tech Support, Micromuse Ltd
Phone: +44 71 352 7774		E-Mail: P.Galbavy@micromuse.co.uk
From: welsh@nosc.mil (Robert C. Welsh)
Newsgroups: comp.unix.bsd
Subject: Cannot install 0.1
Date: 27 Jul 92 21:42:14 GMT
Organization: Naval Ocean Systems Center, San Diego, CA


I Need Help with 386BSD-0.1 install

When I try to boot TinyBSD it senses the following:

"	pc0<color> at 0x60 irq 1 on isa
	com1 at 0x3f8 irq 4 on isa
	com2 at 0x2f8 irq 3 on isa
	wd0<DTC6X80> at 0x1f0 irq 14 on isa
	fd0 drives 0: 1.2M at 0x3f0 irq 6 drq 2 on isa
	npx0 at 0xf0 irq 13 on isa "


The first time I try to boot after power up I get as far as

"	changing root device to fd0a "

and a second later I get

"	trap type 18 code = 0 eip = fe055532e cs = 8 eflags = 10246
	cr 2 0 cpl 4040
	panic: trap
	hit reset please "

If I hit reset it goes through the above but further and comes up on the floppy.
I can then do most things in TinyBSD but as soon as I run install it gives me
almost the same messages as above (the differences are underlined):

"	trap type 18 code = 0 eip = fe055532e cs = fe41008 eflags = 10246
                                              ------------
	cr 2 dee0 cpl 4040
	     ----
	panic: trap
	updating disks "

My hardware is as follows:

AST Premium/386C with 4 MB ram, cache disabled, shadow ram disabled, 387 co-
processor.  (Premium 386 BIOS Ver 2.0)

Oak Technology VGA board (VGA BIOS 067 V1.03) with 512 memory

DTC 6280 ESDI disk controller running a Maxtor 4380EXT hard drive (340MB)

Hope someone can help as I have been following the group for months waiting
to get a shot at this (I just got the disk controller and drive)!

		welsh@manta.nosc.mil

"Strange women, lying in ponds, distributing swords is no basis for a system
of government" - Monty Pyton
Newsgroups: comp.unix.bsd
From: greg@coombs.anu.edu.au (Greg Price)
Subject: 386BSD-0.1 Disk Controllers - Help Needed
Keywords: 386BSD
Organization: Computer Services Centre, Australian National University
Date: 28 Jul 92 15:47:23 GMT


Hi there...I have just been playing around with 0.1 and have the following
problem:

All works fine when I use only one drive, but when I try to boot with a 
kernel supporting 2 drives I get a hang after the "npx0 at 0xf0 ...." message
(I don't see "changing root to fd0a" or anything else). I am trying the 
kernel supporting 2 drives from f.ms.uky.edu (unofficial). I hope I'm doing
the correct thing to test it...I loaded the mini system onto the 1st HDD
then read the new 2 drive kernel from the floppy and copied it on top of
/386bsd. I am in this situation as I don't have enough disk space to load
the source until I get the second drive going. System config as follows:

386DX
WA6-V MFM HDD/FDD Controller with Miniscribe 6085 connected
CI-1010 Rev A Ver 1.12 IDE Controller with 200Meg Connor connected

I had to use the CI-1010 controller as it's one of the few the allows 
IDE drives to coexist with MFM. It all works fine under DOS. The IDE
is always (and according to the CI-1010 docs) has to be the second drive.
Hope some one out there can help, or has had experience with this.

Thanks,
Greg

(greg@coombs.anu.edu.au)

ps. Good work Bill, Lynne, and faithful followers

Newsgroups: comp.unix.bsd
From: michael@resonex.com (Michael Bryan)
Subject: Re: I wonder, did AT&T backstab BSDI?
Keywords: AT&T speculation lawsuit BSDI
Organization: Resonex Inc., Sunnyvale CA
Date: Wed, 29 Jul 1992 23:28:51 GMT

In article <1992Jul29.182141.10399@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>SVR4 is System V, Release 4.  System 7 was an early version of Unix
>way back (in the pre-dawn era :-) )

Isn't that "Version 7" or "7th Edition", not "System 7"?

-- 
Michael Bryan        michael@resonex.com                     |     ,_,
"Pretenders I meet are making a trail along the way.         |    /oo \
They say that they know how to show me a path to guide my    |    <>__|
way to truth..." --- David York, "The Quiet of a Candle"     |    |  U|
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: Adding users
Date: 28 Jul 92 02:56:39 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <9207241849.AA06522@nms1.abb.com>, MLUCI@fuel.abb.com (Mark
Lucia 2915) writes:

>       Please pardon the newbe question, but I'm having trouble adding 
>       users (me) to 386bsd-0.1.

Use 'vipw' to edit the /etc/passwd file.

We really need an FAQ guys.  Didn't we have a volunteer with 0.0?     

-- 
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: quanstro@lars.StOlaf.edu (goon)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: St. Olaf College, Northfield, MN USA
	<9207221021.53@rmkhome.UUCP>
	<1992Jul23.181508.23309@vlsi.louisville.edu>
Date: 24 Jul 92 12:31:53

In article <1992Jul23.181508.23309@vlsi.louisville.edu> meharp01@vlsi.louisville.edu (Michael Harpe) writes:

   Oh well, I hear that Windows NT will be an OK environment.  Have fun, guys!


I've also heard that the food at the local High School cafeteria is edible.

Newsgroups: comp.unix.bsd
From: wade@leland.Stanford.EDU (Wade Hennessey)
Subject: 50 line display
Organization: DSG, Stanford University, CA 94305, USA
	MODE CON: LINES=50
Date: Wed, 29 Jul 1992 22:45:12 GMT
From: jburnes@swbatl.sbc.com (Jim Burnes - 235-7444)
Newsgroups: comp.unix.bsd
Subject: Cant Boot Tiny Disk - HELP!
Date: 21 Jul 92 06:32:43 GMT
Organization: Southwestern Bell

Hi!

I DL'ed rawrite and the dist.fs and fixit.fs to my PC at home.  I
then put both images on their respective 1.2 meg floppies and booted
my system.

It read the tiny disk for about 5-10 seconds and rebooted my machine.
For the record I have a pretty generic 386 box ( except for the
drive controller).

         AMI BIOS (circa 1990).
         AMI 386/20 motherboard, 4 meg RAM, 64k cache
         Orchid ProDesigner Plus VGA
         Perstor ARRL controller (gives you about 1.9 x MFM)
         Miniscribe 80meg (ARRL gives you about 150meg)
         No 387

I've tried disabling video shadow ram to no avail.


Has anyone seen this problem?
BTW: After rawrite had written the entire fs to disk (apparently
without error) I got a "couldnt find address mark" error.  Is
this a standard message that rawrite burps out?

I've crashed and I can't get up....

Thanks in advance,

Jim Burnes


---------------------------------------+--------------------------------------
    Jim Burnes, jburnes@swbatl.sbc.com | SWBell Advanced Technology Labs
---------------------------------------+--------------------------------------
   Truth :  the most deadly weapon ever discovered by humanity. Capable of
   destroying entire perceptual sets, cultures, and realities. Outlawed by
   all governments everywhere. Possession is normally punishable by death.
------------------------------------------------------------------------------
From: terry@npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 Boot and Video Problems
Keywords: 386BSD
Date: 30 Jul 92 17:31:29 GMT
Distribution: comp.unix.bsd
Organization: Novell NPD -- Sandy, UT

In article <1992Jul30.010100.6107@msuinfo.cl.msu.edu> rjs@crs.cl.msu.edu (Robert J. Stanton) writes:
>2)  When I  use  "nn" or   use   more on the
>    INSTALL  notes, I get blinking text
>    instead of highlighted text.

This has to do with whether or not register 2 is correctly set up on your
video controller (bit 4 or bit 5, if I remember correctly).  Most video
adapters which emulate the register set will not do so unless jumpered for
"extended VGA" or something similar.  ATI's EGA Wonger has this problem.
Check out the "IBM Techinal Reference Manual", the section on the CGA
card.  The register controls whether the high bit of the Background color
nibble is the "highlight color bit" or the "blink bit".

>Also, I wish that the cursor did not flash so
>rapidly.

This is a function of the clock on your video card, since most cursors are
hardware.  There may or may not be a fix for this based on writing some
value into some [defined by the manufacturer] register.

					Regards,
					Terry
From: wilker@hopf.math.purdue.edu (Clarence Wilkerson)
Newsgroups: comp.unix.bsd
Subject: Re: tape drive problems
Date: 21 Jul 92 21:29:42 GMT

Will an ARCHIVE 60 meg tape with the SC499R controller work for
the wt0 device?
-- 
Clarence Wilkerson      \ Bitnet:       wilker%math.purdue.edu@purccvm
Prof. of Math. (topology)\ Internet:    wilker@math.purdue.edu
Dept. of Mathematics      \ messages:   (317) 494-1903, FAX 494-0548
Purdue University,         \ office:    (317) 494-1955 (voice/modem)
W. Lafayette, Indiana 47907 \
From: dennis@nebulus.ampr.ab.ca (Dennis Breckenridge VE7TCP)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 29 Jul 92 18:30:40 GMT
Organization: Alchemy Mindworks, Edmonton, Alberta

When I posted that I meant BSDI. I know about the rest c'mon guys!
-- 
-------------------------------------------------------------------------------
At first sight, the idea of any rules or principles being superimposed on the
creative mind seems more likely to hinder than to help,but this is quite untrue
in pratice. Disciplined thinking focus inspiration rather than blinkers it. 
-------------------------------------------------------------------------------
From: ken@sugra.uucp (Kenneth Ng)
Newsgroups: comp.unix.bsd
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
Date: 26 Jul 92 05:50:50 GMT
Organization: Private Computer, Totowa NJ

In article <1992Jul22.163407.10823@Warren.MENTORG.COM:, tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
: Gee, I went to a tiny liberal arts school that doesn't get all those
: favors and perks from Corporate America.  I never have seen a source
: license.  I guess that just bumped up the value of my degree?  HHOS.

I wouldn't call Drew University a tiny school.  Liberal arts yes, but not
tiny.  Furthermore, from what I have read here, AT&T is not suing on the
basis of copyright infringement, it is suing based on the *IDEA* of UNIX(R).
You know, concepts like pipes, forks(), tree structured directories, setuid,
etc.  

In this political year, has anyone tried contacting the various candidates
to see how they stand on this issue?  It may be interesting.

-- 
Kenneth Ng
Please reply to kdn5669@hertz.njit.edu for now.
AT&T and Apple: Just say NO!