07-19-2008
You've taken the kernel sources supplied by OpenSuse, haven't you? Suse uses a modified kernel und therefore ships modified kernel sources (which have other features, ... - nearly all distributions do this). That's normally no problem.
But when you try to use standard patches they fail, because the patch utility does not find the proper lines in the sources to modify. Even if there's a way to get those sources compiled better don't use them, because the changes can be incompatible with each other.
Better download an unpatched kernel source tarball from kernel.org (which you can use to patch later on).
You could also have a look into your packages, maybe Suse does also ship an unmodified "vanilla" kernel source tree. This one is exactly identical to the standard tree. You could patch this one without problems.
PS: can't see any problems with your English.
10 More Discussions You Might Find Interesting
1. Linux
I"m installing my ATI card in FC4. I'm going off of instructions that i've found. The firs step says that i need my kernel sources which i've got then it says that i've gotta unpack them so i can make links to the file later. My kernel sources that i've got are .src.rpm I've installed them but... (1 Reply)
Discussion started by: byblyk
1 Replies
2. Linux
Hi can you please help what is this error in linux....
How to check and resolve this. thanks (1 Reply)
Discussion started by: kaibiganmi
1 Replies
3. Linux
Hi All,
I've seen people build modules against a certain kernel source (eg in /usr/src/kernels/my_source/) and some people build against the sources in /lib/modules/my_source/build/
What is the difference and are there any benefits to using the /lib/modules source?
Regards,
Brendan (0 Replies)
Discussion started by: Brendan Kennedy
0 Replies
4. News, Links, Events and Announcements
So, I was browsing groklaw.net, and I was surprised to read that Pamela Jones was reading the copyright notices in the UnixWare 7.1.1 source code files...
Groklaw - Santa Cruz Listed Novell as Owning the Copyrights in 1999
How can that be? Are the UnixWare 7.1.1 sources available to the... (1 Reply)
Discussion started by: pepinox
1 Replies
5. Solaris
Q.) What is KERNEL PATCHING? (0 Replies)
Discussion started by: aparna66
0 Replies
6. Solaris
Hi,
I just want to know, is there any difference between Kernal patching and OS patching in solaris/linux
Thanks in advance (1 Reply)
Discussion started by: vks47
1 Replies
7. Red Hat
Hello,
I have a problem in my server:
HP ProLiant DL580 G5
My OS is REDHAT 4.6
I have an error when I start the server:
Badness in do_unblank_screen at drivers/char/vt.c:2878
...
Your time source seems to be instable or some driver is hogging interupts
rip __smp_call_function +... (1 Reply)
Discussion started by: markke
1 Replies
8. Solaris
Hi folks,
I was patching Sun server (SunOS suns121 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Fire-T200) with the lateset bundle. It was completed with no errors. Server was restarted with shutdown command
(/usr/sbin/shutdown -y -i6 -g0) after patching was complete. However, after that,... (3 Replies)
Discussion started by: zulu1
3 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
What is the difference between these two comands?
sed s/a/b/ <f1 >f2
sed s/a/b/ f1 >f2
Best,
santiagorf (3 Replies)
Discussion started by: santiagorf
3 Replies
10. Emergency UNIX and Linux Support
I was installing Solaris-10 Recommended patch Cluster and it came out without installling all patches. I gave a rebooted and tried installing it again, but it seems some lock or something is prevenventing to install further patches. I am not able to figure out and I am struck in between... (4 Replies)
Discussion started by: solaris_1977
4 Replies
LEARN ABOUT SUSE
git-patch-id
GIT-PATCH-ID(1) Git Manual GIT-PATCH-ID(1)
NAME
git-patch-id - Compute unique ID for a patch
SYNOPSIS
git patch-id < <patch>
DESCRIPTION
A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with whitespace and line numbers ignored. As such, it's "reasonably
stable", but at the same time also reasonably unique, i.e., two patches that have the same "patch ID" are almost guaranteed to be the same
thing.
IOW, you can use this thing to look for likely duplicate commits.
When dealing with git diff-tree output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and
outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. This can be used to make
a mapping from patch ID to commit ID.
OPTIONS
<patch>
The diff to create the ID of.
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]>
DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>.
GIT
Part of the git(1) suite
NOTES
1. torvalds@osdl.org
mailto:torvalds@osdl.org
2. git@vger.kernel.org
mailto:git@vger.kernel.org
Git 1.7.1 07/05/2010 GIT-PATCH-ID(1)