On Fri, 30 Nov 2001 07:49:19 -0500 "David A. Bandel" <[EMAIL PROTECTED]> wrote:
> Collins Richey wrote: > > > On Thu, 29 Nov 2001 08:36:32 -0500 "David A. Bandel" > > <[EMAIL PROTECTED]> wrote: > > > > > >>Collins Richey wrote: > >> > >>[snip] > >> > >>>Re the 1.5.0 topic, I tried to patch 2.5.0 with the pre1 and pre2 > >>>patches. pre2 went on with no complaints. > >>> > >>> > >>Let me try one more time: > >>normal patches from one revision level to another (2.4.16 to > 2.4.17 > >>to > >>2.4.18) must be applied in order successively. > >> > >>-pre and -ac patches need to have the previous one removed before > >>applying the new one (patch -R -p0 -i xxx-pre1 ; patch -p0 -i > >>xxx-pre2). > >> > >>???? > >> > >> > > > > Thanks, David > > > > That is now very clear; will remember forever. I presume this > means, > > if you have the pristine base source, you only need the very > latest > > -pren or -acn patch? > > > correct (assuming you're using the correct base) > > > > > > One more question. When I apply (using one of several methods, > > depending on whether still compressed or not, location, etc.) > patch > > -p0, the patch always fails. I have to use patch -p1. Could you > > explain this > > > very simply, this: > look in the patch at the first line: > > diff -Nur linux-2.4.15/Makefile linux/Makefile > > > This line shows you how (and where) the patch was created. To apply > this patch, you should be in the directory where linux (either as a > directory or symlink) exists. So what will be patched is > linux/Makefile. > > If you don't have linux or a symlink, but only linux-2.4.16 and > don't > want to create a symlink, then cd into linux-2.4.16 and use -p1. > > When you use -p1, the first part of the name will be stripped > (linux/), > leaving you with Makefile, which is what will be patched. Big note: > while the kernel patches put out by Linus and Alan Cox are > standardized > and will always be the same, anyone creating a patch can create it > anywhere in the source tree (or above it) (s)he wants to. So you > may > find patches you have to cd well down into the source tree to apply. > Just read the first line of the patch for a clue as to where to > start. > Each successive -p# removes one more part of the name. So if the > patch > says: usr/src/linux/Makefile and you're in src/, you'll need to use > -p2. > > Now, the -R is (ostensibly) for Reversing the patch. This is not > entirely accurate (even if it is true). What it does is apply the > patch > in reverse order using linux/, but going from the second to the > first > rather than the first to the second. That is, rather than change > lines > that begin with - to look the lines that begin +, it changes the > lines > that look like + to ones that look like -. > > Clear as mud? > Very clear; it's a keeper for me. -- Collins Richey Denver Area gentoo_rc6 k2.4.16+ext3+xfce+sylpheed+galeon _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
