Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!mtune!codas!killer!jaime From: jaime@killer.UUCP (James Dasilva) Newsgroups: comp.os.minix Subject: Re: A (general) word about getting new patches with the SHAR files Message-ID: <1883@killer.UUCP> Date: Wed, 21-Oct-87 16:42:26 EST Article-I.D.: killer.1883 Posted: Wed Oct 21 16:42:26 1987 Date-Received: Sun, 25-Oct-87 01:08:08 EST References: <609@louie.udel.EDU> Reply-To: jaime@killer.UUCP (James da Silva) Organization: The Unix Connection BBS, Dallas, Texas Lines: 30 Keywords: sed chmod exit fix In article <609@louie.udel.EDU> ESC1332%ESOC.BITNET@wiscvm.wisc.edu (K.Keyte) writes: > ii. I've compiled my version of 'sed' (eventually after increasing > the stack space of 'sh' and performing a manual 'asld' to get > around the RAM disc overflow (by using an 'asld' -T. option). > However... the 'sed' call doesn't seem to work too well. It > truncates some of the files at strange places and leaves most > of them completely empty. The problem is in exit(), not sed. Put a flush() before each exit() in the sed sources and you should be fine. > iv. The FIX program simply calls 'strcmp', but due to the tab/space > (etc) problem(s) mentioned in (iii) above, it nearly always fails > the test even when it SHOULD pass. The solution is to write a > replacement 'strcmp' which ignores differing white-space characters, > but the solution is not ideal. I have not yet had this problem, but it does seem that a version of fix that ignores differences in whitespace IS a good solution to the problem, barring fixing every mailer in use. Patch does this, doesn't it? Using the Minix 1.2 shell with the data area set to 32000 bytes, sed with the described fix, and the version of chmod that I posted to the net, I have been able to successfully unshar every shar that I have attempted, including all of ast's 1.2 "Definitive Update". I have not attempted the Turbo-C patches, however. James da Silva UUCP: ihnp4!killer!jaime