=== gerald is now known as Guest197
[06:56] <smb> lamont, Then something is not right. Should say /dev/vda1 (and no it only always says sda regardless of ata or real scsi)
=== faust is now known as Guest14235
=== gerald is now known as Guest58147
[12:55] <lamont> smb: I see
[13:09] <hallyn> ok so what is the recommended lts kernel package for on trusty?  There's a lot of options.  linux-image-hwe-generic-trusty ?
[13:09] <hallyn> i.e. will that one auto-update to the vivid kernel at some point?
[13:10] <hallyn> seems the most promising, think i'll go with that
[13:34] <arges> hallyn: what are you trying to do? I believe the high level meta packages are 'linux-<flavor>?-<lts-series>?-<eol-upgrade>'  where eol-upgrade rolls into the next lts kernel
[13:35] <arges> if that pseudo regex makes any sense
[13:38] <hallyn> arges: linux-image-hwe-generic-trusty seems to be an alias for linux-image-generic-lts-utopic ;  -vivid doesn't exist yet;  so my ohpe was that linux-image-hwe-generic-trusty will become linux-image-generic-lts-vivid when that exists
[13:45] <arges> hallyn: off the top of my head, not sure how the meta-packages get pulled in. 
[13:58] <apw> hallyn, i thnk those are coming from the main linux-meta package
[13:59] <apw> hallyn, and likely yes we would want to move those, when its not shiney and likely to eat peoples machines
[13:59] <apw> so once some time has passed for stabalisation
[14:10] <hallyn> apw: but so was linux-image-hwe-generic-trusty the right package for me to install?  i was on 3.13, which was killing kvm when i tried to nest;  just wnat the newest supported kernel
[14:56] <smb> hallyn, hm... maybe what you wanted would have a "utopic" in its name...
[14:56] <hallyn> smb: linux-image-hwe-generic-trusty points to something with utopic in its name
[14:56] <hallyn> is there a structure to these pkgs or is it all ad-hoc?  I assumed the former, am getting the feeling its the latter :)
[14:57] <smb> there is a structure but ... its maybe too complicated for me myself
[18:51] <lamont> smb: full shutdown and start later: /dev/vda1       41151808 13811620  25226756  36% /
[18:51] <lamont> ta
[18:52] <smb> lamont, yw. I hope this also magically avoids the swraid recovery affecting the guest
[18:52] <lamont> smb: that would be most lovely
[18:52] <lamont> and yeah, I have no desire to emulate disks if I can just use them
[18:52] <smb> I know ... :)