Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar -x kernel-2.2.16.tar ? > -----Original Message----- > From: James Manning [SMTP:[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. > > 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) > > 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. > -- > James Manning <[EMAIL PROTECTED]> > GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4
