DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been compiling kernals for my AMD64 X2 box with all SATA drives and nvidia graphics since I built it and while on the whole it's been fairly straight forward,there is one issue that continues to annoy and confuse me, the matter of determening the name of the Kernel. the in append-to-version" clause is repeated in the (deb)file
and the some of the info in frome the linux-header file
is missing.
In my /usr/src dircetory I have
linux-source-2.6.16/
linux-headers-2.6.16-2/
linux-headers-2.6.16-2-amd64-k8-smp/
linux-> linux-source-2.6.16/
my make-kpkg is :
make-kpkg \
--append-to-version=-2.sata-enabled.20060828 \
kernel_image -initrd \
modules_image
and the result is
linux-image-2.6.16-2.sata-enabled.20060828_2.6.16-2.sata-enabled.20060828-10.00.Custom_amd64.deb
and what I would really expect (and like) would be something like:
linux-image-2.6.16-2.sata-enabled.20060828-amd64-k8-smp.deb
I've poured over the man make-kpkg file and the kernel sections of the Debian ref. but I haven't found how the linux-header files are incorperated into the source info
can any one help explain what is happening with the repeats?
When you do a make menuconfig, check General Setup -> [ ]Automatically append version information to the version string. On the 2.6x kernels I've compiled under from source it's always enabled by default, which could explain why you're seeing the version number appended twice.
Quote:
Originally Posted by websinger
I've been compiling kernals for my AMD64 X2 box with all SATA drives and nvidia graphics since I built it and while on the whole it's been fairly straight forward,there is one issue that continues to annoy and confuse me, the matter of determening the name of the Kernel. the in append-to-version" clause is repeated in the (deb)file
and the some of the info in frome the linux-header file
is missing.
In my /usr/src dircetory I have
linux-source-2.6.16/
linux-headers-2.6.16-2/
linux-headers-2.6.16-2-amd64-k8-smp/
linux-> linux-source-2.6.16/
my make-kpkg is :
make-kpkg \
--append-to-version=-2.sata-enabled.20060828 \
kernel_image -initrd \
modules_image
and the result is
linux-image-2.6.16-2.sata-enabled.20060828_2.6.16-2.sata-enabled.20060828-10.00.Custom_amd64.deb
and what I would really expect (and like) would be something like:
linux-image-2.6.16-2.sata-enabled.20060828-amd64-k8-smp.deb
I've poured over the man make-kpkg file and the kernel sections of the Debian ref. but I haven't found how the linux-header files are incorperated into the source info
can any one help explain what is happening with the repeats?
When you do a make menuconfig, check General Setup -> [ ]Automatically append version information to the version string.
No, I just checked and "Automatically append" is unchecked
I trimmed down and tried to simplify my config file a couple of cycles back. thanks for the suggestion though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.