HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.unix.bsd
Subject: 123 bytes too big bin01.56 - how to fix?
From: ryanph@mrl.dsto.gov.au
Date: 28 Jan 93 10:08:25 +1100
Organization: Defence Science and Technology Organisation

I successfully downloaded the tinyBSD disk image file. I installed a 50 Meg 
386bsd partition on my hard disk. I got the distribution files bin01.00 
to bin01.56. I began 'extract bin01'.

It checked the files and choked on the last one only: bin01.56.

This last file is the only one which is not 240640 bytes long, instead, it is
227717 bytes long. My Vax/VMS system's ftp, or else Kermit to the PC, has a 512
byte minimum size, so that when I get the last file on the PC, it is 227840
bytes long.

Naturally, the extraction program chokes because the file no longer passes a
CRC test, despite the fact that there is nothing missing from it.

Does anyone know how to rid this file of the excess 123 bytes?

Alternatively, is there any way I can 'package' the file (in a tar archive or a
zip file) so that I could unpackage it properly in MS-Dos?

Thanks for your help in advance.


Phil Ryan
Melbourne
From: vepaepck@cip.informatik.uni-erlangen.de (Volker Paepcke)
Newsgroups: comp.unix.bsd
Subject: [386BSD] problems with QIC-02 streamer driver
Date: Wed, 27 Jan 1993 22:53:06 GMT
Organization: CSD., University of Erlangen
NNTP-Posting-Host: faui00a.informatik.uni-erlangen.de

hi!

I've some problems with the specification of the correct blocksize
for accessing the streamertape (wangtek qic-02). 
With 512 byte blocks and 1kb blocks there is no problem.
But at greater blocksizes I got anly part of the stuff back
after restoring from tape (there is no error reporting from tar
or from the kernel!!!).
It seems to me, that there is only a small blocksize for tape-access
allowed, but there is another problem:
With small blocksizes the tapestreamer is repositioning all the time
while IO-operations wich is not very good for the tapes and very very
slow!
I saw a buffering capability in the BSDI/386 rewritten code of the
wt.c driver stuff. Is there something similar like buffering or
any patches for improvement on this subject which is running under
386bsd too?
Buying a SCSI-streamer device is no solution for me, since i don't
have the money right now. Any help is apreciated!
thanks in advance,

volker

oh, i forgot:
Can i write tapemarks and is there a mt-command?
From: hg926cy@unidui.uni-duisburg.de (Cyrus)
Newsgroups: comp.unix.bsd
Subject: [386bsd] sockets: permission denied??
Date: 28 Jan 1993 13:45:44 +0100
Organization: Universitaet Duisburg GH
NNTP-Posting-Host: unidui.uni-duisburg.de
Summary: question apout 386bsd and sockets
Keywords: help sockets

Every time I start the cnews "newsrun" I get the message:
rcvd: sockets: permission denied
Can anyone help me to solve this problem.

regards, Ulrich
-- 
----------------------------------------------------------------------
Ulrich Cyrus				hg926cy@unidui.uni-duisburg.de
Fliederstr. 169
D-4100 Duisburg 1			
Germany
Newsgroups: comp.unix.bsd
From: randyd@tfs.com (Randy Daniels)
Subject: [386BSD] disklabel for wd1
Organization: TRW Financial Systems
Date: Mon, 25 Jan 1993 04:14:39 GMT



		Anyone have the scoop on using 2 ide drives?
			2 Seagate ST3144A drives
			1 Ultrastor 15C Controller

	The system is up to patch level 19 and a new kernel has been
	compiled with wd1@wd0.  The problem we're having is that when
	you try to access wd1 the system hangs.  It apperently does one
	operation to the drive then hangs.  Ran disklabel and after the hang
	rebooted (fixit floppy) with only wd1 hooked up as wd0 and it did
	write the disklabel.  Any ideas or pointers?
	Any disk access at all to wd1 will hang the system.
