View previous topic :: View next topic |
Author |
Message |
BigPalabra n00b
Joined: 14 Jun 2008 Posts: 24
|
Posted: Sat Aug 02, 2008 12:10 am Post subject: Append to Kernel Release |
|
|
When configuring a Kernel manually (make menuconfig), what is for "Local version - append to kernel release" and "Automatically append version information to the version string" options ???
Regards. |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sat Aug 02, 2008 2:09 am Post subject: |
|
|
The first option changes, amongst other things, what is reported by uname, and also where the modules for the running kernel are found (ie the subdirectory in /lib/modules/).
This is useful if you are running more than one version of an identical release/revision, for example my currently running kernel I've manually patched with a patchset to add transparent compression to ext2, so I added "-e2compr" to the local version string, and uname now reports "2.6.25-hardened-r2-e2compr".
This can be very useful, for (another) example I learned the hard way that modules compiled for a kernel using sparse memory are incompatible with kernels using flat memory, even if everything else is identical, so this option would have been very useful to me when testing SPARSEMEM out.
As for the "Automatically append version information to the version string", this appears to only really be useful for live git ebuilds, adding the git revision to the kernel's version number, but there may be other uses.
HTH. _________________ "You have to invite me in" |
|
Back to top |
|
|
BigPalabra n00b
Joined: 14 Jun 2008 Posts: 24
|
Posted: Sat Aug 02, 2008 5:22 am Post subject: |
|
|
THX A LOT !! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|