[04:43] <lotuspsychje> good morning to all
[06:33] <ducasse> morning!
[12:26] <BluesKaj> Hiyas all
[14:52] <CodFection> trump 2016
[15:18] <OerHeks> nacc, i want 3.12 ..
[15:18] <nacc> heh
[15:18] <OerHeks> :-D
[15:25] <nacc> in case folks haven't seen (not sure how widely broadcast) the support length of 16.04.x is changing: https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A16.04.x_Ubuntu_Kernel_Support
[15:25] <nacc> should mean we can just ask in #ubuntu are you on hwe or not
[15:25] <nacc> and it only means one thing (16.04.0/1/current)
[15:25] <nacc> although they have made it a bit more confusing by adding a few extra classes
[15:26] <nacc> so not only is there hwe-rolling (iirc, that's the naming, it might have changed again), there's also 'edge' which just follows the latest kernel available (meaning it would pick the 18.04 kernel early, aiui)
[15:27] <OerHeks> yeas, i have noticed the HWE troubles.. good point asking for HWE directly, saves a lot of time
[15:27] <nacc> it will, i think, be a lot less confusing than 14.04.x
[15:28] <OerHeks> i think it is pointless, using 14.04 + hwe, just upgrade to 16
[15:29] <OerHeks> but then again, systemD will be fun!
[15:29] <dax> systemd*
[15:33] <nacc> OerHeks: oh i agree, and with 16.04.1 out, at least now ther is just 14.04.0/1/5, i think it's mostly a good test of kernel compat *before* dist-upgrade
[17:34] <OerHeks> is this a hack attempt? * Received a malformed DCC request from BlackHat. or just a dcc ..
[17:37] <ducasse> with a nick like 'blackhat' he's probably a 12 year old kid who's been watching mr robot
[17:37] <dax> probably trying to use one of the incredibly out of date DCC exploits
[17:41] <BluesKaj> i think someone was talking about the same thing at ##linux the other day
[17:42] <BluesKaj> complaining actually
[17:43] <OerHeks> Yeah i had a feeling those attempts do not work. but not sure, thanks for answering.
[21:53] <Bashing-om> !info cron
[23:25] <daftykins> !info kodi trusty
[23:25] <daftykins> !info kodi