> there to 2.1.115, I would set the following links:
>
> linux -> linux-2.1.110/
> v2.1.110 -> linux
> v2.1.111 -> linux
> v2.1.112 -> linux
> v2.1.113 -> linux
> v2.1.114 -> linux
> Documenation -> linux/Documentation/
>
> I suppose I may be ridiculed, but I learned from the 2.0 kernels, that
> sometimes it wants to find those links. The other thing to do is look
None of those links at all are required by the kernel. Linus's
tarballs extract into the subdir "linux". That is where the
patches get applied. If you've renamed it to something else (as
do many, including myself), you can supply a symlink from that
dir to "linux" and the patch will succeed.
All of those other "v2.*" links are of your own creation. The
kernel doesn't need nor use them.
> through the patch where it fails, and see what the path is oif the file
> it intends to patch, and see if the path is misconstrued, or perhaps the
> file is not there. (I had fs corruption once do to a serious brain
> malfunction on my part - *oops*).
Read /usr/src/linux/README and Documentation/Changes for patching
instructions and version numbers.
-- Mike A. Harris - Computer Consultant - Linux advocateEscape from the confines of Microsoft's operating systems and push your PC to it's limits with LINUX - a real OS. http://www.redhat.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html