jeff@questar.QUESTAR.MN.ORG (Jeff Holmes) (02/15/89)
I was wondering if anyone else has this problem, or if someone could tell me what basic point I'm missing... I was trying to run a shar file through sh on my Minix 1.2 (PC) system. The shar file was about 90K, and there were 4 source files shar'ed together. After extracting 3 of the 4 sh told me that it was out of memory and wouldn't extract the remainder (it just kept printing OUT OF MEMORY ON RAM DISK). Then I pared down the shar file to under 50K and it worked fine. Then I tried a 60K shar file with ALOT of directories, sub directories and files in it and it extracted a majority of the shar file and quit with the message "can't do pipe - try again" which to me says that I had too many processes going. I'm trying to get the 1.3 archives I got from bugs to my home system, from where it is now (at work) without having to copy each directory and file to floppy seperately. Tar won't work so I thought that 'makekit' which creates shar files would be my next best bet, but I'm having alot of trouble getting it to work. I've seen shar files posted that are > 100K so what's the story? Why won't my sh handle the larger shar files? Any help GREATLY appreciated. thanks -jeff- -- Jeff Holmes DOMAIN: jeff@questar.mn.org Questar Data Systems UUCP: amdahl!bungia!questar!jeff
paula@bcsaic.UUCP (Paul Allen) (02/16/89)
In article <2204@questar.QUESTAR.MN.ORG> jeff@questar.QUESTAR.MN.ORG (Jeff Holmes) writes: > [ ... about troubles with unsharing on Minix. He's trying to move the 1.3 upgrade stuff to his PC by encapsulating it in sharfiles.] When I upgraded to 1.3, I put the stuff to be moved in tar files, wrote them on DOS floppies, and then used dosread and a slightly hacked version of the 1.1 Minix tar to extract the stuff. The change to the tar program was trivial. Essentially, I altered it so that it would know that '-' as the name of the tar file means stdin or stdout. I do all my un-sharing on my Sun, and so haven't tried to unpack sharchives on Minix. It's something else to try, anyway! Paul -- ------------------------------------------------------------------------ Paul L. Allen | pallen@atc.boeing.com Boeing Advanced Technology Center | ...!uw-beaver!ssc-vax!bcsaic!pallen