From: gene@stark.uucp (Gene Stark)
Newsgroups: comp.unix.bsd
Subject: Beware patch00061
Date: 26 Jan 93 08:48:00
Organization: Gene Stark's home system
Distribution: world
NNTP-Posting-Host: stark.uucp

In the new patchkit-0.2 just released, people should be aware that patch00061
makes an incompatible change to the interface of functions having to do with
select(2), including "selwakeup".  The change is that (pid_t)'s, rather than
(struct proc *)'s, are now required to identify the process to be awakened.
Patch00061 makes the changes to all the code present in the base system, but
anyone who is using other drivers that support select will have to apply
appropriate changes.  These drivers include Rick Macklem's 386 bus mouse
driver and my "tw" X-10 driver.  Chris Demetriou's "com-beta" driver already
uses the new interface, so if you are trying to get it to work without having
applied patch00061 you should give it up and get the patchkit.

In the next two postings, I include patches for Rick Macklem's busmouse
driver, and for my X-10 driver.

							- Gene Stark
From: scott@pita.cns.ucla.edu (Scott Burris)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] What ist the state of XS3 ?
Keywords: 386BSD, XS3
Date: 28 Jan 93 00:01:42 GMT

kehr@rs3.hrz.th-darmstadt.de (Roger Kehr) writes:


>I'm  looking for a new graphics system (graphics card and
>monitor) for my new 386BSD-system. I heard something about 
>an X-Server for S3-cards i'm very interested in.

>My questions on this topic are :

>- how stable ist XS3 for 386BSD ?

I've been using XS3 for a few months now with an STB WIND/X board
(911 based with Logitech mouse).  I've had no problem.  Things are stable
enough that I never run in anything but an X11 environment anymore.

>- what about the performance relative to a ET4000 card (e.g.
>  Diamond Speedstar+ )

The S3's should put the ET4000's to shame.

>- Are there more newsgroups I could ask ?

This is the place.

>I need a stable system and can't afford to make too much 
>experiments with X. 

>Is it better to choose a fast ET4000 than a S3 ?

Not in my opinion.
-- 
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu
Newsgroups: comp.unix.bsd
From: rooij@mozart.cft.philips.nl (G. van Rooij)
Subject: Re: [386BSD] Quotas, maxusers, & sendmail
Keywords: 386bsd, quota, maxusers, sendmail
Organization: Philips Communications & Processing Services, Eindhoven
Date: Tue, 26 Jan 1993 09:06:45 GMT

Also have enough pty's?

-Guido
From: captain@rot.qc.ca (Andrew Webster)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] boot disk does absolutely nothing on gateway 4dx33v
Date: 29 Jan 93 03:59:55 GMT
Organization: Groupe de Recherche Operationnelle en Telecommunication (ROT) Inc.
X-Newsreader: TIN [version 1.1 PL8]

A Wizard of Earth C (terry@cs.weber.edu) wrote:
> In article <1jkdpeINNkeg@cat.cis.Brown.EDU> tim@news.Brown.EDU (Timothy Miller) writes:
> >I have acquired the boot disk image for 386bsd, and no matter what I try,
> >when my system starts up, it displays all the bios messages, and then hangs
[stuff deleted]...

> This is the "Compaq boot problem".  You can get the patch from the file
> ~/terry/patch.bootblock.fdboot.c on ref.tfs.com, download a Compaq
> dist.fs or fixit,fs, or go to a news archive and get the article
> "Message-ID: <1992Dec08.132820.29435@crash>".

> The problem is insidious, and it's a wonder anyone can boot at all; from
> the referenced article:

> ] Also, Akihiro Higashi, in article
> ] <1992Sep11.051554.29192@mlab.nttdocomo.co.jp>, reported that he
> ] had to change 3rd & 4th "NOP"s to "JMP .+2"s on his COMPAQ 486/50L.
> ] 'NOP' is a delay macro which alters the AL register.  The specific
> ] ange 3rd & 4th "NOP"s to "JMP .+2"s on his COMPAQ 486/50L.
> ] 'NOP' is a delay macro which alters the AL register.  The specific
> ] instances mentioned involve code resetting the DMA controller's first/last
> ] flip-flop and then programming the DMA controller's mode register.
> ] The initialization byte for the mode register is clobbered by a NOP
> ] (I am amazed that the boot works on most systems!).  This can be fixed
> ] by rearranging the code slightly.

