CS_MCCAB%SWTEXAS.BITNET@icsa.rice.edu (06/19/89)
This is a request for those users on bitnet who are upgrading minix.
I am upgrading 1.2 to 1.3. The patch I am using is the binary version
taken from bitnet itself and I am using Minix in which to do all my work.
When I patch I use the following sort of command:
patch -l -N -F3 < minix.1213x
Something happens to the files like minix.1213x between North Dakota
and Texas so that about 1/5 of the diffs have 1 or more extra lines:
e. g. *** 3,6 *** *** 3,6 ***
jack becomes jack
bill bill
sam sam
--- 3,8 ***
--- 3,8 ---
patch aborts every time it hits one of these places. I tried to spot
some pattern to the introduced lines so that I can strip them out,
but cannot.
The only solution I have found is to run patch, wait for the aborts
to occur, edit the diff file and redo until no error occurs.
Is this a well known problem to bitnet gurus? Is my solution the
way people get around this, or is there some other switch on patch
that will make it ignore these extra lines? (Note: the -l switch does
not do this>)
This problem has occurred with every bitnet diff file I have looked at.
One last thing, when patch encounters the patch to mined1.c it
announces that it cannot open a temporary file, then aborts. I have
/tmp on an empty 1.2M disk at this time, so I don't really know why
this message comes up. Anybody help with this one?
Replies to
cs_mccab@swtexas
tom mccabe