HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Could the passwd/crypt changes be included in the patch kit?
Organization: Weber State University  (Ogden, UT)
Distribution: usa
Date: Mon, 5 Oct 92 16:29:20 GMT

In article <1992Oct5.141005.16849@rwwa.COM> witr@rwwa.com writes:
>I was wondering if the passwd/crypt changes could be included in the patch
>kit in a way that does not violate the goofy export restrictions (assuming
>that they still apply, which I am told is not the case).  Perhaps a stub
>module could be used or something, or an *imported* version of the crypt
>code?

Binaries could be if whoever made the patches got an export license and
tracked who they were given to.  The export license part of this is
easy; you just have to agree to do the second part, in writing.

The whole point of DES not being exported is US "National Interest".  This
thinking is obsolete... not because the US doesn't have a right to protecting
what it sees as it's National Interest, but because DES is already out of
the bag already.

The National Interest basis is also being eroded (and in fact may not
even be applicable any more) because DES is so easily ammenable to
cracking using massive parallelism and the other techniques in the
(several months back) Bell Systems Technical Journal.  The fluidic
modelling computer built for NASA Goddard Space Flight Research by
Goodyear can crack DES or trapdoor encrypted data in 1/64,000th of the
time (the number of processors it has).

Anyone who owns a small consulting business (hint, hint, Robert 8-)) want
to se what it would take to get an export license today?  The rules might
have changed since "the end of the cold war", which is the last time I
checked on exporting DES sources.


					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: jonas@sisu.se (Jonas Lagerblad)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problems with new boot code (HELP!)
Summary: boot scsi PC-problems
Date: 6 Oct 92 10:41:10 GMT
Organization: Swedish Institute of Systems Development

Hello all happy 386-bsd users!

I am a previously very content user of 386BSD, but since last night I can't
boot my computer anymore (except from the fixit floppy).

The scenario is like this:

I have a 50Mhz 486DX Brand X (16Mb), an adaptec 1542B, A Seagate Wren7 (1.0Gb)
on which I have been running 386BSD for the last month. The disk is partitioned
with one 200Mb DOS5 partition and one 800Mb BSD partition, and I use the
boot selection code posted quite recently by someone from Berlin (Thomas XXX).

Most things have been
working reasonably well, but yesterday I decided to test Julian Elischer's
new scsi driver. I installed all patches needed in the kernel code, 
configured a new kernel with sd0 configured as boot and swap device, everything
was fine until I tried to boot the new kernel and got an error message
from the boot code that the kernel was to big, using 386bsd.alt.

At this point I decided to install the new boot code. I compiled it without any
problems, installed it with:
disklabel -r -w sd0 wren7 scsitst /usr/mdec/sdboot /usr/mdec/bootsd

