=== Guest80711 is now known as med_ === Lcawte is now known as Lcawte|Away === inteus_ is now known as inteus === Metacity|uh-oh is now known as Metacity === ^King is now known as test1234321 === test1234321 is now known as ^King === devil is now known as Guest57800 === Guest57800 is now known as devil_ === devil_ is now known as devil__ === devil__ is now known as devilz === jelly is now known as this === this is now known as Guest37927 === Guest37927 is now known as jelly === coreycb` is now known as coreycb === Monthrect is now known as Piper-Off [09:38] Good morning. === Lcawte|Away is now known as Lcawte [11:19] hello, my ubuntu 14.04 has kernel version 4.2.0.27.21 from "linux-image-generic-lts-wily" is this the one with vulnerability fixed? === cpaelzer_ is now known as cpaelzer_afk [11:53] Ergo: which particular vulnerability? [11:54] Ergo: if you know the CVE ID, http://people.canonical.com/~ubuntu-security/cve/ [11:54] sadly not all kernel issues with security consequences get CVE assigned (says spender) [12:08] jelly: thanks, I've actually found the CVE and confirmed the version, all is good === devil is now known as Guest84073 === warraymos_alt is now known as warraymos === lordieva1er is now known as lordievader === Guest84073 is now known as devil_ === cpaelzer_afk is now known as cpaelzer_ === `jpg_ is now known as `jpg === Piper-Off is now known as Monthrect [14:05] Anyone know anything about cloud-init here? I have this cloud-init file: https://gist.github.com/hagbarddenstore/bd68e0ebd8944c99b147 I use Ubuntu 14.04.3 (ami-f95ef58a). The error I get is that /tmp/my-key can't be found (By the ssh command in the runcmd), so my guess is that either I have wrong permissions or that write_files is executed after runcmd. Is this the case? This post ... [14:05] ... http://blog.scottlowe.org/2015/12/17/cloud-init-register-instance-into-consul/ suggests that I can do what I'm trying to do, but I simply can't get it to work. [14:06] Also, write_files with owner: ubuntu:ubuntu or path: /home/ubuntu/file will make cloud-init crash and burn, resulting in a server that you cannot access, [15:18] hi folks [15:20] http://pastebin.com/M46a5i60 === cpaelzer_ is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer_ === cpaelzer is now known as cpaelzer_afk [18:37] Do the official vagrant images at http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box not support shared directories? [18:37] also, wow, the topic hasn't been changed in almost 2 years [18:39] I've seen older :) [18:39] should I use the ones at https://atlas.hashicorp.com/ubuntu [18:42] https://atlas.hashicorp.com/ubuntu says "Official Ubuntu Server Wily Werewolf (development) builds" [18:42] I guess wily isn't in development any more [18:44] fwiw I'd only use those images if they match the published signatures [18:44] but that's me [18:52] thanks for the tip [18:53] I guess the conclusion is that the official Ubuntu Xenial images for Vagrant don't actually work with the Vagrant [18:53] no idea, what's a shared directory? [18:53] sarnold: have you used vagrant before/ [18:53] jml: no [18:53] ok [18:54] jml: I've always heard it's some scriptng around virtual box, and i'm .. not inclined to use oracle code when there's good alternatives like kvm / qemu available :) [18:54] Vagrant fires up a VM (generally using VirtualBox) and does a bunch of automatic configuration on that VM to make it work nicely, optimized for development environments [18:55] a key step is mounting a directory from the host (the one where `Vagrantfile` is) onto the guest at `/vagrant` [18:55] that way, you can edit files directly from the editor on your guest without having to manually sync [18:56] aha [18:56] how do they do that? p9fs? nfs? [18:56] some virtio thing? [18:58] https://gist.github.com/jml/220163e18f88edb87976 [18:58] a custom kernel module [18:58] well, custom filesystem, I should say [18:58] wow that seems surprising compared to the alternatives [18:59] thanks jml :) [18:59] yeah, you'll have to ask them. [18:59] anyway, I'm falling back to the "development" wily image that was released on 201601 === rcj` is now known as rcj [21:26] Daviey: hi, you opened RT 16371 a looong time ago. Can it be closed? [21:59] good afternoon. is anyone here using ubuntu server to manage their Clonezilla/DRBL instance? [21:59] celly: how is your failing clonezilla image anything to do with ubuntu [21:59] I asked you just a few minutes ago to not spread this across the ubuntu channels [22:00] i never said it was an ubuntu issue, but with so many people using ubuntu server, i thought maybe, just maybe, someone that might be using ubuntu server for Clonezilla and DRBL might actually be willing to help. [22:01] also, you "suggested" that i didn't ask it in the ubuntu-server channel, you didn't ask me not to do so. if no one helps, then i'll obviously leave it alone. [22:01] celly: and as I told you - just because the clonezilla channel is dead, it's not up to the ubuntu channels to pickup the slack === cpaelzer_afk is now known as cpaelzer [22:03] how is me asking one question affecting you? If someone has some insight, i'm sure they'll respond. if all you're going to do is continue to say, "it's not an ubuntu issue", then what help is that. as i stated, i obviously know its not an ubuntu issue, but considering ubuntu is one of the most used linux distro's and one of the primary supported OS's for clonezilla, what harm does asking a question do? [22:04] and FYI, the ONLY reason i asked the question in the ubuntu channel to begin with is because someone stated that the people in there would possibly help. had someone not said that, i wouldn't have asked [22:05] ok, well please take it back to the clonezilla channel, thanks === sivir_ is now known as sivir === TREllis_ is now known as TREllis