Re: canonical livepatch

[Dimitri John Ledkov]

On 4 November 2016 at 12:44, kallinikos Evangelopoulos
 wrote:
> Thanks very much for the answer. I just checked again, this time with
> --verbose and a reboot, as you suggest, and I got this:
>
> kernel: 4.4.0-45.66-generic
>   running: true
>   livepatch:
> state: nothing-to-apply
> version: ""
> fixes: ""
>
> So, it does seem fine, except for the version again, which appears nowhere,
> unlike everyother instance I managed to see, even yours. Are you sure this
> does not pose a problem? It is strange, isn't it?
>

That doesn't seem strange to me. The version string should be that of
the livepatch kernel module to apply. Currently, there are no
livepatches applied or available to be applied, and hence the version
string is empty.
Note that multiple livepatch versions can be applied against a given
kernel. So, for example, if I don't reboot my machine, and there are
further livepatches released for my currently running kernel then my
version string will keep incrementing whilst the kernel version will
stay the same.

Does above make sense at all?

/me is very new to using livepatches too

Regards,

Dimitri.


> Regards,
>
> Kall
>
>
> Στις 1:29 μ.μ. Παρασκευή, 4 Νοεμβρίου 2016, ο/η Dimitri John Ledkov
>  έγραψε:
>
>
> Hello,
>
> On 4 November 2016 at 09:00, Christian Ehrhardt
>  wrote:
>> Hi,
>> just checked, with the same kernel mine still looks today like yours did
>> initially.
>> If run the status command with --verbose it will list the status it is in,
>> which might help seeing whats going on on your system.
>>
>
> Well if you reboot every day, then you boot the kernel which is fully
> patched - with all security (not just severe ones) and bugfixes. Such
> kernels are released at the same time as livepatches.
> I.e. if one can afford reboots, one is fully up to date.
>
> Plus this service is currently running for xenial only.
>
> I don't like rebooting my desktop. Hence I have:
>
> $ uptime
> 11:25:14 up 24 days,  7:20,  3 users,  load average: 3.15, 2.50, 2.20
>
> $ lsmod | grep live
> kpatch_livepatch_Ubuntu_4_4_0_38_57_generic_1349152  1
>
> $ sudo canonical-livepatch status --verbose
> client-version: "5"
> machine-id: censored
> machine-token: censored
> architecture: x86_64
> cpu-model: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
> last-check: 2016-11-04T11:07:47.882167806Z
> boot-time: 2016-10-11T05:05:04+01:00
> uptime: 583h20m17s
>
> status:
>
> - kernel: 4.4.0-38.57-generic
>   running: true
>   livepatch:
> state: applied
> version: "13.3"
> fixes: ""
>
> Maybe I should reboot into a newer kernel 38 -> 45. If you are running
> 45 kernel, I presume you wouldn't need any livepatches as everything
> is rolled into the latest kernel update.
>
> --
> Regards,
>
> Dimitri.
>
>
>



-- 
Regards,

Dimitri.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Σχετ: canonical livepatch

