HDTenEightyP/NetNews huggingface dataset:
From: bde@runx.oz.au (Bruce Evans)
Subject: Re: 386BSD - Bug in UFS file system + proposed fix
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Mon, 21 Dec 92 08:19:43 GMT

In article <1992Dec16.211422.3663@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <1992Dec16.012248.8123@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
>>[ I posted this once, but I'm reasonably sure it didn't make it out ]
>>
>>There is a major bug in the 386BSD UFS code relating to file permissions.
>>The major symptom is:
>>
>>   Can't read most files that you don't own on a remote NFS 386BSD system,
>>   although there is public read permission, i.e.:
>>
>>-r--r--r--   1 root     other          5 Dec 15 19:15 /tmp/hell
>>
>>A very minor symptom is you can't read some LOCAL files, although
>>there is public read permission, i.e. a file that looks like:
>>
>>-------r--   1 root     other          5 Dec 15 19:15 /tmp/hell
>>
>>[ This functionality seems broken on SunOS 4.1 too, but not on USL S5R4. ]
>
>[ ... fix deleted ... ]
>
>This fix seems a bad thing.  In particular, you *don't* want to allow a
>file which is world read or world execute to be read/executed by someone
>who is a member of a group denied access.

I think the fix is correct.  It seems to be the same patch that I posted
the other day, but is backwards.

Fix undeleted:
---
*** sys.386bsd/ufs/ufs_vnops.c.orig	Tue Dec 15 19:07:09 1992
--- sys.386bsd/ufs/ufs_vnops.c	Tue Dec 15 19:06:55 1992
***************
*** 201,207 ****
  found:
  		;
  	}
! 	if ((ip->i_mode & mode) == mode)
  		return (0);
  	$eturn (EACCES);
  }
--- 201,207 ----
  found:
  		;
  	}
! 	if ((ip->i_mode & mode) != 0)
  		return (0);
  	return (EACCES);
  }
---
What is going on here?  I think that the version in the ".orig" file is
correct, but the version in the "new" file is what's already in 386BSD-0.1,
and wrong.  The patch is for access().  access() is supposed to check that
all the bits (if any) are accessible (== mode) and not that at least one
of the bits is accessible (!= 0).

Checking all the modes should give more security unless access() is misused
(are there any correct uses for access()? :-).
-- 
Bruce Evans  (bde@runx.oz.au)
Newsgroups: comp.unix.bsd
From: gisie@wam.umd.edu (Satan)
Subject: Re: ET4000/W32 and VESA VL-Bus
Organization: University of Maryland, College Park
Date: Mon, 28 Dec 1992 20:20:50 GMT

Can someone post the diffs/specs/etc on the various S3 chips?
ie - 801/805/911 what ever... the ones out now and the ones right
around the corner..

tia,
	tim

-- 
gisie@wam.umd.edu
"How will these windows affect my final document?"
Newsgroups: comp.unix.bsd
From: gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy)
Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
Organization: University of Virginia
Date: Thu, 31 Dec 1992 23:24:12 GMT

In article <1hvu79INNjqq@ftp.UU.NET> sef@Kithrup.COM (Sean Eric Fagan) writes:
#GNU malloc is copylefted.  Using it in a library means that every program
#compiled using that library is copylefted.  That is almost certainly the
#reason why it is not used, and I cannot fault anyone for that.

Well, this would mean that programs would have to be distributed under
the less restrictive GLPL instead of the GPL, but I still bet many
people won't like this restriction. People would be required to ship a
linkable executable, but would not be forced to release source code.




--
-Greg Hennessy, University of Virginia
 USPS Mail:     Astronomy Department, Charlottesville, VA 22903-2475 USA
 Internet:      gsh7w@virginia.edu  
 UUCP:		...!uunet!virginia!gsh7w
From: dpassage@soda.berkeley.edu (David G. Paschich)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Anyone got it working on an IBM PS/2 40SX?
Date: 31 Dec 1992 01:35:58 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu


