Any way to shorten <uname> 4.1.15-4.1.14-4.1.12-3.16.0-4-amd64?
 

Hi, Recently upgraded to longterm 4.1.15, this is how "$kernel" shows up in conky making it wide as a barn door. Tried renaming the modules after compilation before installing didn't work. Tried editing /proc/version, it reverts back..
(Btw how is it "longterm" if they keep changing it every other week, it not even 2 weeks since 4.1.14 replaced 4.1.13 in the archives..) :(
Not that i am complaining, i am sure there are tons of improvements under the hood that i have no idea about..as long as my CPU and HDD temperatures look safe, and i have no problems with sound or graphics, and nothing freezes, i couldn't be happier.:D

The 'long-term' means it will be supported with patches and updates long-term.

I haven't used Conky in years, but there should be a way to use only the first x characters in a string. I don't really remember how string manipulation work in Conky.

have you compiled the kernel yourself?
are you sure this is debian? stable?

what's the output ofthe conky variable $kernel doesn't have any options.
there's global options to limit output to n characters width.
http://conky.sourceforge.net/documentation.html

Yep, followed @m_yates' tutorial in the Sticky here to the letter. Nope, it's Sid.

4.1.15-4.1.14-4.1.12-3.16.0-4-amd64

Thanks for the link, however it'd be much simpler to just avoid the variable and put 4.1.15 as text which i did. It's pointless now tho', conky freezes with the new upgrade, googled it extensively, exhausted all possibilities including resetting hwclock with ntpdate from pool.ntp.org and sync'ing it thus: , got rid of the conky and lua clocks, even tried booting back into the old kernel. No joy, so until the next upgrade it's back to gkrellm for me (room temp. here is 30C on average so i need to keep an eye on CPU/HDD temps.). :study: On the bright side, i have not experienced any of the other malaises like freezing of system, mouse or keyboard, screen, etc. accompanying the conky freeze that i found so many people lamenting about when i googled the issue, it's just conky. :D

If you're running Sid then why not just use the kernel Sid is using? I was compiling my own version of the latest stable kernel from https://www.kernel.org/ but Sid has just moved to 4.3.3 anyhow so I don't need to do that any more to track the latest stable kernel. Of course, if you want to compile your own kernel then do so as it can be useful for enabling options or just a bit of fun but the Sid kernel is now newer than the one you're tracking. As mentioned long term does not mean no updates it mean updates will be forthcoming for a long time so whichever kernel you track there will be updates but if you use the default in Sid it will be much quicker to update as the Debian developers have compiled it for you.

Does make sense to have the latest stable, however debian developers don't seem to have done a very good job of compiling it as far as my hardware is concerned, and apparently i am not the only one who's having issues with it; http://www.linuxquestions.org/questi...es-4175561250/. Ever since the first time i did a dist-upgrade after pointing sources.list to Sid and botched that installation i've made it a point to only do plain upgrades. However, now that you've pointed out what "longterm" actually means i will go for the latest stable but only by compiling it from source. :D

Why not at least try the Debian kernel 4.3 because if it works you're saving yourself time?
If you don't want things to keep breaking then it may be easiest not to use Sid and use something like Linux Mint Debian Edition instead. Without dist-upgrading you're not really running Sid anyhow (as shown by not running the 4.3 kernel) and I can't help thinking you could end up with other issues further down the line if you're not dist-upgrading on a regular basis.

I did, http://www.linuxquestions.org/questi...es-4175561250/, and it didn't take care of the conky freeze issue either, besides freezing during shutdown and reboot.

Edit: Did the sensible thing, compiled the latest stable, thank you for prodding me to do it, took commitment, Respect! :) There's a couple of things on which i do beg to differ, albeit with my glaringly limited knowledge;
It was my understanding that besides the longterm support that you mentioned a longterm kernel also meant that it was one that had been tested and 'bug-fixed' by all major distributions and that only minor bug fixes and patches would be applied to it. That of course, went down the toilet with those biweekly upgrades to it.
Secondly, how can you say that i am not using Sid if i don't do dist-upgrades. Simple upgrades do the same thing except for automatically installing a new kernel, and buggering up my system. In fact i found apt-get judiciously holds back upgrades which could cause problems which aptitude (synaptic) does not (that happened only recently with the audacious plugin upgrade and a few others with it). I get the same new packages in my repository and in addition i have the option to not have them installed automatically. Unless i am very much mistaken apt-get has come a long way and takes care of dependencies very well so i don't have any misgivings about not doing the dist-upgrades, let's see how it goes. Anyhoo, i am very happy with my kernel upgrade so thanks again..conky still skips update_intervals, btw.
Now that's a kernel with a history and pedigree, eh? :D

Stumbled upon it after upgrade to 4.4.0: