Query about custom fedora build process
kai at gnukai.com
Thu Sep 8 12:00:02 EDT 2011
Some programs (like VIM) modify file in-place. Some programs (I think
'perl -pie' may do this) will read the file into memory, and when it's
time to write the file back out, it deletes the original, and writes the
new one. They made a note of this in the wiki article:
"Using vim on FC14, it treated the hard link as a hard link and thus the
above technique failed. It was necessary to repeat the original copy
used for the .orig directory for the .new directory. Note that this uses
twice the space."
Perhaps there's a trick to vim to work around it, but I don't know of any.
My suggestion would be to hardlink the entire source tree, and then
afterwards delete the destination hard links for the files you want to
modify, and re-copy (normal copy) the original files again.
On 09/07/2011 04:16 PM, Vaibhav Jain wrote:
> I am trying to build a custom fedora kernel on a fedora (FC15) machine
> by reading the
> article: http://fedoraproject.org/wiki/Building_a_custom_kernel
> but i am unable to make any progress as my changes are not getting
> So I have query about the procedure given in the article. The article
> asks to first create
> hardliks between files in .new and .orig directories and then to make
> changes and to .new directory and to
> generate a patch by a diff between the .orig and .new directories. But
> I am just wondering if the
> files in both the directories are hardlinks then how can diff work
> because after changing a file in .new directory
> the file in .orig directory should also change.
> cp -r ~/rpmbuild/BUILD/kernel-2.6.$ver.$fedver/linux-2.6.$ver.$arch ~/rpmbuild/BUILD/kernel-2.6.$ver$fedver.orig
> cp -al ~/rpmbuild/BUILD/kernel-2.6.$ver.$fedver.orig ~/rpmbuild/BUILD/kernel-2.6.$ver.$fedver.new
> cd ~/rpmbuild/BUILD
> diff -uNrp kernel-2.6.$ver.$fedver.orig kernel-2.6.$ver.$fedver.new> ../SOURCES/linux-2.6-my-new-patch.patch
> Vaibhav Jain
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kernelnewbies