I'm trying to get 386BSD working on an IBM PS/2 Model 40 SX.  Before I
get half a dozen letters, this machine _does_ have an AT bus, not that
MicroChannel thing.  Anyway, it's a 386SX 16 Mhz with 6 megs of
RAM, a 3.5" floppy, and a 80 meg IDE disk.

I got myself a copy of the boot floppy (agate:/pub/386BSD/386bsd-0.1/bootables)
and booted.  The boot banner appeared, and it found the com port
display, and floppy drive, but not the hard drive.  It got to the
# prompt, and then locked up real good.  ctl-alt-del didn't work;
had to reboot.

Anyway, help would be appreciated.  

David Paschich

-- 
David G. Paschich	Comp Sci Undergrad Association		UC Berkeley
dpassage@soda.berkeley.edu			  dpassage@ana-ng.chaos.org
"We will create a new political climate where the system does not
attract ego-driven, power-hungry people." -- Ross Perot
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Distribution: comp
Date: Fri, 1 Jan 1993 20:03:19 GMT

In article <1993Jan1.102032.8413@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
>>I say we petition Bill to use GNU malloc in preference.  Most folks aren't
>>going to know enough (or dare) to replace malloc in libc themselves, but
>>they will notice the very painful state of affairs that trying to work
>>in a low memory environment brings; why not spare them the pain?
>
>If we are going to vote, I vote for one of the PD malloc implementations
>as opposed to the GNU copyleft implementation.  There are many reasons,
>some stated by Lynne and Bill, for keeping 386BSD salable without sources;
>GNU copyleft ruins this.
>
>
>					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
>-------------------------------------------------------------------------------

If anyone can point me to a good PD malloc which can help me for X stuff, I 
will appreciated it :-)

	Happy New Year,
	Amancio Hasty
-- 
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Newsgroups: comp.unix.bsd
Subject: [386bsd] New Year patch for CMOS clock, was still 92 year
Date: Fri, 01 Jan 93 12:28:37 +0300
Distribution: world
Organization: Ha-oh-lahm Yetzirah
Reply-To: ache@astral.msk.su

