Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
[02:17am] root@darkstar:/usr/src# patch -p1 < patch-2.5.9
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Nru a/Documentation/BK-usage/bk-kernel-howto.txt b/Documentation/BK-usage/bk-kernel-howto.txt
|--- a/Documentation/BK-usage/bk-kernel-howto.txt Mon Apr 22 15:32:18 2002
|+++ b/Documentation/BK-usage/bk-kernel-howto.txt Mon Apr 22 15:32:18 2002
File to patch:
The clean kernel was 2.5.9..why I get this? I tried -p0, -p1...but still the same. I am lost... hope somebody help.
a and b more so don't exist in your file heirarchy, so you will have to stick with using the -p1 argument to negate this issue, and avoid that causing the problem...as it cuts of the first part off the path in the patch files..
second put the patch in your untarred kernel source folder, and then run patch with using -p1 (ex. /usr/src/linux) and see if that helps you...
that ususally means that this patch has been applied in the master sources which you have, and that this patch is basically not needed, cause it should be already there...
but i mean, if you really wanna try, just hit "y" at that screen and see if it goes through with it...
Again, I am confuse with the organizations of the ftp.kernel.org, I download the linux-2.5.9.tar.bz2, and suppose to get the most stable performance, I should get the patch-2.5.9.tar.bz2 too and apply the patch, if it is a clean source why it claims that it is applied before ?
So, if I hit "Y", the should be nothing gonna change ?
P/S: I know the latest kernel should be linux-2.6.0, I am just want to learn and understand, as the kernel version is not important.
If you have a clean 2.5.9 source tree installed the 2.5.9 patch is useless since it provides the changes between the previous version (in this case 2.5.8) and 2.5.9!
2.5.9 is an old development release and I wouldn't rate it stable (heck, it *is* a development release!). The last 2.5 kernel before it was renamed to 2.6.0-pre was 2.5.75.
Go with either 2.4.23 or 2.6.0 instead (latest "old" stable and the first new stable). Kernel versions 2.5 is the development branch between 2.4 and 2.6, 2.3 was the old development branch and the upcoming one is 2.7...as you can see the odd numbered branches are for development, and stable are even numbered (2.0, 2.2, 2.4, 2.6).
Originally posted by hw-tph It is curious that you are in a directory called Linux 2.5.9 and are trying to apply the 2.5.9 patch. Usually the 2.5.9 patch would be applied to a pristine 2.5.8 source tree to upgrade it to 2.5.9.
If you already have 2.5.9 and try to apply the 2.5.9 patch, the error you're getting is the one you should be getting!
Oops, I didn't read the post..now I realized. So, if I want to apply patch, I should get the 2.5.10, am I right ?