and after copying my /etc/disktab to the FIXIT floppy I rebooted, and
got no response at all from the new boot code. The boot selection still
works and I can boot DOS (but who wants to run DOS?), but when selecting 
Unix nothing happens, and I have to do a reset of the computer (Ctrl_Alt_Del 
doesn't work).

At this point I thought OK, there is some bug in the new boot code, lets
reinstall the old code, I booted the fixit floppy, checked my file
systems and reinstalled asboot and bootas with the same command as above (s/sd/as).
Tried to reboot, but still no response from any unix boot code..

My disk layout is (approximately) like this:

offset	size(kb)	Usage
0	200000		DOS5 partition (with boot select code)
200000	700000		/dev/sd0a
900000	100000		swap (/dev/sd0b)
200000	800000		/dev/sd0c
0	1000000		/dev/sd0d

Does anyone have any idea of what to do to get my disk bootable again,
I have considered removing the DOS partition and installing Unix on that
partition too, to avoid the problems with bootselect (can that be the cause
of this?), but there ought to be some simpler method.

Regards Jonas Lagerblad
-- 
Jonas Lagerblad
Phone Office: +46-31-830250 Home: +46-31-205955 Car: +46-10-2846031
FAX:	+46-31-831047
email:	jonas@sisu.se
From: berry@max.IN-Berlin.DE (Stefan Behrens)
Newsgroups: comp.unix.bsd
Subject: [386bsd] locked IDE-HD-controller
Date: 5 Oct 1992 23:40:52 +0100
Organization: A poorly-installed InterNetNews site
NNTP-Posting-Host: max.in-berlin.de

When I heavilly load my system, or when I use UUCP over a 2400 bps
line and my daily run wants to do its job meanwhile, or when I simply
do too much things at the same time (with iScreen) my two IDE
harddisks get locked (or the controler or the system?).
The LED for my IDE-controller is burning and I can go on working until
the update daemon tries to synchronize. Until then every process that
needs disk-IO blocks for ever.
I have got an i38[67] running at 33Mhz, 32KB cache, 8 MB of ram, one
IDE controller with an 177 MB and a 245 MB IDE drive (all for 386bsd),
an unused printer (every patch I tried caused a reboot) and a modem
connected to a 16550AFN UART card.
It is the fifth UNIX version I am working with but it is the first
multitasking system that gets locked when I actually do multitasking!!!
Anyway, I love it. I can write my programms (I save and sync very
often) and I can get mails (sendmail with my own sendmail.cf for an
UUCP-link) and news (InterNetNews).
-- 
Stefan (berry@max.IN-Berlin.DE)
From: stripes@pix.com (Josh Osborne)
Subject: Re: How long AT-buss DMA transfers can be done to "user memory"?
Organization: Pix Technologies -- The company with no adult supervision
Distribution: comp
Date: Thu, 1 Oct 1992 12:55:56 GMT

In article <OLOF.92Sep28202046@ikaros.fysik4.kth.se> olof@ikaros.fysik4.kth.se (Olof Franksson) writes:
[...]
>The DMA hardware limit is 64k, but on my system it seems to be 20k (21k or
>more makes the system reboot). Is this as it should, a bug, or due to
>erroneous use of the kernel routines?

When an ISA system does block mode DMA RAM refresh is normally not done.  So
if your system needs refreshes more offen then normal, or does them less
offen then normal (which makes missing any worse), or the device you are
DMAing/ to/from is slower then normal, or a combonation of the above then 
the ammount _you_ can DMA without later getting parity errors (which are
offen wired to reboot, or at least cause an NMI) is going to
be less then 64K.
[....]
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
>	isa_dmastart(readflag, bp->b_un.b_addr, bp->b_bcount, channel);
>		.
>	/* Wait for end of transfer */
>		.
>	isa_dmadone(readflag, bp->b_un.b_addr, bp->b_bcount, channel);
>
>Since AT-buss DMA is restricted to 64k of continous, non 64k block address 
>breaking, one problem might be that the isa_dma*() routines dont check
>for these things. Another restriction might be that the routines are
>unable to lock more than a certain amount of address space in continous
>physical memory.
>
>I am not so familiar with kernel physical/virtual memory management
>and would like to avoid these topics at length. My experience mostly 
>concerns writing device drivers for SUN and XENIX, not BSD derivatives. 
>
>	Sincerely
>
>		Olof Franksson
>		Physics IV, KTH, Sweden
>		+46 8 790 7219 


Newsgroups: comp.unix.bsd
From: ejh@slustl.slu.edu (Eric J. Haug)
Subject: 386BSD gethostbyname change
Organization: St. Louis Univ.
Date: Mon, 5 Oct 1992 12:52:37 GMT

I became tired of not being able to boot 386bsd and mount the two
NFS partitions because the ethernet bridge was down, or the name server
was not up to date, so i changed the way hostname lookup fails.
Any comments?
eric
In the file gethostnamadr.c in src/lib/libc/net at around line 281
#if	0	/* get rid of this, in favor of ...   ejh@slustl.slu.edu */
		if (errno == ECONNREFUSED)
			return (_gethtbyname(name));
		else
			return ((struct hostent *) NULL);
#else
			/* always check the local host table */
		return (_gethtbyname(name));
#endif
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: Gateway 486, Wangtek 5150 & Sun tape drive, KCL
Date: 4 Oct 92 21:02:55 GMT
Organization: St. Peter's College, US

In article <CMM.0.90.2.718183986.lim@cs.columbia.edu>, lim@cs.columbia.edu (Jong Gyun Lim) writes:

[Note- my comments apply to the hardware and to BSDI's BSD/386 product. You
 should see similar results with 386BSD, though]

> 1. if I buy the tape drive, I should also buy the Adaptec 1542B (~$250),
>    Right?  ($349+$250= almost $600.  ugh...)

  Right. You'll need a supported SCSI controller. At the moment, that's the
Adaptec 1542B.

> 2. Since Wangtek 5150 is QIC-150 standard, does this mean that I can read
>    the tar files written by the Sun QIC-150 tape drive?
>    If so, I could probably justify my $600 because then I could use it as
>    a safe way of transferring large files between the two machines.

  Yes. I have interchanged tar tapes between my Sun 3/60 (SunOS 4.1.1, Wang-
tek 5150ES), my MS-DOS PC (MS-DOS 5.0, Wangtek 5150ES, Andreas Kaiser's GTAK),
and my BSDI system (BSDI gamma, Wangtek 5150ES) without any problems.

> 3. Do you see any problem using IDE HD and SCSI tape drive together?
>    I could upgrade the 340mb IDE HD to 340mb SCSI HD for about $210...

  No problems, although you do have a second controller generating heat, etc.
The 1542B uses different I/O ports from the IDE controller. On my BSDI system
I ran a 210Mb IDE, 760Mb SCSI, and the tape all at the same time.

  Your budget and possible growth plans should be considered when thinking
about converting the IDE to SCSI. Is the IDE controller on the motherboard
or on an expansion card?

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: Re: problem,ith compiling kernel
Organization: Supercomputing Research Center (Bowie, MD)
Date: Mon, 5 Oct 1992 15:02:20 GMT

In article <vgdp57q+@aix01.rz.fht-mannheim.de> u84167@aix01.rz.fht-mannheim.de ( ) writes:
>he (the computer) did his compiling work and then he said:
>loding 386bsd
>init_main.o undefined symbole _version reference from text segment

Gee, i have seen this so many times, and the fix is so easy, if you don't 
mind temporary kludgery. 

I didn't feel like messing around and getting it right, as it looked like
the patch kit would do the job, so did a *very* temporary work-around. 

Go ahead and use ci -l on init_main.c if you do this ...
and praise all the Good Guys who put rcs into 0.1 

In init_main.c, i added the line: 
char version[] = "This is a version string";

YEEECCCHHH, right? but i got a kernel ... and again this is done in the 
knowledge that it is TEMPORARY. 

make sure that your string is at least 10 bytes, as somewhere below
a printf references version[9]. 

Sorry if this makes too many of you feel ill. :-)
ron
-- 
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      | rminnich@super.org
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      | (301)-805-7451
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      |
From: erich@hri.com (Eric Hilfer)
Newsgroups: comp.unix.bsd
Subject: Re: Motif for 386BSD
Keywords: Motif 386BSD
Date: 28 Sep 92 18:51:38 GMT
Originator: erich@rodan

I'm afraid I lost track of this thread, but I am still interested.
Did someone say that they had built Motif on 386BSD?  I have just tried building
Motif 1.2, and after a little fooling around it compiled without errors
or missing symbols.  BUT, the mwm manager and most of the demos crash at random
locations!  Those that run can only make Simple XmStrings, any compound string
comes out garbled.  The Motif release notes say that internationalization must be
present in the X11R5 build and in the C library.  I assumed that this would be OK
with 386bsd0.1 and the binary distribution of X386 from pub/incoming/X386 in
agate.berkeley.edu.  Am I wrong?  Has anyone else tried Motif 1.2?

Thanks,

Eric
-- 
----------------
Eric Hilfer
erich@hri.com
From: knie2586@csd4.csd.uwm.edu (Robert Joseph Knier)
Newsgroups: comp.unix.bsd
Subject: 2 RLL drives and 386BSD
Date: 29 Sep 1992 23:41:39 GMT
Organization: Computing Services Division, University of Wisconsin - Milwaukee
NNTP-Posting-Host: 129.89.7.4

Subject: 2 RLL drives and 386BSD
Summary: 
Expires: 
Followup-To: 
Distribution: usa
Organization: Computing Services Division, University of Wisconsin - Milwaukee
Keywords: 


All,

	I just finished applying the patches for the 386BSD system from
Terry Lambert (Thanks Terry !!!!!).  I have a slight problem.  When applying
patch number 00021 (to add multiple hard drives to the system) the kernel
panics on boot up.  The message said 'cannot mount root'.  I am currently
running only 1 of the 2 65Mb hard drives that are on the system.  (soon
as I can get the kernel updated I will add the second).  Would anyone
have any ideas?  My configuration is as follows:


Northgate 20Mhz 386DX system
 2 RLL hard drives (65Mb each)
 2 5 1/4 FDDs
 a 2400 baud modem

 4 Mb of memory (w/coprocessor)
 I am using the standard GENERICISA configuration when building the kernal




 Thanks

 Robert Knier
 (knie2586@csd4.uwm.edu)
From: jim@quantime.co.uk (James Chapman)
Newsgroups: comp.unix.bsd
Subject: lp.c problems (with fix)
Date: 6 Oct 92 17:21:27 GMT
Organization: Quantime Ltd, London


Found that this made the lp driver work on our machine
(a 33Mhz Gateway 386)  which suffered loss of characters
with files >1K.  However, not sure why this fixes it...

jim


*** lp.orig.c   Tue Oct  6 18:09:04 1992
--- lp.c        Tue Oct  6 17:53:00 1992
***************
*** 377,389 ****
        struct lpctrl *lpc = &lp_ctrl[unit];
        int port = lpc->port;
        char val;
  
        /*
        ** check for spurious interrupt
        */
  
!       if (!(lpc->flags & LPF_BUSY))
                return;
  
        /*
        ** any more to print
--- 377,394 ----
        struct lpctrl *lpc = &lp_ctrl[unit];
        int port = lpc->port;
        char val;
+       int s;
  
+       s=splhigh();
+ 
        /*
        ** check for spurious interrupt
        */
  
!       if (!(lpc->flags & LPF_BUSY)) {
!               splx(s);
                return;
+       }
  
        /*
        ** any more to print
***************
*** 394,401 ****
                {
                val = inb(lpc->port + LPR_STAT);
  
!               if ((val & LPS_BUSY) == 0)
                        return;
  
                /*
                ** output the character
--- 399,408 ----
                {
                val = inb(lpc->port + LPR_STAT);
  
!               if ((val & LPS_BUSY) == 0) {
!                       splx(s);
                        return;
+               }
  
                /*
                ** output the character
***************
*** 425,430 ****
--- 432,438 ----
                LPDELAY(1);
                }
  
+       splx(s);
        lpiodone(lpc);
        }
  
Newsgroups: comp.unix.bsd
From: nils@merlin.ims.uni-stuttgart.de (Cornelis van der Laan)
Subject: Re: How to get parallel printer to work ?
Reply-To: nils@ims.uni-stuttgart.de
Organization: IMS, University of Stuttgart, Germany
Date: Sat, 3 Oct 1992 17:27:02 GMT

>>>>> On 1 Oct 92 18:08:12 GMT, gpw10@phoenixcd.amdahl.com (Gary Ward) said:

Gary> I also have a HP DeskJet 500.  This printer expects <CR><LF> at the
Gary> end of each line.  I provided a simple output filter to add the needed
Gary> <CR> characters and it would then print text fine.  Unfortunately
Gary> doing this screws up graphics printing.  I therefore invented another
Gary> logical printer which does not filter and dump all my graphics to it.

There's no problem if you set the Deskjet into the mode where it
automagically expands <LF> to <LF><CR>. Do this with the following
printcap:

#
# Setup for HP Deskjet 500:
#
# tr= Eject page at end of all jobs
# mx= Maximum size of job (0 = no limit)
# sh= no header page
# fo= send 'form-feed' when opening device
# ff= the 'form feed': Reset printer, CR=>CR, LF=CR+LF, FF=CR+FF
# tr= (eject page at end of printing ?)
#
jet|rjet|lp|"Deskjet 500":\
	:lp=/dev/lp1:\
	:sd=/usr/spool/lpd/jet:lf=/usr/adm/lpd.errs:af=/usr/adm/lpr-prints:\
	:mx#0:tr=\033&l0H:fo:ff=\033E\033&k2G:sh:

As graphics data contain a reset sequence you can just print all your 
files without fiddling with strange in/outfilters.

--Nils.

Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: fax software for 386bsd?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 5 Oct 1992 08:17:20 GMT

mark@student.business.uwo.ca (Mark Bramwell CS STAFF) writes:

>My modem is a fax capable modem.
Which modem are you using ?

>Under dos/windows, I can use WinFaxPro to send and receive faxes.  I am
> am not interested in receiving faxes, just sending them.
With the software mentioned below you can send and receive faxes.
Although all received faxes will end up in one directory. That might
be a problem if you plan to use a real multi-user environment.
This is what I gathered from the README file.

>Is there any fax software for unix based machines?  text or X11?
Yes. It is under the GNU project.
Its name is
	fax-3.2.1.tar.Z
This is a spooling system. I didn't take a look at it but it seems to be
written for BSD systems. So it should not be too difficult to port it.
Somebody in Munich, Germany did it, but, unfortunately I lost his
e-mail address.
I have the patches for a Supra FAXModem (but not tried those, yet).

Oh yes, if you don't want to change all the Makefiles you should port
GNU-make (make-3.62.tar.Z), first.

Hope this helps,

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
Newsgroups: comp.unix.bsd
From: ggr@koonda.acci.com.au (Greg Rose)
Subject: Newbies (Was Re: new new scsi release beta2 part 1 of 5)
Organization: Australian Computing and Communications Institute
Date: Thu, 1 Oct 1992 23:17:31 GMT

In article <1992Oct1.182115.14256@fcom.cc.utah.edu> terry@icarus.weber.edu writes:
>In article <rwa.717885468@aupair.cs.athabascau.ca> rwa@aupair.cs.athabascau.ca (Ross Alexander) writes:
>><yawn, another newbie...>
>
>I love it when I try to start a discussion about "how to make something
>require less effort" and get accused of being a "newbie" ...usually by
>someone who just got done spending 90 hours figuring out how do do what
>I want simplified and thinks they know everything now.

This reminds me of the time on comp.arch when someone accused
dmr@research.att.com <Dennis Ritchie> of making a false statement
about the beginnings of C. Boy, was he ever flamed. It stopped
abruptly when Dennis apologised for his misstatement.

I've been mucking around with kernel configurations for way too long
already, and agree with Terry that there are many possible improvements.
However, like both Ross and Terry, I assert I know how to do it.

By the way, Ross, I object to your use of the term "newbie" as an
epithet. "Intolerant", now there's an epithet... :-)

--
Greg Rose                 Australian Computing and Communications Institute
ggr@acci.com.au                                              +61 3 282 2532
"If you ever do that again, I'll cut you out of my will!"
		    -- Captain Ross to Co-pilot Gann, "Fate is the Hunter"
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: adaptec 1740-42a SCSI controller won't boot?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Fri, 2 Oct 1992 10:50:10 GMT

jrb@ichips.intel.com (James Binkley) writes:

>In trying to boot dist.fs on an Intel 403e with
>a adaptec AHA-1740A/1742A controller, I get
>the following fatal error messages from the
>hard disk driver:

>as0 at 0x330 irq 11 drq 5 on isa
>...
>as0b: controller error 0x12 reading fsbn 0
>scsi sense: 0 0 0 0 0 0....
>as0b: controller error 0x12 reading fsbn 0
>scsi sense: 0 0 0 0 0 0....
That's the same result I got a few weeks, ago.
I thought that I had ordered a reasonable system :-)

>In other words, gave up on block 0. I presume
>the above device is actually as0d since as0b
>doesn't exist and install install fails the same way, 
>except the device is as0d?  Any suggestions as
>to why the driver is failing?
No. I don't have any idea. However, read on:

You definitely need the latest SCSI drivers from Julian Elischer
(julian@tfs.COM) and his new boot blocks.
I have used those and, suddenly, I could boot my harddisk
yesterday !
It is important that you use the new "bios" boot blocks made by him, too.
Otherwise, you can just install but not boot from your harddisk !

Oh yes, I did forget to tell you that this only works, if the
Adaptec 1742A (or whatever) is configured for "standard mode", i.e.
1542B emulation mode. Don't be afraid, you won't loose the 33MB/s
DMA data rate on the EISA bus using this mode !
And, of course, the default configuration must not be changed, i.e.
port 0x330, irq 11, drq 5. But this is shown on your message above and it
seems to be right.

You should perhaps try and go back in your newsreader to get the
driver sources and the new boot-block (also sources).

>Any help appreciated. Thanks.
Hope it helps.

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
Newsgroups: comp.unix.bsd
Date: Sun, 4 Oct 92 3:33:06 EDT
From: Jong Gyun Lim <lim@cs.columbia.edu>
Subject: Gateway 486, Wangtek 5150 & Sun tape drive, KCL

Hi,

I want to be able to:

	run KCL (Kyoto Common Lisp)
	under 386bsd
	with X

I already ordered the following setup from Gateway,

	486DX/66MHz
	8 MB Ram
	ATI Ultra Pro VGA card 
	340mb IDE

Then I learned from comp.unix.bsd that someone is selling the Wangtek 5150ES
at a bargain price, so I am thinking that I might as well get that, too.


Now the questions:

1. if I buy the tape drive, I should also buy the Adaptec 1542B (~$250),
   Right?  ($349+$250= almost $600.  ugh...)

2. Since Wangtek 5150 is QIC-150 standard, does this mean that I can read
   the tar files written by the Sun QIC-150 tape drive?
   If so, I could probably justify my $600 because then I could use it as
   a safe way of transferring large files between the two machines.
	
3. Do you see any problem using IDE HD and SCSI tape drive together?
   I could upgrade the 340mb IDE HD to 340mb SCSI HD for about $210...

4. Does 386bsd support ATI card?  In particular the Gateway version of the
   ATI Ultra Pro VGA card for local bus...

5. Did anyone manage to use KCL under 386bsd?



Sorry for asking so many questions at once, but I need the answers quick
so that if there is a need for major change in spec, then I better make the
call to Gateway before they make the shipment (well, they are slow, but who
knows.)


Actually, while I am at it, I might as well ask another question :)

6. Does 386bsd support HP LaserJet IIIP (w/ Postscript cartridge) ?
   Or is this a dumb question?



Thank you all you experts!



	Jong "Wanna See My 486 Beat SPARC 2" Lim