> -----Original Message----- > From: James Manning [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 03, 2000 10:35 AM > To: [EMAIL PROTECTED] > Subject: Re: FAQ > > [Marc Mutz] > > > 2.4. How do I apply the patch to a kernel that I just > downloaded from > > > ftp.kernel.org? > > > > > > Put the downloaded kernel in /usr/src. Change to this > directory, and > > > move any directory called linux to something else. > Then, type tar > > > -Ixvf kernel-2.2.16.tar.bz2, replacing > kernel-2.2.16.tar.bz2 with your > > > kernel. Then cd to /usr/src/linux, and run patch -p1 < > raid-2.2.16-A0. > > > Then compile the kernel as usual. > > > > Your tar is too customized to be in a FAQ. > > there is no bzip2 standard in gnu tar, so let's be > intelligent and avoid > the issue by going with the .gz tarball as a recommendation. -z is > standard. It's going to be changed to the POSIX tar and GNU gzip invoked separately, because everybody felt the need to bitch, and because people aren't smart enough to not send me two copies of the message. :-) > Also, none of the tarballs will start with "kernel-" but "linux-" > anyway, so that needs fixing. Also, I'd add "/path/to/" before the > raid in the patch command, since otherwise we'd need to tell them to > move the patch over to that directory (pedantic, yes, but still) ok, cool, I'll fix those. > oh, and "move any directory called linux to something else" seems to > miss the possibility of a symlink, where renaming the symlink would > be kind of pointless. Whether tar would just kill the symlink at > extract time anyway is worth a check. Tar likes to clobber things when I give it half a chance. I'll mention about the symlink a bit more, although perhaps I should just tell people that they're expected to be familiar with downloading, unpacking, and building kernels before they read this document. Greg
