On Sat, Sep 10, 2005 at 05:19:07PM +0200, Andrea Arcangeli wrote: > On Sat, Sep 10, 2005 at 07:43:31AM +0200, Sven Luther wrote: > > Not a good idea. Why clutter the namespace of versions in order to adapt to > > non-debian needs. ? What is it you intent to do anyway ? > > My intent is to be able to tell the "branch" of the kernel based on > `uname -r` (per subject). So if I see 2.6.13-whatever-debian it means it > was a kernel patches by the debian patchset. If I see 2.6.16-3-ppc64 > I don't know for sure where it comes from.
Sure, i am not stupid, i perfectly noticed that, now my question is why do you want to know that ? > So it doesn't sound such a terrible thing from my point of view. Sure, it is a debian system, running a debian kernel, and that's it. If you want you can look at the uname -r output, then look at /lib/modules/<version> and look in your dpkg database to match it to a package, something like that : dpkg -S /lib/modules/`uname -r` Or even : if dpkg -S /lib/modules/`uname -r` ; then echo DEBIAN; else echo NOT DEBIAN; fi > I don't see what's the bad thing about marking -debian or -deb the > kernels that you _modify_ with your set of patches. So, you want us to add uneeded cruft to all the debian kernel packages, just to satisfy your curiosity ? Please try convincing us first if you have a legitimate reason to want to do this distinction or something. > I'm not saying that you have to add -deb if you _don't_ modify the > kernel source, infact I believe you shouldn't add -deb unless you change > the kernel source. Bah. > But if you apply your own patches (like -mm,-ck,-ac,FC,EL,etc..etc..) > then what's wrong at being able to identify which patchset was applied > like it's already possible for many other branches? Sure, you have a debian system, you should have a debian kernel, if you don't run a debian kernel, your self own fault, and if you don't remember what kernel you have installed, ... > > more /proc/version > > Linux version 2.6.12-1-powerpc ([EMAIL PROTECTED]) (gcc version 4.0.2 > > 20050806 > > (prerelease) (Debian 4.0.1-4)) #1 Tue Aug 16 20:08:54 UTC 2005 > > That's the compiler, I'm not tracking the compiler. In theory I could, > but then it would get wrong if I would grab a debian kernel and compile > it under suse. However if I fail to idenfiy the branch of the kernels > based on `uname -r`, I agree the fallback would be to use the compiler > to identify the branch (even if it's not completely reliable). > > Personally I also see as pointless to add 686 or k7 in the name, why > don't you simply enable /proc/config.gz that will tell the user a _lot_ > more than just the cpu compilation selection? But that's quite offtopic, > my intent was only to try to identify the kernel vendor/branches. Oh, right. do you have a single clue on how the debian package system works ? And what the relationship between the kernel version and the name of the debian package containing it is ? Also, with your scheme ? How will you distinguish between the 686 or k7 flavours (or even the powerpc and powerpc64 flavours, which are not compatible with each other) ? Also notice that /boot/config-`uname -r` will give you all the info you need about the running kernel's config file. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
