rattan@frith.egr.msu.edu (12/29/89)
I am having problems with unsharing the 1.5 postings under
MINIX 1.3 (PH-distribution). It seesm that 'sed' has porblems with
shar files. It compiled properly even with the larger POOLSIZE of
12000 in sedcomp.c. The behaviour is shown below.
---------------
sh < include_00
x - a.out.h
x - amoeba.h
.
.
.
x - limits.h
limits.h: cannot create
x - locale.h
here document '/' unenclosed
(it quits here ...)
----------------
Any clues to the behaviour of sed? All help will be greatly
appreciated. Thanks in advance.
- rattan@frith.egr.msu.eduTAR@MAINE.BITNET (Thom Rounds) (01/03/90)
In article <5890@cps3xx.UUCP>, rattan@frith.egr.msu.edu says: > > I am having problems with unsharing the 1.5 postings under >MINIX 1.3 (PH-distribution). It seesm that 'sed' has porblems with >shar files. It compiled properly even with the larger POOLSIZE of >12000 in sedcomp.c. The behaviour is shown below. >--------------- >sh < include_00 >x - a.out.h >x - amoeba.h > . > . > . >x - limits.h >limits.h: cannot create >x - locale.h >here document '/' unenclosed >(it quits here ...) >---------------- >Any clues to the behaviour of sed? All help will be greatly >appreciated. Thanks in advance. > This is not the behavior of sed. This is the behaviour of a trucated file. Don't worry, you aren't the only one. Glen Overby has the complete files on archive. To get them if you can FTP from there: FTP vm1.nodak.edu 230 IBM VM/SP TCP/IP FTP vm1.nodak.edu blah blah blah USER anonymous 2** User anonymous logged in, working directory is ANONYMOU 191. CD MINIX (case really doesn't matter, it's VM, so it winds up as upper case) 2** Working directory is MINIX 191 GET PC-UPD.150- (post number) Post number is the number of A.S.T.'s post, i.e., #32 would be PC-UPD.150-32 >>> Transfer complete, transfer rate was too damn fast. QUIT If you are on BITNET: TELL LISTSERV AT NDSUVM1 GET PC-UPD 150-(post number) if you are on a VM sys. If you aren't on VM, do whatever it takes to get an IUCV message there containing the above text. It's usually faster to get it through FTP than thru BITNET, unless your Bitnet link is close or it's late or both, when Bitnet can actually be faster (suprised me at first, too). They are quite complete (Ghod knows, I replaced enough of mine with his) That should clear up your problem. >- rattan@frith.egr.msu.edu --Thom Rounds