> And for brave, brave souls:

> ] Fortunately, these changes do not shift the boot code, so a binary patch
> ] is possible.  The changes to the first sector on the disk (fixit.fs or
> ] dist.fs) are given below:
> ] 
> ] Offset    Old    New
> ] ------    ----   ----
> ] 0x00e1    0x07   0xbf
> ] 0x00f2    0xb0   0xee
> ] 0x00f3    0x46   0xe4
> ] 0x00f4    0xee   0x84
> ] 0x00f5    0xe4   0x4a
> ] 0x00f6    0x84   0xb0
> ] 0x00f7    0x4a   0x46

> I believe the pattern "b0 46 ee e4 84 4a" would exist even on altered boot
> disks, since this portion of the boot would be unchanged, even if not at
> the same offset.  Work back by -15 (decimal) to fix the e1 offset value.

> Using either a binary patch or Compaq boot disks should alleviate the
> need to have a working system to build a disk to have a working system...


I tried the binary patch, and lo-and behold it boots!
Thanks!

-------------------------------------------------------------------------------
captain@broue.rot.qc.ca	| Andrew Webster	|  "The engines canna take it 
			|			|  anymore cap'n..."
IP: 192.77.49.131	| ROT inc.		 ------------------------------
			| Recherche Operationnelle en Telecommunication
			|
Voice: +1 514 737 0020	| Dataradio Inc.
Fax:   +1 514 737 7883	| Montreal, Quebec
-------------------------------------------------------------------------------
From: julian@tfs.com (Julian Elischer)
Subject: Re: please help with SCSI tape and 386BSD!
Organization: TRW Financial Systems, Berkeley, CA - 94704
Date: Mon, 25 Jan 1993 05:57:19 GMT

In article <727806169rommel.root@jonas.gold.sub.org> rommel@jonas.gold.sub.org (Kai Uwe Rommel) writes:
>In article <727481242rommel.root@jonas.gold.sub.org> rommel@jonas.gold.sub.org (Kai Uwe Rommel) writes:
>>I have a SCSI tape drive (Tandberg 4120) and want to read 386BSD from
>>it after installing the boot disk, which worked fine. I can prepare a
>>tape with 386BSD under OS/2 but cannot read it under 386BSD. In fact,
>>386BSD cannot read *anything* from the tape.
>>
[deleted]
>>
>>However, when I try to access the tape (even with cat, not only with
>>tar), it streams a bit and when using "tar tv" I see one line with the
>>contents of the first record (correct, BTW) and then I only get the
>>message "length error". What is wrong here and what can I do?

The record length handling code is broken in the 
present scsi tape driver, due to the accidental incusion of a 
well meaning but wrong patch.

I am nearly ready to release a 'fixed' version, but I'm going to need
guinea-pigs, as I have only variable record length drives to check
it on.

>>
>Update: I have today tried a HP 35470A DAT drive and to my surprise it
>works. It is a SCSI-2 device like the Tandberg streamer but unlike the
>Tandberg it works fine. I suspect that they respond a bit differently
>to SCSI commands. 
>
>Does anyone know the fix for 386BSD to get the Tandberg working? BTW,
>both the Tandberg and the HP DAT work fine under OS/2, so it's not a
>fault in the hardware.

hopefully the answer may be on the way.
8-)

>
>Kai Uwe Rommel

julian
+----------------------------------+       ______ _  __
|   __--_|\  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
From: hlu@eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] gcc2 and -fPIC
Date: 26 Jan 93 21:04:30 GMT
Article-I.D.: serval.1993Jan26.210430.27806
Organization: School of EECS, Washington State University

In article <CGD.93Jan25211237@eden.CS.Berkeley.EDU>, cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
|> anybody gotten code compiled w/gcc2's -fPIC to assemble properly
|> (or "at all") under 386bsd?
|> 
|> if so, could you tell me what i'm doing wrong?
|> 
|> gcc -c -fPIC -O foo.c
|> just won't do it for me... 8-)
|> 

That is because as on bsd doesn't support PIC yet. That leads to another
question. I believe a.out format is not very good for PIC even with some
patches. Personally, I prefer ELF. The problem is gnu binutils 2.x and
gas do not fully support ELF. I was wondering if anyone has done something
on ELF?

 
H.J.
Newsgroups: comp.unix.bsd
From: lpc@dickens.com (Luis P Caamano)
Subject: Re: Problem to transfer large data via socket communication - Need Help
Date: Mon, 25 Jan 1993 19:33:06 GMT
Organization: Dickens Data Systems, Inc.

In article <1829@igd.fhg.de> mike@igd.fhg.de (Mike Sokolewizc (Gast)) writes:
>>  we develope a program with socket communication. We have large
>>  datas to transfer. So we use the following routines
>>  to send data from socket to socket (stream):
>>
>>        write(socket,(char*)data,buffer)
>>        read(socket,(char*)data,buffer)
>>
>>  But now we've problems sending/receiving large data for
>>  example 50*50*50 matrix of floats or larger. Is there any
>>     Oliver
>
>the system gives you only exactly what's waiting at that socket at that instant, even if more
>data is coming.  Therefore, you have to nest the read() within a loop and keep reading until
>you get an error or the expected number of bytes:
>
>  num_read = 0;
>  do
>    {
>      l = read( socket, &buffer[num_read], BUF_SIZE - num_read );
>      num_read += l;
>    }
>  while ( (num_read < BUF_SIZE) && (l > 0) );
>

Same thing applies for write() over a socket descriptor.

-- 
Luis P. Caamano                        |         lpc@dickens.com
Dickens Data Systems, Inc. Atlanta, GA |         uunet!dickens.com!lpc
---------------------------------------------------------------------------
If I think I know it all, I'll stop learning. -myself
The more I learn, the more I know I know nothing. -somebody else
Newsgroups: comp.unix.bsd
From: galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN)
Subject: Re: reading from parallel port
Organization: University of Colorado, Boulder
Date: Tue, 26 Jan 1993 02:54:55 GMT

In article <C1ADIM.1s3@sleeper.apana.org.au> raz@sleeper.apana.org.au (Roland Turner) writes:
>bs@Germany.EU.net (Bernard Steiner) writes:
>
>>Folks,
>>I just read through one of those terrible x86 magazines. Somebody advertized
>>their LPT port ethernet[TM] adapter.
>
>>While I believe that the idea of driving the ethernet through a slow LPT
>>port is not really fascinating, I sort of like the idea of using the
>>parallel port for "serious work". This would require reading from the
>>port, though.
>

I have built some hardware that read from the parallel port.  The problem
is that the main data lines are output only.  You can read from the port,
but it returns the last value that you wrote, not what is currently
what you may have put on the port.
	I did get it to work (I was building a MIDI port for a lab).  What
I did was to use four control lines from one of the ports that CAN be read
and read a nibble at a time.  It worked, and was fine for MIDI (A serial
interface) but I would imagine that it would be SLOW for an ethernet card.

Also, it could be that some newer lpt cards do have bidirectionality.  I
think the MCA cards do for instance, but I may be wrong.

john galbraith
galbrait@rintintin.colorado.edu


Newsgroups: comp.unix.bsd,comp.unix.wizards,gnu.misc.discuss
From: oz@ursa.sis.yorku.ca (Ozan Yigit)
Subject: Re: ENOUGH! Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Organization: York U. Student Information Systems Project
	<1993Jan23.212839.7548@prl.dec.com>
	<1jtn31INNl22@shelley.u.washington.edu>
Date: Wed, 27 Jan 1993 18:29:22 GMT

Tim Smith writes:

   >
   >rob pike's jim & sam
   >

   Amusing but irrelevant comment: Pike wrote these editors after the following
   statement: "Everybody writes an editor.  It's easy to do and makes them feel
   important.  Tell them to work on something useful."

