HDTenEightyP/NetNews huggingface dataset:
From: ljo@r2d2.eeap.cwru.edu (L. Jonas Olsson)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] How can I expand data segment?
Date: 6 Oct 1992 15:27:50 GMT
Organization: Case Western Reserve Univ. Cleveland, Ohio (USA)
NNTP-Posting-Host: proteus.eeap.cwru.edu

In article <veit.718359993@du9ds3> veit@du9ds3.uni-duisburg.de writes:
>In <45240004@hpycla.kobe.hp.com> yas@hpycla.kobe.hp.com (Yasuyuki Suzuki) writes:
>
>>I have 50MB of swap space on my 386BSD disk. But the data segment size
>>of each process seems to be limited around 4MB.
>
>>How can I expand data/stack/text segment size of each process?
>
>limit datasize unlimited
>limit stacksize unlimited
>

With the stock sources this will give you a 32MB limit on the data size,
for even more you need to edit /usr/src/sys.386bsd/i386/include/vmparam.h.
In this file you have the parameters for default data size (DFLDSIZ) and
max data size (MAXDSIZ) among others. I have them set to 16 and 128MB and
have successfuly used up to 45MB in one process. The system seems a little
more flaky though so some other tweaking/bug fixing might be needed. Also
note that the system grinds to a halt when the swap space is used up, there
is no friendly message "virtual memory exhausted" and the mallocs don't
return 0.
What kinds of paging are used/possible to use in 386BSD? There are options
in the config files for swappages, vnodepager, and devpager. Is the
vnodepager similar to Mach's inodepager? (Mach systems can page to empty
inodes on the regular partitions and does not need any swap partition)
Is it possible to get the vnodepager to do this?

Jonas Olsson
ljo@po.cwru.edu


Newsgroups: comp.unix.bsd
From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Subject: ARCHIVE of 386bsd news via anon ftp
Keywords: news archive 386bsd australia
Organization: Australian Defence Force Academy, Canberra, Australia
Date: Fri, 2 Oct 1992 04:28:29 GMT

A quick reminder that minnie.cs.adfa.oz.au has archives of the news in
comp.unix.bsd in the /bsdnews directory. It also has a cache of 386BSD
binaries, so ftp'ing from minnie will take some load from kirk.bu.oz.au.
Here's the archive readme:

---
Welcome to the 386BSD news archive in minnie. This contains the Usenet news
articles from comp.unix.bsd since just before 386BSD 0.1. If the 386BSD
newsgroup changes, the archive here will track the change.

The archive is kept as a set of MS-DOS ZIP files, each containing 100 news
articles. For example, 3400.zip contains articles 3400 to 3499. Requests to
change the format of the archive will fall on deaf ears.

Other files in this directory give the subject lines for the articles. For
example, subject.300 holds the subject lines for files 3000 to 3999. These
subject files are ordered by subject, not by article number. I have edited
out those articles related to the USL/BSDI suit etc. etc.

Updates to the archive will probably be done on a weekly basis. Disk space
is currently tight, so expect to see files disappear on a FIFO or LRU basis.

	Warren Toomey	wkt@csadfa.cs.adfa.oz.au
---


Newsgroups: comp.unix.bsd
From: Granville.Moore@purplet.demon.co.uk (Granville Moore)
Subject: 386BSD: problems with Del
Organization: FidoNet node 2:252/305.0 - The Purple Tentacle, Reading
Date: Wed, 30 Sep 1992 15:24:00 +0000

On 22 Sep 1992, You said to All:

JM>   Dell 450SE, 486 50Mhz, EISA, 24 Meg RAM
JM>   Adaptec 1742 SCSI controller
JM>   WD 8013W 10baseT ethernet

JM>   when i boot the Fixit disk (with debug stuff) i get:

JM>   [ lots of what looks like disk sector debugging ]
JM>   [ 0.1 headers ]
JM>   pc0<color> ...
JM>   com1 ...
JM>   com2 ...
JM>   fd0 ...
JM>   as0 ...
JM>   we0 ...
JM> npx0 at 0xf0 irq 13 on isa (???)
JM>   changing root device to fd0a

JM>   it then hangs, or at least appears to do nothing.

JM>   any ideas?

I get exactly the same results with a Texas Instruments 1300 (386/dx) system.
Currently with MDA (ugh!, but itwas a terminal server...), just about to
upgrade to VGA.

Likewise,  any ideas?

I would greatly appreciate copies of any suggestions that are e-mailed to you,
or suggestions from anyone else reading this.

