[00:05] phillw, it would be best if you could open a launchpad bug, so we can track all the appropriate information. You can open a bug using a web browser on any system(It doesn't have to be the system exhibiting the bug). Again, just go to the following link: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug [00:06] Any system with Internet access that is. [00:07] jsalisbury: my VM does not want to to play...... [00:10] jsalisbury: where do you need me to pull logs from? as it is a KVM I can pull any data you need. [00:14] phillw, the following commands will collect all the appropriate data: [00:14] 1) uname -a > uname-a.log [00:14] 2) dmesg > dmesg.log [00:14] 3) sudo lspci -vvnn > lspci-vvnn.log [00:14] 4) cat /proc/version_signature > version.log === emma_ is now known as em [00:15] phillw, what happened after you ran: apt-get install linux-generic [00:21] jsalisbury: there seems to have been a drop of support for kernel (and motu). We do have people who want to make community re-spins but some of the tools that they used are no longer there. [00:22] jsalisbury: Hi Joe, this is the last I got from the VM [00:22] root@amjjawad:/home/ali/src/linux-3.13-rc8# make oldconfigscripts/kconfig/conf --oldconfig Kconfig [00:22] # [00:22] # configuration written to .config [00:22] # [00:22] root@amjjawad:/home/ali/src/linux-3.13-rc8# [00:23] root@amjjawad:/home/ali/src/linux-3.13-rc8# apt-get install linux-generic [00:23] Reading package lists... Done [00:23] Building dependency tree [00:23] Reading state information... Done [00:23] linux-generic is already the newest version. [00:23] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [00:23] root@amjjawad:/home/ali/src/linux-3.13-rc8# [00:25] phillw, Are you now running the 3.13.0-3-generic kernel (After a reboot) ? [00:27] jsalisbury: the VM I'm working with is Linux amjjawad 3.13.0-3-generic #18-Ubuntu SMP Mon Jan 13 19:11:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [00:27] my machine is phillw@piglet:~$ uname -a [00:27] Linux piglet 3.13.0-3-generic #18-Ubuntu SMP Mon Jan 13 19:11:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [00:30] phillw, ok, to summarize, you upgraded a server flavor from Precise running the 3.8 backport kernel to Trusty, but the kernel remained at 3.8. But you were able to upgrade to 3.13.0-3-generic manually? [00:31] I did a -d to ask the server to jump to 14.04. [00:31] jsalisbury: correct === cwillu_ is now known as cwillu [02:46] jsalisbury: As it turns out, rtg just fixed that bug. :P [07:13] TGIF [09:26] * apw yawns mightily [09:27] I am sure RAOF has mighty AUS BEEEES === mwhudson is now known as zz_mwhudson [09:40] who stole my bees? [09:41] * apw notes .au does have above average bees [10:36] hey apb1963 [10:36] i mean apw [10:36] are you around [10:36] apw: i stole them i forgot to tell you [10:36] lol [11:59] Sarvatt, was it you i was talking to about the gm45 "character square corruption" which looked like fence issues? [11:59] Sarvatt, as i have just upgraded userspace from S to T and it has gone away now [12:56] Sarvatt, though the tearing is appaling in chromium [12:57] apw: finally got a reply to the email about the multitouch track pad [12:58] apw: and the response is You mean that one? http://www.spinics.net/lists/linux-input/msg26869.html It never got applied, would be nice to hear whether that bug still exist and have it resubmitted. Thanks David [13:21] eagles0513875, sounds like movement, was the original submitter on the thread, if not maybe time to poke them [13:22] the patch has a lot of questions you might hope that the maintainers would reply on [13:22] apw: the original submitter i think is MIA [13:22] but ... seemingly not [13:22] i dunno if you could step in or not [13:24] it is very hard to own a patch when you don't have the h/w to test changes on [13:25] apw: i can test it but I have no idea what i would need to do to patch the kernel and recompile [13:25] well i have a site on how to do that but not sure how to go about it [13:26] apw: Would you be willing to help me out in this regard or am i a bit on my own [13:40] eagles0513875, we may have a amchine with the same h/w will investigate [13:40] apw: thanks I would though like to apply the patch for now to my existing kernel on 13.10 [13:41] apw: going to update the bug from the response i got in the email [14:07] eagles0513875, canyou confirm this is a lenovo L530 [14:08] im not on a lenovo [14:08] im on a toshiba sattelite s75-A7221 [14:08] and you know htat patch fixes your issue ? [14:11] eagles0513875, ^^ [14:12] apw: i need help patching the existing kernel to test it as i dont know how to patch my kernel as well as recompile it [14:19] apw: would it be possible for you to provide a testing kernel somewhere for me to install and test [14:35] eagles0513875, is there a bug number for this? [14:36] apw: for the upstream bug [14:36] the only bug i have is the launchpad one linking to the discussion upstream previously [14:38] which is which one [14:40] apw: this is upstream http://www.spinics.net/lists/linux-input/msg26869.html [14:41] on launch pad its bug 967399 [14:41] Launchpad bug 967399 in linux (Ubuntu) "[11.10] Elantech trackpoint does not work Lenovo " [High,In progress] https://launchpad.net/bugs/967399 [14:49] smb, have you been running trusty kvm sessions lately ? I just upgraded from 12.04.2 to trusty and it appears to have wedged. [14:50] rtg, KVM installs only not upgrades [14:50] smb, hmm [14:50] I mean Trusty server installs [14:51] smb, right, thats all I'm doing to [14:51] guess I'd bettercheck that the daily works [14:51] rtg, You are using a raid1 by chance? [14:51] nope [14:52] Ok, that was one piece that has issues currently. Otherwise my installs were using a daily iso from the 15th [15:03] (15:00:07) phillw: hi, do we expect the bug that does not use the 3.13 kernel as a an upgrade from 12.04 LTS? [15:06] aka, when updating from 12.04 lts, we do not get the kernel release for 14.04 [15:06] phillw: O_o not like you to be in here [15:07] eagles0513875: the people here are proffessional. [15:07] i know im working on getting a multi touch track pad issue solved [15:07] I need them to to fix an issue [15:10] eagles0513875: joe salisbury is afk, as is bodhi-zazen.... I'm stuck until the kernel team fix it :) [15:10] phillw, no we expect something upgraded to use the correct kernel [15:11] apw [15:11] apw: how should i proceed with the issue of the multitouch track pad? [15:11] apw: it did not.... how do I fix it? [15:12] phillw, if it was an update-manager update then (unintuitvly) the thing to do is to file a bug against update-manager and say "yes" to the during an update from a previous release [15:12] it's really good to catch this error so early :) [15:12] as that gets the appropriate logs from the update [15:13] apw: the VM is non GUI.... so I cannot file a bug :( [15:13] eagles0513875, we need to find out that this patch even has a thing to do with your issue, which would mean i need to spin a kernel (as you don't seem to be able to), and that'll happen when i get to it [15:13] phillw, you can file a bug, its just harder [15:13] apw: if you can give me the steps on what i need to do I can do it [15:14] phillw, iirc you can just do the same thing, and it uploads it and then gives you the URL for it to continue on another machine [15:15] apw: the VM is there... tell me what you need & I will do it. Just recall that I am a tester not a coder and you will have to give me step by step instructions. [15:15] if you need step by step instructions, he may as well just do it himself [15:17] ikonia: i just really need help with patching. if http://www.howopensource.com/2011/08/how-to-compile-and-install-linux-kernel-3-0-in-ubuntu-11-04-10-10-and-10-04/ works then i can follow those instructions to apply [15:17] compile* [15:17] ikonia: I have offered them root access to the VM. More than that I cannot do :) [15:17] phillw, "ubuntu-bug update-manager" should work GUI or not [15:17] phillw, i think ikonia was talking to eagle [15:18] eagles0513875: I'm missing background here - but what kernel version are you trying to build ? [15:18] ikonia: the one that comes with 13.10 [15:18] forget that that article is for older kernels and release. are the steps to compile it the same? [15:18] if you arn't confident building it then a negative test will not be conclusive anyhow [15:18] ok [15:19] ikonia: I'm building the kernel for 14.10 [15:19] phillw: so ? [15:19] sorry... 14.04 [15:19] apw: ill leave it in your hands [15:19] phillw: i think that was directed at me btw [15:20] eagles0513875: is there a bug logged for this ? [15:20] eagles0513875: that communities can not make respins is an issue. [15:20] communities can make respins [15:20] ikonia: my issue has nothing to do with what phillw is doing [15:20] who said they can't ? [15:21] ahh [15:21] wait a min we are on two different wave lengths here [15:21] I'm missing background/context for both issues [15:21] ikonia: my issue is relating to my multitouch track pad on my laptop [15:21] i found https://launchpad.net/bugs/967399 [15:21] Launchpad bug 967399 in linux (Ubuntu) "[11.10] Elantech trackpoint does not work Lenovo " [High,In progress] [15:21] ikonia: https://answers.launchpad.net/ubuntu/+source/debian-cd/+question/240037 [15:21] and this laptop has an elantech multitouch track pad but that bug is geared specifically for lenovo so I was wanting to patch my kernel to see if that fixes my track pad not working at all. [15:22] eagles0513875: is that your exact bug ? [15:22] btw apw thanks for offering to compile a test kernel with the patch [15:22] ikonia: yes that my track pad doesnt work at all right now. [15:22] phillw, when something is hard to do, that doesn't make it easy to document, cd creation is such a beast, it has evolved over some 12 years [15:22] eagles0513875: ok - so it's the same bug but on version 13.10 ? [15:22] correct [15:23] eagles0513875: ok, cool, so the bug is valid. [15:23] eagles0513875: so where are you getting the patch from ? [15:23] the bug [15:23] there is one as well as a diff [15:23] ikonia, though this bug is for a lenovo, and that isn't what he has [15:23] what ??? [15:23] the patch isn't even for the 13.10 kernel [15:23] the patch is for a lenovo lapto mine is a toshiba [15:23] eagles0513875: why are you talking to upstream ??? [15:23] apw: I do have people to help.... what is needed is kernel for server edition to up grade to the 14.04 edition (3.13) [15:23] what the debvil..... [15:24] apw asked me to see what happened to it as it had initially been filed upstream for inclusion into mainline [15:24] and basically the last comment i got today about it. [15:24] eagles0513875: so what is the model of track pad you have ? [15:24] how would i check that [15:25] you don't even know the model ??? [15:25] you're assuming the lenovo track pad has the same model as yours and the lenovo patch will fix it [15:25] phillw, and hopefully the log as to why the upgrade didn't complete will be in the logs from the bug you're filing with the ubuntu-bug command [15:25] apw: I cannot file a bug :( [15:25] eagles0513875: how are you following bugs looking at patches, when you don't know the model of the hardware that's failing ???? [15:26] apw: it is a server with no X [15:27] you can manually look at the logs ? [15:27] log the bug manually on launchpad.net ? [15:28] phillw, you do not need X to file a bug, i just did it here by doing a DISPLAY= ubuntu-bug ... and it does it all in ascii [15:28] did you even try it ? [15:29] ikonia: i found out how to determine which track pad i have but not the model [15:30] ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=11 [slave pointer (2)] [15:34] apw and what is the name of the bug you want? [15:35] ubuntu-bug update-manager [15:35] and say Yes to the "during an upgrade from a previous release" prompt [15:38] runnig [15:39] apw: The collected information can be sent to the developers to improve the [15:39] application. This might take a few minutes. [15:39] ..==== AUTHENTICATING FOR org.freedesktop.policykit.exec === [15:39] Authentication is needed to run `/bin/cat' as the super user [15:39] Multiple identities can be used for authentication: [15:39] 1. ali,,, (ali) [15:39] 2. Jason,,, (jason) [15:39] 3. eagles,,, (eagles) [15:39] 4. Kris,,, (kris) [15:39] 5. bipul [15:39] 6. dan [15:39] Choose identity to authenticate as (1-6): ................ [15:40] eagles0513875: you're on shacky ground [15:40] eagles0513875: it seems a very random approach [15:40] ok [15:40] i guess ill just wait it out. for apw [15:41] eagles0513875: I would try to get some factual information together [15:41] eg: your hardware make/model - the hardware make/model that this patch fixes/support would be a good start [15:41] before pushing/wasting peoples time for tests [15:41] do you even known if it uses the same module to drive the touchpad as this bug ? [15:41] ok. thing is the bug doesnt specify which elantech model it fixes either [15:42] eagles0513875: right - so you finding out would be a good start [15:42] ikonia: that is why im asking for help to patch my kernel [15:42] to test and see if it truly does fix the issue. [15:42] eagles0513875: why are you patching the kernel when you don't know the scope [15:42] eagles0513875: you're running before waling [15:42] walking [15:43] how am i supposed to determine the scope by looking at the patch and determining my model? [15:43] eagles0513875: do you have a profile at https://wiki.ubuntu.com/QATeam/Hardware ? makes life a lot easier to the devs :) [15:43] phillw: no [15:43] eagles0513875: then do it :) === awe_ is now known as awe|afk [15:43] eagles0513875: a good basic check would be "what is the target kernel that patch is aimed at" [15:44] eagles0513875: that patch maybe for 3.1.8 - and the changed between 3.1.8 and 3.1.12 make it useless [15:44] from the looks in the bug report 11.10 [15:44] im guessing what ever kernel was on that [15:44] eagles0513875: right, so quite old - so probably not going to be targeting / compatible with the same kenrel you are using [15:45] 3 years is a long time [15:45] a lot gets changed in 3 years [15:45] ikonia: if that is the case besides filing a bug report with all the appropriate bug information [15:45] ? [15:45] apw: I have no idea what it is up to..... [15:46] ikonia: what i need to do is file a bug report against 13.10 instead [15:46] with the version of my track pad in that case [15:46] yeah, I think that's a good thing to do, reference the other bug if you want, but a lot has changed [15:46] try to get solid factual information though [15:46] nothing half hearted or guessed, facts only [15:47] eagles0513875: have a read of https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs [15:47] why are you giving him an installer bug link ? [15:47] I thought this was a problem after the install, with the running OS [15:48] phillw: O_o not sure what that has to do with anythign im experiencing plus im not on 14.04 [15:48] ikonia: do you mind if we take this discussion back to kubuntu [15:48] no problem at all [15:48] phillw: I'd suggest focusing on your own problem [15:48] eagles0513875: I give people all options. [15:48] you give bad information [15:48] that is random and not helpful [15:48] so I'd sugget focusing on your own problem only [15:50] ikonia: that, my friend, is something I do not give.... a bug is a bug, the dev's need what is available. Having the the hardware is always handy :) But, we will not fall out @P [15:51] you're giving bad information and bad links to people, please don't [15:51] focus on your own bug please. [15:54] ikonia: I'd like to query as to a link given that is run by a canonical person can be seen as you as a bad link? https://launchpad.net/~nskaggs [15:55] for the exact reasons I said earlier [15:55] it's nothing to do with the installer [15:55] he's not running 14.04 [15:55] seems pretty clear giving a link to installer bugs for non-installer problems is "bad" [15:56] ikonia: and I didn't know that... as to how updates break installed systems is "bad" :) [15:56] sorry, I don't understand your last statement [16:14] ikonia: I'm chatting with eagels, chatting on two channels does get confusing! I'm awaiting the fix to have the 3.13 kernel installed onto 12.04 lts :) Please do not take my frustrations personally, it is just somewhat frustrating at times :) [16:17] phillw, earlier you said you were upgrading this machine and didn't get 3.13, are you saying you are doing 'update' of 12.04lts and expecting to get the 3.13 kernel [16:18] apw indeed, i expected an lts to lts upgrade actually bring the new kernel :) [16:19] phillw, so the machine is now running 14.04 yes? [16:20] (just confirming that that is right, as that makes the bug i asked you for the right thing) [16:21] eagles0513875, ok a saucy kernel with that patch applied is here: http://people.canonical.com/~apw/lp967399-saucy/ [16:21] thanks apw :) will give it a try [16:23] apw: you know something... I've got lot a lot of apologising and self kicking to do.... although reminding us in upgrades that we need to reboot twice instead of trying to remember. :D [16:24] one doesn't need to reboot twice in an upgrade, i just did one on my other computer, S->T not half an hour ago, and only rebooted once [16:25] apw I had to on the KVM virtual machine [16:26] that may be an artifact of the way the kvm images are maintained there, not something i have seen on any of mine [16:27] it *may* be worth a release note for any server people running kvm.... but is more a #ubuntu-server issue. I'm only here to build the non-pae 13.03 kernel :) [16:27] phillw: I told you yesterday that the upgrade from a non-3.2 kernel wouldn't upgrade you to 3.13, and told you how to work around it. [16:27] phillw: As it turns out, rtg fixed that bug last night, so it should work now. [16:27] phillw: I'm not sure why you're still talking about this. [16:28] infinity: i was aware the the bug was in progress, and then got asked to raise a bug...... [16:28] Where's the bug you filed? [16:29] infinity: I was still in the process of trying to file it! the server is cli and has sat for 60 minutes '''collecting data''' [16:30] smb, just installed the trusty server amd64 daily. same result. gets stauck right after /scripts/init-bottom [16:30] phillw: Okay, or you could not file it. Since the bug is "there's not path for precise+lts-backport upgrades to to 14.04" and, like I said, this was (a) a known bug, and (b) fixed 6 hours after you tripped on it. [16:30] rtg, weird... [16:31] I wonder why it would boot the installer.... [16:33] infinity: if the bug is fixed, no need to report... unless some one wants bug fixing points :P As I have the VM with 3.13 I can use it to build the non-pae kernel. To the other wonderful people on here, a massive thank-you. [16:35] phillw: Is this just a one-time kernel build for yourself, or something you're hoping to upload to the archive? [16:35] phillw: Cause as I've told many people, many times, I won't accept a non-pae kernel in the archive without it also coming with a (believable) statement of support intent, like I have for lowlatency. [16:35] infinity: it is going to be a 14.04 lts kernel for any flavour that needs it. [16:35] phillw: Throwing a rotting corpse of an unmaintainer kernel in the archive so people can have unpatches security holes on their old hardware isn't a win. [16:36] phillw: It is, is it? According to whom? And who will maintain it? [16:36] s/unmaintainer/unmaintained/ [16:36] phillw: Who's going to rebase it against master every 3 weeks? [16:36] phillw: Who's going to test those rebases to make sure they still boot and work? [16:37] phillw: Since I'm pretty sure this isn't you, who are yo uvolunteering to do work that they didn't sign up for? [16:38] infinity: "we" the people will maintain it. on http://phillw.net/isos/ and as bodhi-zazen has agreed to teach us http://bodhizazen.net/Tutorials/kernel we are secure in how we support this. [16:40] infinity: https://answers.launchpad.net/ubuntu/+source/debian-cd/+question/240037 what you seem to forget, is that with some help... communities can co-ordinate and make spins. [16:40] phillw: If this isn't going to be in the primary archive, you can do whatever you like. [16:42] infinity: the kernel will be in a ppa (so I'm told) and any community can use it as a build / update area. I've now to build my first kernel :) [16:42] smb: rtg: i think we are seeing the same issue that you are discussing, today's trusty server installs being broken... just confirming if it helps [16:43] psivaa, change your display from cirrus to vga [16:43] psivaa, Turns out broken means only that in kvm the default cirrus card causes framebuffer issues [16:43] psivaa, The guest gets up just the screen stops getting updated [16:44] smb: I'm sure we discussed this last night? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674 [16:44] Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed] [16:45] smb: rtg: ok, just to confirm... does that tally with the following log: [16:45] Jan 17 07:32:43 anna[8496]: corrupted status flag!!: 0 [16:45] Jan 17 07:32:43 anna[8496]: (process:10447): tar: write error: No space left on device [16:45] Jan 17 07:32:43 anna[8496]: (process:10447): tar: write error: No space left on device [16:45] psivaa, No that rather sounds obviously like disk too small? [16:46] smb: no disk size is no different to what we used yesterday, 8G [16:46] rtg: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/comments/43 [16:46] Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed] [16:46] phillw, No it is not. That is an x driver bug [16:47] okies :) [16:47] rtg, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401 [16:47] Launchpad bug 1269401 in linux (Ubuntu) "[Trusty] Switching framebuffers fails on VMs using cirrus" [Medium,Confirmed] [16:57] jjohansen, bug #1270215 looks like an AA issue, e.g., trusty LTS prevents dhclient from running. [16:57] Launchpad bug 1270215 in Ubuntu "kernel 3.13.0-4.19~precise1-generic: no internet" [Undecided,New] https://launchpad.net/bugs/1270215 [17:16] what should I try next on this?: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269986 [17:17] Launchpad bug 1269986 in linux (Ubuntu) "kernel oops - unable to handle kernel NULL pointer dereference; probe_monitoring_device / nouveau_i2c_identify" [Undecided,Confirmed] [17:26] rtg, shall I hold off on bisecting bug 1270215 ? since it may be an AA issue? [17:26] Launchpad bug 1270215 in linux (Ubuntu Precise) "kernel 3.13.0-4.19~precise1-generic: no internet" [High,New] https://launchpad.net/bugs/1270215 [17:27] jsalisbury, yeah, it'll be a waste of your time. lets get jjohansen to look at it first. [17:27] rtg, ack [17:38] jsalisbury, However, bug #1270218 looks like a good bisect candidate. [17:38] Launchpad bug 1270218 in linux (Ubuntu) "3.13.0-4-generic [Radeon HD 7950] No Display at Login Screen" [Medium,Confirmed] https://launchpad.net/bugs/1270218 [17:39] rtg, heh, looking at that one right now :-) [17:39] there just weren't that many commits between -3 and -4 [17:40] rtg, looks like it was introduced between v3.13-rc8 and commit 85ce70f [17:40] yup [17:41] rtg, although there were a few branch merges [17:41] apw: trying to install the kernel headers and its complaining about missing dependencies [17:48] rtg, Should be a quick bisect, I'm guessing it's one of these: [17:48] git log --pretty=oneline b25f3e1c358434bf850220e04f28eebfc45eb634..85ce70fdf48aa290b4845311c2dd815d7f8d1fa5 -S radeon [17:48] f244d8b623dae7a7bc695b0336f67729b95a9736 ACPIPHP / radeon / nouveau: Fix VGA switcheroo problem related to hotplug [17:48] 59aebe2b32466f7ed5b79f18646be6dddc926a6d Revert "drm/radeon: Implement radeon_pci_shutdown" [17:48] 9c57a6bd3ea4a9870a7ce2fd961da6ef4986bbc1 drm/radeon: add radeon_vm_bo_update trace point [17:48] 84d597b74b58dd52621abf5f052a81370ace1816 drm/radeon: add VMID allocation trace point [17:48] ec39f64bba3421c2060fcbd1aeb6eec81fe0a42d drm/radeon/dpm: Convert to use devm_hwmon_register_with_groups [17:48] jsalisbury, seems likely [17:54] hmm, the kernel apport hook should probably have /var/log/kern.log in it so it doesn't just have the successful boot dmesg attached like that bug [17:58] Sarvatt, doesn't bdmurray own apport ? [18:00] rtg: that's pitti but I work on it some [19:11] apw: sadly that didnt fix the problem for me :( [20:13] BenC, from LKML: Kernel stack overflows due to "powerpc: Remove ksp_limit on ppc64" with v3.13-rc8 on ppc32 (P2020) [20:15] rtg, nice catch ... [20:15] apw, just drifting thru LKML... [20:16] we do rely on it :) [20:16] hopefully it'll pop out for 3.13 final [20:17] rtg: yep 1270215 looks like a policy issue [20:17] jjohansen, ack [20:27] bjf, from LKML: 'Baytrail problems (was Re: Linux 3.13-rc8)' talks about a stable patch that might give you fits. [20:35] ARGH! [23:30] sforshee: https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/