Amusing indeed. The original statement is appearently about mail systems
not about editors. Are you sure the quote you attribute to him is indeed
one of his? I very much doubt it.

...oz 
Xref: sparky comp.unix.bsd:11773 comp.bugs.4bsd:245
From: jtkohl@decvax.dec.com (John Kohl Base File System)
Newsgroups: comp.unix.bsd,comp.bugs.4bsd
Subject: syscall(2) broken on i386 + FIX
Date: 24 Jan 93 17:11:07 GMT
Organization: Digital Equipment Corporation

This bug seems to derive from the Net/2 i386 BSD code; it's in BSD/386,
and probably also in 386BSD.

Description:
	syscall(2) doesn't work right.  It leaves $sp off by a word,
which can lead to disaster when it's called repeatedly (as it is in
XView3.0).

Repeat-By:
	Write a program that has a local variable on the stack;
initialize it, then call syscall() repeatedly.  Note that the value
eventually gets trashed when the stack works its way up over the
variable.
Fix:
*** /cdrom/usr/src/lib/libc/i386/sys/syscall.s	Wed Jan  1 16:22:58 1992
--- syscall.s	Sat Jan 23 01:24:01 1993
***************
*** 45,50 ****
--- 45,52 ----
  	pop	%eax	/* syscall number */
  	push	%ecx
  	LCALL(7,0)
+ 	push	%ecx	/* need to push a word to keep stack frame intact
+ 			   upon return; the word must be the return address. */
  	jb	1f
  	ret
  1:

--
John Kohl <jtkohl@zk3.dec.com> or <jtkohl@mit.edu>
working for but not representing:	Digital Equipment Corporation
Member of the League for Programming Freedom---get details: lpf@uunet.uu.net
(The above opinions are MINE.  Don't put my words in somebody else's mouth!)
Newsgroups: comp.unix.bsd
From: galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN)
Subject: su problems.
Organization: University of Colorado, Boulder
Date: Wed, 27 Jan 1993 07:01:08 GMT

Hi, 
	On my 386bsd machine, nobody can su to root.  There is no
password (confirmed by checking the password file a hundred times), yet
it asks for one anyway.  I tried setting a password, but it would not
accept it.  The /etc/group file is ok too.
The only way to become root is from the login: prompt.  Then,
no password is needed.  Obviously, this is a pain.  Does anybody know
what is going on?  Thanks.

john galbraith
galbrait@rintintin.colorado.edu
From: captain@rot.qc.ca (Andrew Webster)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Followup: WD8013 card
Date: 26 Jan 93 01:52:18 GMT
Organization: Groupe de Recherche Operationnelle en Telecommunication (ROT) Inc.
X-Newsreader: TIN [version 1.1 PL6]

Thanks to those who sent their suggestions.  In fact it helps
quite a bit that there is no other device on IRQ 9 ;-)

OOPS!

On a slightly related topic:
The WD8013 does seem to exhibit odd behaviour as the kernel only detects
the card from a cold boot / power up.
One person who responded mentioned this problem.  It is wide spread?
Is there a fix?


-------------------------------------------------------------------------------
captain@broue.rot.qc.ca	| Andrew Webster	|  "The engines canna take it 
			|			|  anymore cap'n..."
IP: 192.77.49.131	| ROT inc.		 ------------------------------
			| Recherche Operationnelle en Telecommunication
			|
Voice: +1 514 737 0020	| Dataradio Inc.
Fax:   +1 514 737 7883	| Montreal, Quebec
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: markd@csqx.cs.rhbnc.ac.uk (Mark Damerell)
Subject: BSD on HP ??
Reply-To: markd@csqx.cs.rhbnc.ac.uk (Mark Damerell)
Organization: RHBNC
Date: Thu, 21 Jan 1993 15:35:11 GMT


PLease has anybody got BSD running on the H-P series 700 machines?
If so, does it include NFS and/or NIS? How good are the installation
instructions?