Despite what may appear in the header to this posting, my e-mail address is:
      gvm@Nemesys.demon.co.uk

Regards

Granville


  PQ-Under-Trial 2.15  Everyone lies, butit doesn't matter, since nobody listens
From: linkt@GroupW.cns.vt.edu (Tim Link)
Newsgroups: comp.unix.bsd
Subject: bootp server for 386BSD
Date: 30 Sep 92 15:57:53 GMT
Organization: Va Tech Communications Resources

I have a bootp server running now.  If anyone is interested in trying it
out let me know.  There's a very slight hack in it I'd like to get rid
of before ftp-ing it to agate for general consumption.

I sent a couple of posts related to the SIOCGIFCONF and OSIOCGIFCONF
ioctl functions for sockets but got no replies.  I'll ask one more time
if *ANYBODY* out there can show me the details of the structures these 2
functions return.  On other systems they seem to be synonymous, but on
386BSD they definitely are not, and the "non-O" version seems to return
garbage (compared to what I *think* it should be returning.).

Anyway, if you want to try out the bootp server send me mail at
linkt@groupw.cns.vt.edu

Thanks... Tim
From: toreh@bootes.sds.no (Tore Haraldsen)
Newsgroups: comp.unix.bsd
Subject: Xfree & Paradise VGA Plus card
Keywords: (or:  Don't be stupid like me :-)
Date: 30 Sep 92 21:52:55 GMT
Organization: Statens Datasentral A/S, SDS, Norway

.. is it possible to run Xfree/X386 on a Paradise VGA Plus? Under DOS it
supports up to 800x600. What would the Xconfig file look like?

-- tore
Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: Catch What They're Saying About Us...
Organization: Xenix Support, FICC
Date: Mon, 28 Sep 1992 20:53:18 GMT

Oh no, not again...
-- 
Peter da Silva                                               `-_-'
Ferranti Intl. Ctls. Corp.                                    'U` 
Sugar Land, TX  77487-5012
+1 713 274 5180                                   Har du kramat din varg idag?
Xref: sparky comp.unix.bsd:6389 comp.unix.sysv386:14972
From: johng@informix.com (John Galloway)
Newsgroups: comp.unix.bsd,comp.unix.sysv386
Subject: Is there an FAQ for 386bsd?
Date: 26 Sep 92 09:38:48 GMT
Distribution: ca
Organization: Galloway Research
Originator: johng@godzilla


    Supported hw, hw to avoid, common pitfalls, where too get it, what
    are the basic features (DOS windows, NFS, X...etc.) i.e. the guide
    book for the unix hacker thinking about getting a 386/486 box.
    thanks.
	-jrg

-- 
internet    jrg@galloway.sj.ca.us  John R. Galloway, Jr  795 Beaver Creek Way
applelink   D3413                  CEO...receptionist    San Jose, CA   95133
                                   Galloway Research     (408) 259-2490
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: 386BSD's non-standard C library
Organization: tu-chemnitz
Date: Mon, 5 Oct 1992 17:54:29 GMT

Well Terry,

i agree with most of your statements. But, with respect to ANSI, my thoughts
are some different.
K&R has not been declared to be a standard. There have been many changes
since early K&R to the latest pre-ANSI compilers and libraries. (Have a
look at the various configuration dependencies contained within the GNU
packages.) That's the reason, only an ANSI compiler defines ``__STDC__''
which implies that this is _the_ standard.

Of cource, when writing code for a variety of systems, this should imply
the possibility of compiling it on a K&R compiler, whatever one could
understand for this term. Possibly, there should be #ifdefs whenever
needed or appropriate. For example, the toupper() could be defined
like
  #ifndef __STDC__
  #define toupper(c) (islower(c)? _toupper(c): c)
  #endif
or similiarly.

But when compiling for any modern environment (all *-Dos compilers,
and 386BSD with its gcc, for example) i prefer writing (almost) strict
ANSI code, i. e. my gcc won't warn anything when compiling with -Wall
(except the sccsid:-). There are security reasons: the prototypes will
show typos and other errors in an early stage of compilation, some
better defined implicit type conversions make live easier. Rather than
linting _and_ compiling, everything is done in one step (and thus faster
since there's only _one_ parsing of input). And believe, gcc -Wall warns
a lot (maybe more than lint? - e.g. forgotten arguments in a printf list?).
But - this is applicable only when the destination of my program is some
system i'm sure about there's an ANSI compiler. When programming for
386BSD, this is always true.

	vy 73!
	J"org (ham call: y43tl)

--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: 386BSD and IDE drives
Organization: Chinet - Public Access UNIX
Date: Tue, 29 Sep 1992 13:05:22 GMT

In article <id.O7NT.0O3@ferranti.com> peter@ferranti.com (peter da silva) writes:
>In article <Bv32LD.K9t@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>> 	Something is very wrong here.  My experience is that IDE drives
>> 	are great for UNIX and IDEAL for 386bsd.  Main reason is that, like
>> 	SCSI, they hide bad sectors from the OS.
>
>This is the one problem with SCSI, and presumably IDE. Why? What happens
>when you have a marginal disk? 
>I've been burned by this.
>
	Well, in actual use, I have found modern IDE/SCSI drives to be
	much more reliable than MFM/RLL/ESDI drives.  Newer technology,
	etc.  I back up regularly (ha!), and a sudden onslaught of bad 
	sectors would be no worse than any other catastrophic failure.
	I mean, just look at all the poor people complaining of the
	distribution having bad parts because they get errors when
	unpacking it.  They are using MFM/RLL/ESDI drives that the
	OS is not aware or reporting bad sectors.  This don't happen
	with IDE/SCSI.
>
>>       Never a need to run bad144 or worry about bad sectors.
>
>Oh, you should worry. Trust me.
>
	With IDE/SCSI?  Please elaborate.

>Not unless you really compromise on the quality of the drives, or unless
>you've got some sort of special deal. Street prices vary by $20-$50 for
>the same drive in SCSI and IDE versions.

	Seems with top of the line drives, (>300 meg < 18ms seek), SCSI
	drives are a few hundred more than the same IDE.  This is
	non-negligable when a SCSI controller runs a couple hundred
	and a IDE is basicaly free.  
	Again, this is all supposing no need for over 2 devices.

-- 
	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
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: Re: 386BSD Questions
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sat, 3 Oct 92 15:07:47 GMT


I'm also wondering about this ongoing discussion on "16MB limit on the ISA bus".
Recently I had a 486/33 motherboard which could be populated with 32 MB of
4MB SIMMs. 

Is 386bsd bound to a 16MB limit? I cannot believe that.

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: How to format UNIX floppies under 386BSD
Date: 1 Oct 1992 21:35:48 -0500
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu

In <1992Sep29.165042.1@vax.sonoma.edu> levinson@vax.sonoma.edu writes:

>> MS-DOS always
>> want's to reformat the entire disk in these cases.  mformat will do the
>> job in about 5-10 seconds.

>well, there is format /q in MSDOS which just overwrites the root directory.

Try that with a disk that's been stomped on with rawwrite or tar from
386BSD.  Since the format command can't figure out what format the
disk is in it figures that it *has* to format the entire disk,
regardless of what you tell it.  You are just a dumb user and of
course, it knows better.

++Brett;
From: rwa@aupair.cs.athabascau.ca (Ross Alexander)
Newsgroups: comp.unix.bsd
Subject: Re: new new scsi release beta2 part 1 of 5 (fixed)SKIP
Date: 30 Sep 92 20:37:48 GMT
Article-I.D.: aupair.rwa.717885468

terry@cs.weber.edu (A Wizard of Earth C) writes:

>Currently, the command line configuration tools are abominable.  I shouldn't
>have to edit my file (hoping I have the right one) to change an IRQ or add
>pty's, config it, change directories (making sure I get the one named the
>same as my file), make depend, make, and then manually install the resulting
>executable, remembering to delete the devices which are no longer applicable
>to my new configuration, and adding the ones which are but did not exist
>prior to the most recent rebuild.

<yawn, another newbie...>

If you can't handle it, admit you're an incompetent and stay out of
the kitchen.  You might change your silly mail address too; a wizard
indeed!  Real wizards don't so much as imagine that the simple list of
trivial steps you mention are worth spending time on, much less
kvetching about.

Just run the GENERIC kernel, and leave the hacking to your betters.

Ross
--
Ross Alexander  rwa@cs.athabascau.ca  (403) 675 6311  ve6pdq@ve6mgs.ampr.org
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Newsgroups: comp.unix.bsd
Subject: Re: Moving ethernet card from IRQ2 to IRQ5 in 386BSD
Keywords: Ethernet card, IRQ, 386BSD
Date: 2 Oct 92 20:06:16 GMT
Organization: tu-chemnitz

u8011841@cc.nctu.edu.tw () writes:

>...
>   My quesion is: When I moved the NE2000 ethernet card from IRQ 2 to IRQ 5,
>the kernel can still detect the presence of the card but report

>   ne0 ethernet address 00:.... at 0x300 irq 9 on isa 
>                                         ^^^^^
Thats a problem of ISA bus, refer to Bills article in DDJ. The driver
is unable to detect the real IRQ and thus assumes IRQ being set as
configured in the systems file.

>   In fact, the FAQ mentioned that "Ken Raeburn report that simply rebuilding
>the kernel from supplied sources will get rid of it".
Yes, that it is. You MUST reconfigure and rebuild your kernel.

>But we prefered our
>486 work for DOS & 386BSD.  And IRQ set to 2 will halt the computer when run
>the clarkson packet driver.  It seems that VGA adapter use IRQ 2 too.
I didn't get any problems on irq 2 with the packet drivers. Most VGA
cards allow to disable their interrupt generation. It's only an old
compatibity hack to have it (EGA), but as far as i know this int is very
useless (occurs during vertical retrace).
>   So, How do I tell the kernel that the ethernet card had been moved from
>the default IRQ 2 to IRQ 5? Can somebody kindly to give me some help?
As mentioned above, _reconfigure_ your kernel, then rebuild - everything
will be nice.

	J"org

> 
>   Thanks in advance

>Shun-Jee Liu 
>liu@cmibm4.nctu.edu.tw
--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Mixing SCSI with other HD controllers...
Organization: Weber State University  (Ogden, UT)
Distribution: comp.unix.bsd
Date: Mon, 5 Oct 92 19:56:01 GMT

In article <1992Oct5.183056.20169@news.nd.edu> jim@stargate.helios.nd.edu (Jim McCusker) writes:
>One last question, I tried to restore my SCSI drive to a DOS partition using
>MS-DOS 5.0's FDISK and then formatting.  After format completes formating
>I am given the message that it could not write the boot area.  How do I 
>get around this????

DOS 5.0?  You are in luck (or as in luck as you are going to get while
still running DOS on a perfectly good hard drive. 8-).).

