HDTenEightyP/NetNews huggingface dataset:
From: bernd@iamk4526.mathematik.uni-karlsruhe.de (Bernd Wiebelt)
Newsgroups: comp.os.linux
Subject: cp foo.graphics /dev/lp1 is slooooooooow.
Date: 23 Dec 1992 14:14:27 GMT
Organization: University of Karlsruhe, Germany
NNTP-Posting-Host: iamk4526.mathematik.uni-karlsruhe.de
Keywords: cp /dev/lp1 print kernel
X-Newsreader: TIN [version 1.1 PL8]

This has been asked before, but not yet answered.
Somewhere between linux98.1 and linux99 there was
a change in the blk-drv code which affects output
speed on printers. Does anyone know a cure for
this dilemma which doesn't involve putting the 
old blk-drv code from linux98.1 back into 99?
(In fact, I remeber there was a posting about
a programm solving this problem (lptune???) but
the same posting said that this programm was not
yet completed).

This gets me to another question: Why the hell was
there a change in the !working! lpr-code in a
version so close to linux 1.0. Shouldn`t we have been
waiting till 1.0 was out and then think about redesigning
lpr-code?

Meanwhile, my system is to some extent unusable, since
I am not able to print out graphics which were 
produced by doc-->ghostscript. So, I can only print
out plain ascii-files, which (thank god!) works good.

Any cure for this problem would be highly appreciated.
From: dingbat@diku.dk (Niels Skov Olsen)
Newsgroups: comp.os.linux
Subject: Re: 0.99 directory bug?
Date: 23 Dec 92 15:51:14 GMT
Organization: Department of Computer Science, U of Copenhagen

mph@plasma.apana.org.au (Martin Peter Howell) writes:

>roberts@cray.com (Michael Roberts  {67000 CF/DEV}) writes:

>>My recent upgrade to 0.99 from 0.98.5 has yielded a bug involving
>>floppy disks. When I mount a floppy disk with a minix filesystem
>>on it and I change directories to the floppy disk, I get errors
>>using "pwd" and "du". "pwd" gives the error:

>>	pwd: No such file or directory

>>but it works fine when my current working directory is on a hard
>>drive partition. "du" works fine on floppy directories, but if I'm
>>in a floppy directory and "du" a hard disk directory, like "du /",
>>I get the error:

>>	du: cannot get current directory: No such file or directory

>I have found that trying to mount an extended or minix fs on a
>directory that is not in the root (eg. /usr/mountpoint) always gives
>these errors.  Whereas mounting to a directory in the root is no problem.
>I noticed this a while ago (0.98.[12]) but haven't tried it since
>so I don't know if it has been fixed.

I have used this mounting scheme for ages (!) now:

# /etc/mount
/dev/sda2 on / type minix (defaults)
/dev/sdb1 on /usr type ext (defaults)
/dev/sdc1 on /usr/src type ext (defaults)

With absolutely no problems.

Niels
Newsgroups: comp.os.linux
From: jem@sunSITE.unc.edu (Jonathan Magid)
Subject: Re: X and Orchid Fahrenheit 1280
Organization: University of North Carolina, Chapel Hill
Date: Thu, 31 Dec 1992 18:17:17 GMT

In article <C04rtB.FLL@utdallas.edu> ramesh@utdallas.edu writes:
>
>This archie listing  seem to refer to the XS3 directories for 386BSD and
>not for Linux. The linux port is available in ftp.robots.ox.ac.uk. If I am
>correct 386BSD XS3 will not work with Linux.

if you want to avoid going trans-atlantic (and live on my side. :) )
we mirror robots on a daily basis. check on sunsite.unc.edu in 
/pub/X11/X-servers.

jem.
-- 
Jonathan Magid     jem@sunSITE.unc.edu       sunSITE Administrator
Virtual pizza Delivery (tm)::faxed in 30 cycles or less or you get it
----------------------------------------FREE!!!-----------------------
From: ccasted@prism.gatech.EDU (Edward Deering Boykin)
Newsgroups: comp.os.linux
Subject: ps in linux .99p1 broken?
Date: 26 Dec 92 03:34:53 GMT
Organization: Georgia Institute of Technology


 just got Linux patch 1 ver .99 compiloed on my machine. I have a 66mhz 486
with 8meg ram and local bus hard drive. I have a 64 meg linux partition
and a 15 meg swap.
It only took me 7 minutes to compile! That was with no scsi no fpu emulation no ext-fs and all elese default. I also included the sound kit stuff.
Anyway once I rebooted with the new Image ps does not work. I get this error msg:
lseek kmem: unknown error 207994200

buh?
also my xload form Xfree861.1 shows a continuous bar from top to bottomeven with
just the server running. no windows no nothing running. 
Any ideas?

Later.....
Ed 
ccasted@prism.gatech.edu

-- 
BOYKIN,EDWARD D    Wanna-be Experimental Aircraft Builder Extraordinare
Georgia Institute of Technology, Atlanta Georgia, 30332
Internet: ccasted@prism.gatech.edu
	  gt5584e@prism.gatech.edu
Newsgroups: comp.os.linux
From: S_BIRKENMAI@rzmain.rz.uni-ulm.de (Birkenmaier Rainer)
Subject: Problem with Trident-VGA 9000 and X-Windows
Organization: University of Ulm, Germany
Date: Mon, 21 Dec 1992 15:00:30 GMT
X-News-Reader: VMS NEWS 1.24

Hello everyone!!!

I've got a 486/33 Mhz with 8MB Ram and Trident 9000-VGA-Card (with 512 kB).
I didn't manage yet to configure X-Windows correctly (in Linux 0.98).Only
the the PVGA1 driver brought some unreadable pixels to my monitor.

Can anyone help me or tell me where to get TVGA-drivers from?
Please post or send e-Mail.

Thank's a lot

Rainer Birkenmaier
From: Dave-Nuttall@cup.portal.com (David Dave Nuttall)
Newsgroups: comp.os.linux
Subject: Re: Kernel Build Benchmark
Date: Thu, 24 Dec 92 17:00:53 PST
Organization: The Portal System (TM)

To whom it may matter/be of interest:

Linux src 0.99, pl 1
on:  486/DX 33, 8MB RAM, 8MB of swap
     on Maxtor 210MB IDE hard drive

MAKE CLEAN 
date = Thu Dec 24 18:37:17  1992
make all
#
date = Thu Dec 24 18:47:40  1992
Newsgroups: comp.os.linux
From: quandt@cs.umr.edu (Brian Quandt)
Subject: real time
Date: Sun, 3 Jan 1993 05:41:59 GMT
Organization: University of Missouri - Rolla, Rolla, MO

What can anyone say about linux and real time support?  Same
question applies to 386bsd.  I tend to believe that this concept
would not be possible.  The reason being is that this (I believe)
is a fundamental design change in how the kernal works.  However,
if anyone has information to the contrary please let me know.
Newsgroups: comp.os.linux
From: bmyers@shyguy.lonestar.org (bob myers)
Subject: compiling .99.1 - problem with inode_init
Organization: 3-B Technology
Date: Wed, 23 Dec 1992 21:57:52 GMT

Yesterday, I downloaded the linux-0.99.1.tar.Z file from tsx-11.mit.edu,
and installed it on my laptop (tandy 4800HD/50 mb linux partition/8 mb ram).
I deleted the entire /usr/src/linux tree before installing the "new" copy
of the source code, just to be sure that nothing was left around that wasn't
needed...

well, when I went to do the make all, I got as far as the
system compiling upto it hitting this reference for calling inode_init
in /usr/src/linux/init/main.c (line 241, i believe).  I get the following
message(s):

init/main.c: In function 'start_kernel':
init/main.c:241: too many arguements to function 'inode_init'
init/main.c:241: void value not ignored as it out to be 
make: *** [init/main.o] Error 1

Any ideas?

-bob

-- 
-----------------------------------------------------------------
Bob Myers                        | You gotta watch out for those
Shyguy's AT&T SVR4 Unix/Uniboard | shy guys....you never know 
Email:bmyers@shyguy.lonestar.org | what they're thinking..:)
Newsgroups: comp.os.linux
Subject: Re: 0.99 pl 0/1 fine, but breaks xdm -nodaemon
From: hamilton@golem.wcc.govt.nz (Michael Hamilton)
Date: 24 Dec 1992 14:19:03 +1300
Organization: Wellington City Council, Wellington, NZ
Keywords: kernel linux 0.99
NNTP-Posting-Host: golem.wcc.govt.nz


0.99 patch level 1 seems to work fine on the following two
configurations, appart from the xdm problems I reported in a earlier
posting.  Good work.

Make:		MiTAC
Model:		4280G
Processor:	486DX 33 MHz (Unknown amount of cache)
Bus:		EISA
Memory:		8MB 
BIOS:		Phoenix Technologies 1.0 4280 R1.03
HD:		202 MB Formatted (Conner of some kind)
Video card:	PVGA 512K 
HD/FD cntrllr:	SCSI Adaptec  AHA-154XB
Monitor:	MiTAC M1420-02N
Eithernet:	Western Digital EtherCard PLUS V2.1 8013EP
Misc:		COM1 - Logitech mouse.


Make:		Hewlett Packard 
Model:		HP QS20
Processor:	386DX 20 MHz
Memory:		8MB 
BIOS:		Phoenix Technologies V D.02.05 QS/20
HD:		Quantum Prodrive LPS 240 AT IDE
Video card:	InformTech (ie noname) Tseng ET4000 HiColor 1MB
HD/FD cntrllr:	HP Multi-function card
Monitor:	Philips 7 CM 3209
Misc:		COM1 - CASE Quattro 2400 buad modem (noname serial card)
		COM2 - mouse (Quickshot QS-159) (noname serial card)
		COM3 - vt320 terminal (IRQ 10 from HP multi-function card)
		Colorado Jumbo 120 tape unit (backup via tar to DOS)


-- 
Michael Hamilton, Computer Services Section, Wellington City Council, P.O. Box
2199, Wellington, New Zealand.  Phone: (64) (4)801-3300  FAX: (64) (4)801-3020
Domain: hamilton@csc.wcc.govt.nz          PSImail: PSI%0530147000090::HAMILTON
From: kf8nh@kf8nh.wariat.org (Brandon S. Allbery)
Newsgroups: comp.os.linux
Subject: Re: lpd
Date: Fri, 01 Jan 93 01:42:17 EST
Distribution: world
Organization: Brandon S. Allbery's Personal System

Bob.Martin@f34.n343.z1.fidonet.org (Bob Martin) writes:
> Since I new the diskettes were good and the disk drive is ok (works fine
> under dos and windows) I started looking at the CMOS settings. After
> trial and error I found that if I added 1 wait state the hangups went
> away.
> 
> Any body else seen this before or can confirm this, may just be my
> hardware.  

I haven't seen it with Linux or anything else on my 386DX-33, but I *have*
seen something like this.  It's what made me buy the 386DX-33.

My previous machine was an XT with an Intel Inboard-386 (386DX-16).  It
started out with 1MB RAM.  When I decided to upgrade it to be almost a real
computer :-) so I could run Borland C++ and multiple DESQview windows (the
Inboard requires special activation to enable 386 capabilities, and no
386-mode OS supports this activation, so *ix-like OSes were clearly out of
the question) I added a 2MB daughterboard and replaced my ancient MFM
controller and 20MB hard drive with a 50MB IDE setup.

Under DOS it worked.  Under DESQview disk reads were often utterly corrupted.

The "utter corruption" turned out to be SuperStor, which I had been running
on the 20MB drive and installed on the 50MB drive.  When I removed it, I
found that the computer was occasionally catching a byte sent by the disk
drive *twice*.

I tried again, first with an SCSI disk and an ST01 controller, then with an
MFM drive and a newer MFM controller (my old controller was so old that it
couldn't habdle a drive larger than 20MB).  The SCSI was the most reliable,
but even it duplicated characters occasionally.  Forcing wait states on hard
drive reads (this can be done with the Inboard configuration/386 mode
activation TSR) made it even more reliable, but it still had the problem.
By then it was obvious that it was a hardware problem between a fast hard
drive, a fast CPU, and a very slow (XT standard) bus, and bought a real 386.
I suspect hardware wait states would have worked even better, but there was
no way to get them on an XT....

Again, this only happened under DESQview.  Had I been capable of booting
something like Linux, it would probably have happened there as well.

So:  it is quite possible for hardware timing to be such that things work
under BIOS/DOS, but not in a multitasking environment.

++Brandon

He's BAAAACK! Brandon S. Allbery     NOTE NEW ADDRESS!!! kf8nh@kf8nh.wariat.org

Newsgroups: comp.os.linux
From: rahardj@ccu.umanitoba.ca (Budi Rahardjo)
Subject: make config (0.99.1), gcc -m486 question
Summary: confused
Keywords: config 486
Organization: University of Manitoba, Winnipeg, Manitoba, Canada
Date: Wed, 23 Dec 1992 14:20:26 GMT

When doing 'make config', there's a question :

Use -m486 flag for 486-specific optimization ?

I am using an 386SX, what would be the answer to that ?
If I say yes, gcc starts to compile stuff with -m486 flag. 
Is this okay ?

Right now I answered it with no.

-- budi
-- 
Budi Rahardjo <Budi_Rahardjo@UManitoba.Ca>
Unix Support - Computer Services - University of Manitoba
Newsgroups: comp.os.linux
From: jrs@world.std.com (Rick Sladkey)
Subject: Re: working telnet/telnetd and others available
Organization: The Internet
Date: Thu, 24 Dec 1992 03:21:20 GMT

>>>>> On Wed, 23 Dec 1992 04:54:48 GMT, jrs@world.std.com (Rick Sladkey) said:

Rick> And yes, telnet and telnetd really work.  I think.

Oops, I forgot to mention that you need the login from
poeigl-1.7.tar.Z in order to use the telnetd binary.  Otherwise,
comment out the "-h" stuff in telnetd.
--
Rick Sladkey
jrs@world.std.com
Newsgroups: comp.os.linux
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: Re: UUCP 103 (taylor)
Date: Mon, 21 Dec 1992 18:50:28 GMT
Organization: Illinois State University

In article <1992Dec21.153625.4491@welchgate.welch.jhu.edu> keithc@welchgate.welch.jhu.edu (Keith Christopher) writes:
>
>Infile included from uucico.c:304:uucp.h:1180:conflicting types for 'strncasecmp'
>/usr/include/string.h:36: previous declaration of 'strncasecmp'
>
>make *** [uucico.o] error 1
>
This is a relatively common error which occurs when porting software to
Linux.  Typically, just commenting out the offending declaration (in this
case, uucico.c line 304) will fix the problem.  Depending on what assumptions
the code makes about the type for strncasecmp, you may need to fix other
parts of the code as well.  I typically comment out, compile, and if it
doesn't dump core and seems to work, don't worry too much :-).  Since this IS
a mailsystem, I would probably be more careful in checking the code first,
since (unlike some other toys) its pretty important that it work correctly
and reliably.

Hope this helps!

Jean.

-- 
Jean Liddle                                 
Computer Science, Illinois State University  
e-mail:  jliddle@ilstu.edu                  
--------------------------------------------
Newsgroups: comp.os.linux
From: weh@beta.lanl.gov (William E. Harvey)
Subject: Re: Error...NMI received?
Organization: Los Alamos National Laboratory
Date: Sat, 26 Dec 1992 11:25:16 GMT

In article <1992Dec25.143730.25517@klaava.Helsinki.FI> torvalds@klaava.Helsinki.FI (Linus Torvalds) writes:
>NMI's generally get generated by either memory parity errors or by
>special hardware (power-saving features etc).  Linux tries to disable
>NMI completely because it can't handle it anyway, but it seems some
>motherboards let it through anyway (or then I do the disabling
>incorrectly: I have never seen a NMI anyway). 
>
>		Linus


I was getting this all the time on my laptop.  What I did was find the
section of source code that printed out "NMI received ..." and
commented it out.  The power saving features of the laptop work fine
and my screen doesn't get garbaged up whenever the disk drive autoparks.

Billy Harvey
weh@lanl.gov
Newsgroups: comp.os.linux
From: cae@davidge.com (Caleb Epstein)
Subject: Possible Race Condition?
Followup-To: comp.os.linux
Keywords: race
Organization: Davidge Data Systems Corp., NYC, NY
Date: Wed, 30 Dec 92 20:48:24 GMT

Linux kernel: 0.99.1

    Greetings, fellow Linuxers.  I believe I may have
discovered a race condition in the kernel this afternoon.
It may relate to the MINIX file system.

    I was installing a new hard drive on my Linux box and
had copied over a whole bunch of directories onto the new
disk (a new, roomy /usr parition).  I was then removing the
old directories (from a primary, MINIX partition) after a
reboot and did the following:

        cae_1# cd /mnt
        cae_2# rm -fr * &
        [ I paused for a few seconds; my drive was chugging ]
        cae_3# ls -Flg

The 'rm' job was working and ended up finishing its job just
fine, but the 'ls' never did anything - no output at all.  I
hit Ctrl-C and Ctrl-Z a few times, but got no response.  I
logged on on another VC and did a 'ps'.  The 'ls' was still
there, but all attempts to kill it were in vain - it stuck
around, even when I sent a signal 9 to it (usually kills
anything on the Suns at work).  The STAT field for the 'ls'
process showed 'R'.  Eventually I killed the login shell and
the previously-hung VC got a new login prompt.  Even after
this, though, the 'ls' job was still in the process table.
It only disappeared upon a reboot (obviously).

    Does this sound like a possible race condition in the
MINIX fs code?  Could my Ctrl-C/Z-ing have hung things up?
Am I a dodo for wanting to 'rm' and 'ls' at the same time?

    Oh, BTW, both of my hard drives hang off of a Seagate
RLL drive controller, if that matters.

-- 
[ Caleb Epstein ][ Davidge Data Systems Corp, New York, NY ][ cae@davidge.com ]
[      Someone's definitely jumping into the tub ... with your brother!       ]

Newsgroups: comp.os.linux
From: dinn@ug.cs.dal.ca (Michael 'Moose' Dinn)
Subject: Gopher: anyone ported it to Linux?
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
X-Newsreader: TIN [version 1.1 PL6]
Date: Sun, 3 Jan 1993 15:21:33 GMT


Has anyone ported Gopher 1.x to Linux? If not, I'll start doing that
tomorrow... For those of you who don't know what Gopher is, it's the
slickest information server to come along since man pages.

--
 Michael Dinn, CS Student * dinn@ug.cs.dal.ca * Use your modem! (902) 461-4773
 "make lots of money",  "enjoy the work",  "operate within the law":  choose 2
Newsgroups: comp.os.linux
From: alsaggaf@athena.mit.edu (M. Saggaf)
Subject: Re: App. defaults for Seyon 1.6
Organization: Massachusetts Institute of Technology
Date: Fri, 1 Jan 1993 02:31:09 GMT

>>>>> On Fri, 1 Jan 1993 00:28:28 GMT, wto@cbnewsg.cb.att.com (William T. O Connell) said:

WTOC> In article <C056uA.14G@techbook.com> kosina@techbook.com (Martin Kosina) writes:
>Hi,
>
>I got Seyon 1.6 to work, but the program is still complaining that it
>cannot find the "application defaults" and therefore "won't run
>correctly". I read the help file and README but it only says that
>linux users need not to change anything and everything will be
>installed properly if you compile it with "make install". It puts the
>file 'Seyon' into /usr/lib/shlib/ /jump/X11/appdefaults/ but can't
>find it even if I put this into my $PATH.  Could someone tell me
>where this is supposed to go ?
>
>Thanks !

WTOC> Move the file to /usr/X386/lib/X11/appdefaults.  (Note: I'm not
WTOC> on my linux machine right now, that should be the right path -
WTOC> if it's not, it's close).  Anyway, the makefile puts it in the
WTOC> wrong spot. After putting it the directory with all the other
WTOC> application default files, seyon should find it.

Yes, the imake config template of SLS seems to be broken. You can
certainly install the app-defaults files by hand, but this is a
temporary relief and not real remedy; and the problem will bite you
again when you build other X applications under your setup or upgrade
Seyon. Better fix the imake template. Shouldn't require changing more
than a couple of lines. In the mean time, you have to install the
app-default files as follows:

install -c -m 0444 Seyon.ad /usr/X386/lib/X11/app-defaults/Seyon
install -c -m 0444 Seyon-co.ad /usr/X386/lib/X11/app-defaults/Seyon-color

Cheers,

/M. Saggaf                          | Stop the genocide
 alsaggaf@athena.mit.edu            | Save Bosnia


Newsgroups: comp.os.linux
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: Re: HIMEM.SYS&WINDOWS3.1&LINUX(kernel panic after run windows3.1)
Date: Sat, 26 Dec 1992 17:35:10 GMT
Organization: Illinois State University

In article <1992Dec26.041223.62271@cc.usu.edu> slc4x@cc.usu.edu writes:
>Hi: 
>     The problem is that after I install SLS, I backup some of my dos
>file and reinstall the MS WINDOWS 3.1. After I reinstall it and run the windows
>I try to login linux again(of cause I reset the system). But there's an error
>message come out just before linux load the kernel into the memory. The error
>message is

t is unlear in your post whether you are doing a warm-reboot from DOS to
linux, and whether you are using LILO or BOOT.SYS to select your
operating system, or just running bootlin from the DOS command line.
Personally, I use boot.sys because (a) I still keep DOS around for games
and (b) I'm too cowardly to mess around with the boot sector of my hard drive.
If you are doing this, you can use himem.sys or other 386 memory 
management, as long as your config.sys file is organimzed something like
this:

device=boot.sys [various args]
  device=boot.a
  device=top     Select Desired Operating System
  device=boot.1  Linux
    shell=c:\etc\bootlin.com c:\etc\image
  device=boot.2
    device=himem.sys
    [ ... other ms-dos drivers, BUFFERS=, FILES=,  etc. ]
  device=boot.z
device=boot.end

In this case, if you want to bootup linux, you do so without starting
any goofy memory management stuff under DOS which might interfere with
bootlin and hence how the linux kernel gets loaded into memory.

hope this helps!

Jean.
-- 
Jean Liddle                                 
Computer Science, Illinois State University  
e-mail:  jliddle@ilstu.edu                  
--------------------------------------------
From: hikaru@infodn.rmi.de (Walter Doerr)
Newsgroups: comp.os.linux
Subject: [FIX] Re: gcc : Internal compiler error
Keywords: GCC Internal Error
Date: 30 Dec 92 17:09:55 GMT
Organization: infodn, Dueren, Germany

In <#012p5=@rpi.edu> palmj@rebecca.its.rpi.edu (Jyri L. Palm) writes:

|Basically, when I try compiling various packages, the most common error message
|that I'm getting nowadays is :

|gcc: Internal compiler error: program cc1 got fatal signal 11
|make: *** [main.o] Error 1

I have SLS 0.98pl5 from mid november and I encountered this problem at
various times: first when recompiling the kerneel after a reinstall (new HD)
and then when compiling xv 2.00.
At first the problem seemed spurious but later it got to a point where I was 
unable to compile even a single .c file.

Out of desperation I reinstalled cpp and gcc from the installation disks
(using sysinstall -remove 222d7b and then reinstalling the same files again).

This fixed the problem.

Hope this helps.

-Walter


-- 
"Country music sucks. All it does is take precious airspace away from shock
 DJ's whose cruelty and profanity amuse us all."      - Bart Simpson [8F19] 
Newsgroups: comp.os.linux
From: amartell@nyx.cs.du.edu (Alex Martelli)
Subject: Re: Undefined C library functions
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Sun, 27 Dec 92 16:33:39 GMT

wto@cbnewsg.cb.att.com (William T. O Connell) writes:

>Unable to login, get the following message after entering any login :
>	login: root
>	Undefined C library functions
>		1. ulimit (use getrlimit/setrlimit instead).
>		2. light C shared image (use the real one instead).
>	login:
	...
>Note that I recently updated to libc.so.4.2. But, I don't know
>if this library is causing the problem because I inadvertently
>deleted some other libaries but restored them from my SLS 99 
>distribution. Maybe I have a symbolic missing link? or missing library?

>Any ideas on what is causing this during the login process.

Yes, I had this identical problem: it IS 4.2!  I got 4.2 and superimposed
it onto a SLS 0.99, together with a pl 1 kernel, and pointed libc.so.4
to it, and login broke exactly in the way you describe.

Quickest fix: make a symbolic link /lib/libc.so.O, point it to the
libc.so.4.1 library; emacs /bin/login, Ctrl-S for libc.so.4, change the 4
into an O, and save it.  Now it works again.

Note that you CANNOT patch with perl, since it truncates input files at
first binary byte of 0 (the little fix for this perl bug has also been
posted in a followup to my msg, if you have perl sources to patch).


Alex
--
Alex Martelli - preferred email alex@am.sublink.org
Newsgroups: comp.os.linux
From: ldstern@rodan.acs.syr.edu (Larry Stern)
Subject: problem with crt0.o
Organization: Syracuse University, Syracuse, NY
Date: Mon, 21 Dec 92 04:44:04 EST

I have SLS .98p6 running sucessfully on my 386, but on several occasions
when I've tried compiling different Unix applications the compilation
stops with a 'crt0.o' error.  Has anyone else encountered this problem,
and if so, what did you do?
				
					Thanks,
					Larry

Newsgroups: comp.os.linux,comp.windows.x,comp.windows.x.i386unix