My connection to News is very flaky; I would be grateful for direct 
replies.
Thank you, mark
From: cs170501@vtaix.cc.vt.edu (Matthew C. Mead)
Newsgroups: comp.unix.bsd
Subject: 'w' returns "can't get namelist" and a few other questions
Summary: Problem with 'w', how to run fingerd, and mail config
Keywords: w fingerd mail config
Date: 20 Jan 93 23:50:12 GMT
Organization: Virginia Tech, Blacksburg, VA


  Hi.  Thanks to all who replied to me with mail about how to get slip working
it seems to be working great!  I think that somehow I messed up one of the
files that the command 'w' uses or something, but am unsure.  It always gets
an error returning 'can't get namelist.'  Any ideas?  Also, I noticed that the
finger daemon is not part of the standard setup and does not run on my machine.
Could someone point me on how to get that working?  I found a file called
'fingerd' in /usr/obj.... somewhere...but was unsure if that was it since it
doesn't seem to be set executable.  My local mail seems to work fine, but I
can't mail to a remote system, and for my last question, why would gcc 2.3.3
respond to a compile attempt saying it did not recognize a '-lang-c' flag?

Thanks in advance to any responses!


Matthew C. Mead
cs170501@vtaix.cc.vt.edu
From: hogan@marie.physik.tu-berlin.de (Tuukka Uusheimo)
Newsgroups: comp.unix.bsd
Subject: 386bsd vs Linux, which to choose?
Date: 28 Jan 1993 13:21:43 GMT
Organization: ZRZ/TU-Berlin
NNTP-Posting-Host: marie.physik.tu-berlin.de


	Yes, I want to install either one on my system, but now I've
got to choose. I've tried 386bsd for a while, and then ran out of hard
disk, and patience... So, I've played with dos for a while. But now I've
had a sudden burst of money on my bank account, and I have to spend it
quickly on another hard disk...

	My system:

ISA 386/40 + 387/40
8MB ram, (64kB cache)
Maxtor 7120A (130MB AT-IDE)
Archive ???? 60MB tape drive	(uses DC2000/2120, connected to floppy adapt.)
Pro Audio Spectrum 16bit	(Yes I had something to do with dos...)
Sony CD-ROM	(connected to PAS via SCSI(?) 8-bit)
Trident-8900C	(but can get Tseng ET-4000)
+ another hard disk 100-200MB...

	So, that's what I've got, and now I would like to know why to choose
the 386bsd over Linux? Is there support for my CD-ROM in bsd, or for my
tape drive? Is the source code available on CD? (I've heard of a MegaCD that
"contains BSD sources", but thats all...)

	If there is someone out there that can, and is willing to help me.
Please answer to this group or via e-mail.

					Tuukka Uusheimo
				e-mail:	hogan@kannel.lut.fi (redirected)
					hogan@marie.physik.tu-berlin.de

Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: [386bsd] still trying to compile rayshade
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Sun, 24 Jan 1993 19:45:24 GMT

Hi,

Using the previous patch, I managed to get rayshade and raypaint to work :)


When I attempt to render with raypaint glass.ray, raypaint core dumps.
I did managed to render several of the examples, like ashtray.ray, solids.ray,
etc...

Don't know if this is my own problem over here but would like to know
if anyone else has it working.

On a different topic, is there a ray tracing program which
works in color.


Thank you!

-- 
This message brought to you by the letters X and S and the number 3
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
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: 386BSD INIT Problem?
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL8]
Date: Fri, 22 Jan 1993 02:16:48 GMT

Mike Trim (mtrim@crucible.demon.co.uk) wrote:
: I've installed the 386BSD system together with the patch kit (except 47)
: as seems to be recommended.  I've also managed to install Julian's SCSI
: drivers and the modified LPT driver recently posted.  All seems to be 
: working except the `init' program rebuilt after installing the patch kit.
: I'm currently using the distribution `init'.

I have the same problem but I install it by using mv . I've one system where
the init works fine but it is where I have the init sources.

Newsgroups: comp.unix.bsd