The FDISK from 5.0 DOS has a magic undocumented option.  Type:

	FDISK /M

To rewrite the master boot record with stuff DOS likes.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: alan@ulka.zso.dec.com (F. Alan Jones)
Newsgroups: comp.unix.bsd
Subject: Re: How to format UNIX floppies under 386BSD
Date: 5 Oct 92 15:33:15 GMT
Article-I.D.: ninja.1992Oct5.153315.22272
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation


What we really need is public domain lower level format code.  If
someone can give me a pointer, I'll look into porting it.  I only
have a copy of DOS 3.3, and I'll spend several weekends on this 
project before I spend a dime on DOS.  Religious reasons.

Alan
From: U45923@uicvm.uic.edu (Arnatt Klinsong)
Newsgroups: comp.unix.bsd
Subject: Help: mtools - How do I get instruction?
Date: 27 Sep 92 17:42:53 GMT
Article-I.D.: uicvm.92271.124253U45923
Organization: University of Illinois at Chicago

When I try typing 'man cmd' cmd - some command in mtools, I don't get the manua
l. I try executing it without any parameter, but there isn't much help their. O
viously I need detail help on mtools. Is there a file explaining mtools some wh
ere on the net. I really need to put my backup files on to my flopy disk. I sur
e there is a simple command parameter that I over look. ANY HELP WILL BE GREATL
Y APPRICIATED..Thank a head of time..Arnatt   U45923@uicvm.uic.edu

.
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: XFree86 gives me a blank screen !
Keywords: X Xfree86 install
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Thu, 1 Oct 1992 06:49:18 GMT

In article <BvEp22.24@news.cso.uiuc.edu> venkat@uxh.cso.uiuc.edu (Venkat Swaminathan) writes:
>Hi folks,
>
>I downloaded the XFree86 binaries from agate:/pub/incoming/X386 and have been
>[unsuccessfully] trying to install XFree86. After I type 'sh startx' or 
>'xinit' there is a 3-4 second pause and then the message "Waiting for X
>server to begin accepting connections" followed by a number of periods - two
>to a line. After a minute or two the screen just blanks and nothing short of a
>reboot will get the screen back. The keyboard is apparently working because
>of the disk activity pattern when I type a command etc.  I have spent hours
>on trying out different values in the Xconfig file to no avail. I am using the
>kernel binary from agate:/pub/incoming/X386/386bsd.kernel... whatever.
>
>DETAILS:
>	386/25 MHz machine with 4MB RAM/125MB HD; Diamond Speedstar VGA video
>	card with 1MB video RAM; MAG PMV 1448 monitor; Microsoft compatible
>	mouse on com1.
>
>Any help will be appreciated either by email or USENET. Thanks !
>
>Venkat
>
Preferably, from a terminal other than the console, try
the following in the directory where you have your X386 server:

csh
./X386 >& foo

if your screen does not come back, type sync a couple of times
and reboot.

Look at thfile foo.  also please check for a core dump.
last but not least your card may not be
supported. It may be one of those sparkling new models out of
Diamond with a clock synthetizer. If it does have a clock synthetizer,
I suggest that you take it back, because we can't program 
Diamond's propieratory clock synthetizer.

God I hate answering questions concerning Diamond equipment.
To make matters worse I have a Diamond SpeedStar which I
tried to dump but I can't.

Cheers,
Amancio





Newsgroups: comp.unix.bsd
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: Mounting NFS volumes
Organization: University of Michigan ITD Consulting and Support Services
Date: Tue, 29 Sep 1992 20:58:39 GMT

So I am attempting to mount an NFS volume over local ethernet to my
machine.  I issue this (as root):

mount -t nfs -o intr,rsize=1024,wsize=1024 <hostname>:/<path> /mnt

And it always returns: Device not supported.  Well there is no
explicit NFS device, is there?  Why is it saying this?

I issue showmount -e <hostname> and it tells me that the volume is
exported and ready to mount for anyone.

Paul Southworth                    |     ftp redspread.css.itd.umich.edu
Consulting and Support Services    |        Anonymous Political Archives
Information Technology Division    |                     100% 386BSD 0.1
University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org

  <Representing myself.  Everything I say is for educational use only.>
From: hlu@video.eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: ecvt(), where's the source?
Date: 4 Oct 92 20:35:07 GMT
Article-I.D.: serval.1992Oct4.203507.24975
Organization: Washington State University

In article <k3i4RB1w165w@tsoft.sf-bay.org>, bbs.barfeau@tsoft.sf-bay.org (David Fox) writes:
|> Hello, I'm compiling a program that wants to use ecvt() and there's
|> no function for that in 386BSD.  Does anyone have this?
|> 
|> --
|> David Fox (bbs.barfeau@tsoft.sf-bay.org)

Try the Linux C library. If you need a library function which is not in 386bsd,
there is a good chance you can find it in Linux.

If you find something which is better than or missing in Linux, please let me
know.

Thanks.

H.J.
--
hlu@eecs.wsu.edu
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: X386 (vga unknown ioctl) 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sat, 3 Oct 92 18:30:03 GMT


I installed X386-1.02E from agate (pub/incoming) today and found the following
'quirks' (It's great, but does not yet work for me):

The README is talking about 1.0.3 but what I got from incoming/X386 is 1.0.2E.

The path does not seem to get installed. I'm not a csh user, but what I saw
was that /etc/csh.login is patched but logging out and in again did not change my path (user root).

I applied all patches. All but one worked OK. 2 hunks for com.c failed. I was
using com.cgd. The two hunks that failed refered to the two occurences of 
minor-1 (cgd's code had a minor-1, the patch wanted minor). I repaired that by hand in com.c

After editing a Xconfig file I started X386 by "startx". I was running my kernel
at that time and got /dev/vga illegal ioctl (or unknown or something like that).
I looked in /dev/vga and found it at 12 0. I'm suspecting that the ioctl
that the server attempted refers to the 'new kernel extensions' that are under
work. Switching to the generic kernel ended up in reject 65531 messages a lot
signalling to me that this kernel is of no use to me due to the different network configuration I have .

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: merce@xenitec.on.ca (Jim Mercer)
Subject: Re: new new scsi release beta2 part 1 of 5 (fixed)
Organization: XeniTec Consulting, Kitchener, Ontario, CANADA
Date: Tue, 29 Sep 1992 17:58:54 GMT

In article <1992Sep23.221352.16254@tfs.com> julian@tfs.com (Julian Elischer) writes:
>This release of the new scsi system has been considerably neatenned up
>as far as the definitions of scsi arguments go.
>also supports cdrom.

if anyone builds a kernel with this, i would appreciate a copy.

-- 
[ Jim Mercer   Reptilian Research  merce@iguana.reptiles.org  +1 519 893-6085 ]
[             I don't want to work for a company that has a CIO.              ]
[              Disclaimer! I don't need no stinking Disclaimer!               ]
Newsgroups: comp.unix.bsd