[Paul Sladen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 4 Nov 2016, kallinikos Evangelopoulos wrote:
> kernel: 4.4.0-45.66-generic
>     version: ""
> except for the version again, [...] unlike every other instance

Hello Kall. What is the Locale/$LANG set to on this machine?

-Paul

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFYHIYLc444tukM+iQRAi0hAKCWpVq0G16Lb95chcE5tEQfSVCrFQCgiioQ
KcJB2Vb/q6+5w4R/6b1B0vA=
=N2hS
-END PGP SIGNATURE-



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Σχετ: canonical livepatch

[kallinikos Evangelopoulos]

Thanks very much for the answer. I just checked again, this time with --verbose 
and a reboot, as you suggest, and I got this:
kernel: 4.4.0-45.66-generic
  running: true
  livepatch:
    state: nothing-to-apply
    version: ""
    fixes: ""

So, it does seem fine, except for the version again, which appears nowhere, 
unlike everyother instance I managed to see, even yours. Are you sure this does 
not pose a problem? It is strange, isn't it?

Regards,
Kall 

Στις 1:29 μ.μ. Παρασκευή, 4 Νοεμβρίου 2016, ο/η Dimitri John Ledkov 
 έγραψε:
 

 Hello,

On 4 November 2016 at 09:00, Christian Ehrhardt
 wrote:
> Hi,
> just checked, with the same kernel mine still looks today like yours did
> initially.
> If run the status command with --verbose it will list the status it is in,
> which might help seeing whats going on on your system.
>

Well if you reboot every day, then you boot the kernel which is fully
patched - with all security (not just severe ones) and bugfixes. Such
kernels are released at the same time as livepatches.
I.e. if one can afford reboots, one is fully up to date.

Plus this service is currently running for xenial only.

I don't like rebooting my desktop. Hence I have:

$ uptime
 11:25:14 up 24 days,  7:20,  3 users,  load average: 3.15, 2.50, 2.20

$ lsmod | grep live
kpatch_livepatch_Ubuntu_4_4_0_38_57_generic_13    49152  1

$ sudo canonical-livepatch status --verbose
client-version: "5"
machine-id: censored
machine-token: censored
architecture: x86_64
cpu-model: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
last-check: 2016-11-04T11:07:47.882167806Z
boot-time: 2016-10-11T05:05:04+01:00
uptime: 583h20m17s
status:
- kernel: 4.4.0-38.57-generic
  running: true
  livepatch:
    state: applied
    version: "13.3"
    fixes: ""

Maybe I should reboot into a newer kernel 38 -> 45. If you are running
45 kernel, I presume you wouldn't need any livepatches as everything
is rolled into the latest kernel update.

-- 
Regards,

Dimitri.


   -- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: gdlib-config command missing in yakkety

[Colin Watson]

On Fri, Nov 04, 2016 at 11:20:01AM +0100, Vincent Gerris wrote:
> I noticed when trying to install GD-2.53 with perl, that the gdlib-config
> command seems to be missing, which was there in :
> packages.ubuntu.com/xenial/libgd-dev
> 
> Can you explain what happened?

It was removed upstream of us by Debian a little while back:

  https://tracker.debian.org/news/770159

I believe you're supposed to use pkg-config instead nowadays.

-- 
Colin Watson   [cjwat...@ubuntu.com]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: canonical livepatch

[Dimitri John Ledkov]

Hello,

On 4 November 2016 at 09:00, Christian Ehrhardt
 wrote:
> Hi,
> just checked, with the same kernel mine still looks today like yours did
> initially.
> If run the status command with --verbose it will list the status it is in,
> which might help seeing whats going on on your system.
>

Well if you reboot every day, then you boot the kernel which is fully
patched - with all security (not just severe ones) and bugfixes. Such
kernels are released at the same time as livepatches.
I.e. if one can afford reboots, one is fully up to date.

Plus this service is currently running for xenial only.

I don't like rebooting my desktop. Hence I have:

$ uptime
 11:25:14 up 24 days,  7:20,  3 users,  load average: 3.15, 2.50, 2.20

$ lsmod | grep live
kpatch_livepatch_Ubuntu_4_4_0_38_57_generic_1349152  1

$ sudo canonical-livepatch status --verbose
client-version: "5"
machine-id: censored
machine-token: censored
architecture: x86_64
cpu-model: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
last-check: 2016-11-04T11:07:47.882167806Z
boot-time: 2016-10-11T05:05:04+01:00
uptime: 583h20m17s
status:
- kernel: 4.4.0-38.57-generic
  running: true
  livepatch:
state: applied
version: "13.3"
fixes: ""

Maybe I should reboot into a newer kernel 38 -> 45. If you are running
45 kernel, I presume you wouldn't need any livepatches as everything
is rolled into the latest kernel update.

-- 
Regards,

Dimitri.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

gdlib-config command missing in yakkety

[Vincent Gerris]

Hi,

I noticed when trying to install GD-2.53 with perl, that the gdlib-config
command seems to be missing, which was there in :
packages.ubuntu.com/xenial/libgd-dev

Can you explain what happened?
The versions are both 2.1.1 and I tried to find if anyone encountered this
issue but I did not find anything.
Shouldn't the command be there just like in 16.04 ?

Kind regards,
Vincent
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: canonical livepatch

[Christian Ehrhardt]

Hi,
just checked, with the same kernel mine still looks today like yours did
initially.
If run the status command with --verbose it will list the status it is in,
which might help seeing whats going on on your system.
​
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

canonical livepatch

[kallinikos Evangelopoulos]

Hello, 

Recently I installed the canonical livepatch. Today I tried to see the status. 
I used the  command. Here is the result:
kernel: 4.4.0-45.66-generic
fully-patched: false
version: ""

Is there an explanation? The first time I tried this command I had this result:
status:
- kernel: 4.4.0-45.66-generic
  running: true
  livepatch:
    state: nothing-to-apply
    version: ""
    fixes: ""
but not today!... Note that in both cases there is no version. I noticed in the 
internet that the version should be mentioned but in my case is not. -- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss