Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!usc!brutus.cs.uiuc.edu!caesar.cs.montana.edu!milton!uw-beaver!ssc-vax!bcsaic!paula
From: paula@bcsaic.UUCP (Paul Allen)
Newsgroups: comp.os.minix
Subject: Re: PATCH
Message-ID: <21552@bcsaic.UUCP>
Date: 12 Mar 90 19:25:15 GMT
References: <1990Mar11.081127.7489@ncsuvx.ncsu.edu>
Reply-To: paula@bcsaic.UUCP (Paul Allen)
Organization: Boeing Computer Services AI Center, Seattle
Lines: 33

In article <1990Mar11.081127.7489@ncsuvx.ncsu.edu> wall-rt@cscosl.ncsu.edu (Richard Todd Wall) writes:
>
>     Could someone please post a man page for the patch program???  If there
>isn't one, could someone explain how it is used???

Well, patch has lots of options and the man page documements all of
them.  But for the particular case of using patch to apply Minix
upgrades, all you really need to know is that patch eats diff files
on stdin and figures out what file(s) to patch by parsing the diffs.
It looks for the file(s) to patch in the current directory.

For applying the latest bunch of patches, I unpacked each shar file
in the appropriate directory and then ran this little script:

	for n in *.cdif
	do
		patch <$n
	done

Patch makes a copy of each file it patches in filename~ and any rejected
diffs go in filename#.  So if the patch output scrolls by too fast, you
can just look for *# to see if patch had any trouble.  (If you're
patching on a Berkeley system, you get .orig and .rej files, instead.)

Hope this helps!

Paul Allen


-- 
------------------------------------------------------------------------
Paul L. Allen                       | pallen@atc.boeing.com
Boeing Advanced Technology Center   | ...!uw-beaver!bcsaic!pallen