Hi,
I look today at my computer and see, that still 92 year now active :-(
Here is a patch to fix it (I was mathematician and remember,
that (y % 4) operation need whole year instead of (y - 1970),
moreover (y % 4) determinition of leap year is wrong,
see #define isleap() below for correct implementation).
This patch fix another small problem too, old code add 9x additional
seconds in any case: (sec += ytos(sec) instead of sec = ytos(sec))

P.S.: Happy New Year!

*** clock.c.was	Sun Nov 22 02:52:30 1992
--- clock.c	Fri Jan  1 12:17:04 1993
***************
*** 58,63 ****
--- 58,65 ----
  #define DAYST 119
  #define DAYEN 303
  
+ #define isleap(y) (((y) % 4) == 0 && ((y) % 100) != 0 || ((y) % 400) == 0)
+ 
  startrtclock() {
  	int s;
  
***************
*** 94,102 ****
  	int i;
  	unsigned long ret;
  
! 	ret = 0; y = y - 70;
! 	for(i=0;i<y;i++) {
! 		if (i % 4) ret += 365*24*60*60;
  		else ret += 366*24*60*60;
  	}
  	return ret;
--- 96,104 ----
  	int i;
  	unsigned long ret;
  
! 	ret = 0;
! 	for(i=1970;i<y;i++) {
! 		if (!isleap(i)) ret += 365*24*60*60;
  		else ret += 366*24*60*60;
  	}
  	return ret;
***************
*** 145,152 ****
  	while ((sa&RTCSA_TUP) == RTCSA_TUP)
  		sa = rtcin(RTC_STATUSA);
  
! 	sec = bcd(rtcin(RTC_YEAR));
! 	leap = !(sec % 4); sec += ytos(sec); /* year    */
  	yd = mtos(bcd(rtcin(RTC_MONTH)),leap); sec += yd;	/* month   */
  	t = (bcd(rtcin(RTC_DAY))-1) * 24*60*60; sec += t; yd += t; /* date    */
  	day_week = rtcin(RTC_WDAY);				/* day     */
--- 147,154 ----
  	while ((sa&RTCSA_TUP) == RTCSA_TUP)
  		sa = rtcin(RTC_STATUSA);
  
! 	t = bcd(rtcin(RTC_YEAR)) + 1900;
! 	leap = isleap(t); sec = ytos(t); /* year    */
  	yd = mtos(bcd(rtcin(RTC_MONTH)),leap); sec += yd;	/* month   */
  	t = (bcd(rtcin(RTC_DAY))-1) * 24*60*60; sec += t; yd += t; /* date    */
  	day_week = rtcin(RTC_WDAY);				/* day     */
***************
*** 153,159 ****
  	sec += bcd(rtcin(RTC_HRS)) * 60*60;			/* hour    */
  	sec += bcd(rtcin(RTC_MIN)) * 60;			/* minutes */
  	sec += bcd(rtcin(RTC_SEC));				/* seconds */
- 	sec -= 24*60*60; /* XXX why ??? */
  
  	/* XXX off by one? Need to calculate DST on SUNDAY */
  	/* Perhaps we should have the RTC hold GMT time to save */
--- 155,160 ----
-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
Organization:  The RELCOM Corp.,    |  "Brujuleada entre los lejos
               Moscow, Russia       |  "De lo imposible?!"  (Calderon)
From: aoki@risk.stanford.edu (ikuro aoki)
Newsgroups: comp.unix.bsd
Subject: my new kernel does't boot. does anyone have similar problem?
Date: 3 Jan 93 03:51:40
Organization: Stanford University, Stanford, CA, USA.
Distribution: comp
NNTP-Posting-Host: risk.stanford.edu

Hello all,

I made a new kernel with gcc2.3.3. However, it doesn't boot up 
properly, but continue endless rebooting. 
Does anyone have similar problem? Did you solve this already?

I parched the source code tree with diffs from Mr.Van Der Linden
(vdlinden@fwi.uva.nl). I made gcc2.3.3 with some minor amending.
However, the compilation was very straightforward, doesn't have 
big hitch. This gcc2.3.3 could compile other programs (ex: X11
clients) correctly. I checked it.

I also tried to compile the same kernel source tree with the 
original 'cc' (= gcc1.39). It works fine. No boot problem.

Should I have to re-compile bootblocks (sd) with gcc2.3.3 ?

Any response will be welcome.
Thank you.
--
Ikuro
aoki@risk.Stanford.EDU
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: IBM--What does it mean? (was: Reading joystick)
Organization: University of Utah Computer Center
Date: Mon, 28 Dec 92 05:26:34 GMT

In article <1hj0nqINNlgq@charnel.ecst.csuchico.edu>, fish@ecst.csuchico.edu (Kevin Haddock) writes:
|> One of my favorites is in a .sig from our news administrator:
|> 
|> "IBM, You BM, we all BM for IBM!"

That's actually from the book "When Harlie was one" by David Gerold.  There
is a rewrite of the book for updated technology (I think it's called "When
Harlie was one v2.0"); the updated version, if memory serves me, omits this.


					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: peterson@notredame.ac.jp (Greg Peterson)
Newsgroups: comp.unix.bsd
Subject: 386bsd - reinstall woes
Date: 26 Dec 92 15:45:02 GMT
Organization: Notre Dame Women's College, Kyoto, Japan.

I have 386bsd-0.1 running on one SCSI hard disk, and I want to
transfer it to a larger one (Maxtor XT-8760S).

I began to install the system on the new disk (the whole disk), but
the install program was interrupted. When I restarted "Tiny 386bsd"
and ran install again, it reported that it was installed, then asked
if I wanted to reinstall the system.  When I answered 'y', it went
into a loop, repeating the same message.

I have tried several ways of getting out of this loop: 

  - FDISK and FORMAT in MS-DOS (FAT is messed up)
  - Boot from the old hard disk, mount the new one (kmem error)
  - cp the necessary files to the hard disk (file permissions became 644)

None of these worked. When I try to boot from the hard disk, 386bsd
starts up, looking for a kernel.  That's as far as it gets.

Does anyone have a suggestion?  Ideally, I would like to put a small
MS-DOS partition on the disk (in hindsight), but I would be happy with
386bsd-only as well.

Is there a version of the install program that doesn't go into an
endless loop when you try to reinstall?  Or, lacking that, is there a
way to get the original install program to reinstall the system?

Thanks, and Merry Christmas from Japan.

--
Greg Peterson - peterson@notredame.ac.jp
Notre Dame Women's College, Kyoto, JAPAN (Phone: +81 75 781-1173)
Home: Phone: +81 775 53-8614  Fax: +81 775 52-7768
Newsgroups: comp.unix.bsd
From: sitongia@ozzel.hao.ucar.edu (HAO Computer System Managment Group)
Subject: [386bsd] Anyone have driver for Colorado Memory Systems tape?
Reply-To: sitongia@ozzel.hao.ucar.edu (HAO Computer System Managment Group)
Organization: High Altitude Observatory/NCAR, Boulder CO
Distribution: usa
Date: Tue, 22 Dec 1992 03:46:27 GMT

Does anyone have a driver for the CMS Jumbo QIC-40 (120Mb) tape drive?  Is
anyone working on such?

Thanks for your time.
--
--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
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: Can this scsi combination work under 386bsd?
Organization: TRW Financial Systems
Date: Sun, 27 Dec 1992 22:42:44 GMT

In article <1992Dec23.170441.6708@netcom.com> shawr@netcom.com (rich shaw) writes:
>Hi,
>	I have a rather strange setup. I have a adaptec 1542B with scsi ID
>at 7 and a hard drive with scsi ID 6. My question is can this setup work
>under 386bsd? If not, is there any way to make it work? 

386bsd will have no problems with this with the new drivers..
(the old drivers can also handle it but the device for the disk 
would be as6, so you'd have to change the swap and root definitions.)
The hard bit will be convincing the BIOS on the aha1542 that 
it should boot of ID6. (it won't do it)
If you are booting of another disk, you should be able to reach
the drive as sd0 on the new scsi system or as6 on the old one.

>
>-- rich
>-- shawr@netcom.com

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v



Newsgroups: comp.unix.bsd
From: gtoal@pizzabox.demon.co.uk (Graham Toal)
Subject: Re: Where are tar files of bsd net-2 tapes?
Organization: Cuddlehogs Anonymous
Date: Sat, 2 Jan 1993 16:15:44 GMT

In article <1993Jan1.200415.10908@spectrum.xerox.com> leisner@eso.mc.xerox.com writes:
:All the archives I've seen of the BSD  net-2 tapes are lots and lots of 
:compressed files (i.e. on ftp.uu.net).
:
:Where is everything in a few tar files (like the X11 distribution...)

I don't know, but doesn't uunet's ftp server let you fetch whole
directories as tar files just by saying get dirname.tar ? (don't ask for
dirname.tar.Z if the files are already compressed - save yourself some
redundant cpu time)

G
Newsgroups: comp.unix.bsd
From: gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart)
Subject: Re: [386bsd] looking for logitech bms driver 
Organization: Technische Universitaet Muenchen, Germany
Date: Thu, 31 Dec 1992 15:54:14 GMT

In article <1992Dec31.083055.27555@rdg.dec.com> migi@furka.enet.dec.com writes:
>
>I'm looking for the logitech busmouse driver for 386bsd. I've read
>in an article, that it should be in agate, but I can't find it there.
>
You get obtain it from ftp.informatik.tu-muenchen.de in
/pub/BSD/386BSD/0.1/unofficial/drivers/mouse/logitech

Ralf

From: reink@hpuamsa.neth.hp.com (Reinier Kleipool)
Date: Thu, 24 Dec 1992 15:31:04 GMT
Subject: Re: 386bsd HELP laptop back to DOS 5.0 H/Disk prob
Organization: HP-Sales Office-The Netherlands
Newsgroups: comp.unix.bsd

Hello,


   I have had this same sweat on my face as well when i wanted to return
my borrowed HD back to its owner.

  BUT if you use MSDOS 5.0's fdisk /mbr to restore the original
msdos maser boot record msdos should work ok!


Reinier Kleipool.



  /\
-(  )-/##---------------------------------------------------------------------
  }{/   ##    One has to look out  -- Overschie ------------------------------
.====.        for engineers- they  -- Reinier Kleipool  ----------------------
| [] |   begin with sewing machi-  -- Mail -----------------------------------
|    |   nes and  end up with the  -- X400: C=nl A=400net P=hp O=hp S=Kleipool
|    |   atomic bomb.....          -- desk: Reinier Kleipool/ hpitcb/75     --
| [] |              Marcel Pagnol  -- unix: reink@hpuamsa.neth.hp.com        --
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd,comp.unix.programmer
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] need motif
Keywords: motif 386bsd
Date: 21 Dec 92 12:46:13 GMT
Organization: Applied Math, University of Bonn, Germany

In article <1gnqtaINNenu@hpsdlss3.sdd.hp.com> mattb@sdd.hp.com (Matt Bonner) writes:
>In article <1274@zogwarg.etl.army.mil>, mike@zogwarg.etl.army.mil (Mike McDonnell) writes:
>|> I need to buy motif to rehost some code under 386bsd.  Someone please
>|> tell me about a distributor here in the US.  Prices too if possible.

Don't know about the US, but see below.

>The basic answer is that since I don't think anyone is selling Motif
>binaries for 386bsd (can anyone correct me on this?)

Sure! :-)

Send email to:

Enrico Badella                          Internet: softstar@pol88a.to.cnr.it
Soft*Star s.r.l.                                  eb@icnucevx.cnuce.cnr.it
Via Camburzano 9
10143 Torino                            Phone:    +39-11-746092
ITALY                                   Fax:      +39-11-746487


He sells Motif binaries for 386bsd.  The only reason to charge for it is the
licensing fee that must be paid to the OSF for every copy of a binary Motif
distribution.

-- Volker
-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
Newsgroups: comp.unix.bsd
From: asu@server2.panther.mot.com (Russell Trotter)
Subject: [386BSD] 'tip' and 'su' problems
Organization: Motorola Panther Project, Chandler, AZ
Date: Mon, 21 Dec 1992 16:11:40 GMT

Hello,

  I just recently installed 386bsd for the first time.  I also
installed all 58 patches (except #47) of Lambert's patchkit.  I
also read his FAQ.  I get the usual "all ports busy" message when
I try to run tip.  The FAQ said just recompile and that
should fix it.  Well, after recompiling it (even with the patchkit,
rebuilt kernel and utils) and I still get the same message.  Also,
when I log in as a normal user (non-root) then 'su' (to become
root), my machine hangs, and I am forced to reboot.  Any suggestions
to my newbian questions would be greatly appreciated.  Thanks!

Russ

asu@panther.mot.com
From: blymn@awadi.com.au (Brett Lymn)
Newsgroups: comp.unix.bsd
Subject: Re: Minor XFree86 problems, long function key string bug in elvis
Date: 2 Jan 93 17:18:36
Organization: /usr/blymn/.organization
Distribution: "world"
	<1992Dec30.232628.7555@citec.oz.au>
NNTP-Posting-Host: siren.awadi.com.au
In-reply-to: sgccseh@citec.oz.au's message of Wed, 30 Dec 1992 23:26:28 GMT

>>>>> On Wed, 30 Dec 1992 23:26:28 GMT, sgccseh@citec.oz.au (Steve Hocking) said:

Steve> randy@chinet.chi.il.us (Randy Suess) writes:

>In article <1992Dec30.005909.15079@tackle.uucp> jc@tackle.uucp (John Capo) writes:
>>I have XFree86 running and only have a few problems left to solve.
>>Another thing I have noticed is that my machine is on its knees when
>>I am compiling and running X at the same time.  
>>    No name 386/33, 8M RAM, 128K cache.

>	I have found that 8 megs memory is enough to bring X up with
>	an xterm and that is about it without swapping.  Putting
>	another 4 megs of ram in helps a lot and 16 megs makes it
>	the fastest x86 based X system I have seen.
>	This is not bad, as my sysvr4 system will barely run all
>	by itself with 8 megs, and even with 16 megs, it swaps all
>	over the place with X.
[stuff deleted]
>Randy Suess					 randy@chinet.chi.il.us

Steve> 	I'm quite comfortably running SVR4 on an 8Mb machine with XFree86.
Steve> Usually I have 3 xterms, a clock and a few other bits & pieces running, plus
Steve> the occasional large compile using gcc. It works fine, although gcc will
Steve> elbow out a few things when compiling C++ programs with all the optimisation
Steve> bells. It's quite tolerable, even on a 25MHz 386sx (with 32k cache). BTW the
Steve> Unix is Dell 2.2 with all the uneccessary drivers pulled (RFS, all ethernet
Steve> except WD, some graphics boards). I run NFS, slip, IP, all the stuff X needs
Steve> and the SCSI drivers (I have a Wren 6 drive + BusTek/BusLogic controller -
Steve> fast). 16Mb would be heaps.

Yes you are about on the limit of memory considering what you are
doing.  I bet that if you tried doing something like having your
xterms and a copy of emacs and gdb and *then* compiling that you will
find that you will be doing quite a bit of swapping.  It seems like
8Megs is adequate if you do the occaisional compile and hacking about
but if you get into intensive compile/crash/edit cycles you soon find
the memory is limited.  I never regretted upgrading to 16Meg ;-)

--
Brett Lymn
From: antony@werple.apana.org.au (Antony Suter)
Newsgroups: comp.unix.bsd
Subject: Re: S3 question - Amancio, are you there?
Date: 29 Dec 1992 15:13:29 +1100
Organization: werple public-access unix, Melbourne
NNTP-Posting-Host: werple.apana.org.au

mike@starburst.umd.edu (Michael F. Santangelo) writes:

>we just aren't sure.  Unfortunately the only email address listed
>for the author is on BIX ("rick_g").

I believe that translates to:-

	rick_g@bytep.byte.com

Newsgroups: comp.unix.bsd
From: glenc@netcom.com (Glen Collins)
Subject: [386bsd] Install
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Mon, 28 Dec 1992 00:44:53 GMT

Hello!

	Well I just went out and purchased a 486sx/25 board today and
the install installed!!!!!! Yes, final, but I do still wonder if the
problem maybe with the AMD 386DX chip. COuld it be? Anyone???? It will
be interesting to debug 386bsd on that now since I will have a working
machine I can compile the kernal with. Thanks for all who helped
or tried to at least. I will let you know what I come up with and maybe
I will be able to fix the problem so others won't have the same, eh?

-Glen Collins
	(glenc@netcom.com)

Newsgroups: comp.unix.bsd
From: abs@sunvax.sun.ac.za
Subject: [386BSD] Help needed getting Laserjet II+ to work with 386BSD.
Organization: University of Stellenbosch
Date: Wed, 23 Dec 1992 22:19:12 GMT

Howdy folks!

I have been running 386BSD for a few months now, and have decided to
connect a HP Laserjet II+ to the box. I am on a net, so there hasn't really
been a need for a printer on the box, but now I want it.

I successfully installed the lp patches, and the port is seen.
But when I print, the port or printer seem to just hang. The form feed
light on the laser comes on, but that is all. Nothing else happens.
lpc reports the status as printing, but thats it. If I cat directly to 
/dev/lp ( set up as c 14 0) the same happens.

Can anyone please help me ?

Oh, yes I am using Terry's lp patch. Haug's lpt patch would not work.

Regards

Andre.

abs@cs.sun.ac.za.
Newsgroups: comp.unix.bsd