[00:10] <DirtyCajun> Anyone use tgtadm with vmware esxi hosts? I cant get vmware to recognize any kind of backing-store but a .img flat file made by dd. Direct disks (/dev/sdxxx) and luns (/dev/mapper/vg-1/lv-1) show the controller but no formattable space
[05:30] <cpaelzer> good morning
[05:31] <lordievader> Good morning
[05:31] <cpaelzer> hi lordievader
[08:41] <cperrin> Hey. I amtrying to install ubuntu server 16.04.4 on my Dell R515 and it just wouldn't work. I get the grub screen but after that it just doesn't display anything. It might be a problem with the graphics that I just can't see any thing. Is there an option for "simpler" graphics?
[08:42] <cperrin> Or maybe any other Idea. I see that the Server loads to image but then it just stops
[09:26] <blackflow> cperrin: remove "quiet nosplash" from the kernel command line from grub, see if you get any output from the system booting and with that any error listed.
[12:40] <rbasak> cpaelzer: on empty dirs in git-ubuntu
[12:40] <rbasak> What I've been doing is disabling the hooks but proceeding anyway
[12:41] <rbasak> In many cases the disappearing directory doesn't break anything because it's a 3.0 (quilt) package so gets effectively recreated (with a warning) by dpkg-buildpackage - because it doesn't end up in the debian tarball anyway, and the orig tarball doesn't get changed.
[12:41] <rbasak> So the only things that would be broken are your commits which won't contain the empty directory.
[12:41] <ahasenack> we just have to be careful if it's a new version, right? a new orig tarball
[12:42] <ahasenack> we need to be sure it is the pristine upstream tarball, and not one generated from the git repo
[12:42] <ahasenack> or not even that?
[12:42] <rbasak> In this case I don't think it actually breaks much except for final rich history adoption since the importer will see the mismatch
[12:42] <rbasak> Not even that
[12:42] <rbasak> I believe that the orig tarball will always match byte for byte.
[12:42] <ahasenack> the tarball we get will have the empty dirs?
[12:42] <ahasenack> when we build-source, for example
[12:42] <rbasak> Yes, because we effectively store the binary.
[12:42] <rbasak> (via pristine-tar)
[12:45] <cpaelzer> rbasak: oh I see, you say if the empty dir is not needed/touched by the commits then it doesn't matter
[12:45] <cpaelzer> because the build provess will correctly recreate it anyway
[12:45] <cpaelzer> with just tar+quilt
[12:45] <rbasak> cpaelzer: right
[12:45] <cpaelzer> rbasak: well then let me recreate what I wanted to send you as debdiff in git
[12:46] <rbasak> Only the importer will refuse to accept your upload tag unless you create that final commit with empty directories again (which the git CLI can't do)
[12:46] <rbasak> can't*
[12:46] <cpaelzer> rbasak: and I'll compare the dsc/changes
[12:46] <rbasak> cpaelzer: ack
[13:03] <cpaelzer> rbasak: ahasenack: yes it really is exactly the same debdiff
[13:03] <cpaelzer> ok, then I can MP propose this as well
[13:03] <cpaelzer> \o/
[13:03] <ahasenack> I wouldn't expect the debdiff to chang
[13:03] <ahasenack> e
[13:04] <ahasenack> I was worried about launchpad complaining about a hash mismatch with the orig tarball
[13:04] <cpaelzer> ahasenack: the orig tarball was not touched
[13:04] <cpaelzer> since it doesn't regenerate it but uses it as it has found it on publish
[13:52] <pankaj_> While installing ubuntu server i was unable to comnect and configure network as i was dual booting. But now how to configure my network especially wifi via terminal. Please help
[14:18] <RoyK> pankaj_: try "ip link list" to see if the nic is available
[14:19] <Ussat> dual booting....
[14:19] <RoyK> what about it?
[14:53] <Ussat> There are better things in life than dual booting, like VM's
[16:06] <nacc> what does dual booting have to do with being able to connect to the network?
[16:25] <RoyK> nothing
[18:40] <sarnold> nacc,RoyK, well.. I had a laptop once that couldn't use wireless until you booted it into os x or windows. (I can't remember which laptop that was. I just remember the annoyance.)
[18:40] <sarnold> once the drivers had been updated in the first os then they'd work in linux..
[18:45] <nacc> sarnold: you mean every time?
[18:45] <sarnold> nacc: no, just the once
[18:46] <sarnold> thank goodness :)
[18:46] <nacc> sarnold: ah interesting. so some proprietary logic, i guess?
[18:46] <nacc> sarnold: i wonder if you did some acpi hack if it would 'just work'
[18:48] <sarnold> nacc: my guess was it was just lackinga  firmware, and hopefully the linux-firmware package would have taken care of it
[18:51] <nacc> sarnold: ah could be
[18:52] <sarnold> it was either a g3 ibook or a lenovo z60? iirc a p4m machine ..
[22:38] <jaddison> Hi! looking forward to settling in on 18.04... having a networking problem though. I don't use sleep/hibernation, so it's not related to that.  When I reboot (or boot up after shutting down), the ubuntu does not get an ipv4 address. if I manually run `sudo dhclient` it gets one just fine. Upon reboot it is lost, however.
[22:39] <jaddison> netplan is configured - in fact, the ip address worked fine for a few reboots, then stopped automatically working.
[22:39] <dpb1> jaddison: can you pastebin the files in /etc/netplan/* ?
[22:39] <dpb1> !pastebin
[22:40] <jaddison> https://paste.ubuntu.com/p/RKdyMpqF2d/, dpb1
[22:41] <jaddison> It was originally `optional: true`
[22:41] <cyphermox> what does networkctl say there?
[22:41] <dpb1> jaddison: remove addresses:
[22:41] <dpb1> (I don't think that is causing it, but it's not needed)
[22:41] <sarnold> cyphermox: should I be worried that systemd-networkd isn't running on my laptop?
[22:41] <dpb1> sarnold: no, there you should be using networkmanager
[22:42] <sarnold> dpb1: cool, thanks :)
[22:42] <cyphermox> sarnold: cosmic?
[22:42] <sarnold> cyphermox: bionic
[22:42] <jaddison> cyphermox https://paste.ubuntu.com/p/jZDBTgTYqT/
[22:42]  * dpb1 wonders if something changed in cosmic...
[22:42] <cyphermox> you probably still ought to have networkd running..
[22:42] <sarnold> p3 vs p2?
[22:43] <jaddison> sarnold me? yeah, I just noticed that. No idea how that happened though?
[22:43] <cyphermox> jaddison: did you change the hardware for that system?
[22:43] <jaddison> cyphermox no.
[22:43] <jaddison> wait, what do you mean?
[22:43] <cyphermox> changing network card
[22:43] <jaddison> I plugged in another GPU after it all
[22:43] <sarnold> did you move the NIC?
[22:43] <jaddison> surely that wouldn't do anything
[22:43] <cyphermox> could be that
[22:43] <jaddison> no
[22:43] <jaddison> it's onboard nic
[22:44] <jaddison> so ubuntu/netplan can't adjust if hardware is moved? that doesn't sound quite right... :)
[22:44] <cyphermox> you mean networkd/udev
[22:46] <cyphermox> but essentially, yeah, the issue is that the netplan yaml expects to configure p2, but the device is p3
[22:47] <jaddison> cyphermox but I don't understand how it got into that state. Is this something that might happen again in future? I literally installed the box got it running fine, then added a GPU (I *think* that was the trigger?) then it all fell apart
[22:48] <cyphermox> it's a little odd that adding a GPU would cause that, but it's plausible, the p there stands for which numbered bus the device is on
[22:49] <cyphermox> jaddison: only when you change hardware, this is dependent on what buses are scanned in what order, but the ordering won't change
[22:49] <cyphermox> I don't expect it would change again even if you changed the GPU
[22:49] <dpb1> jaddison: a more reliable naming scheme *could* be for you to use mac address matching to id the card you want.
[22:50] <dpb1> jaddison: https://netplan.io/examples#vlans -- look at the mainif, 'match:' stanza
[22:50] <jaddison> cyphermox, dpb1 so, if I don't move hardware around in future for this box, I won't see this problem, most likely?
[22:50] <cyphermox> right
[22:50] <jaddison> dpb1 thanks, that's interesting.
[22:50] <dpb1> yup
[22:50] <jaddison> cyphermox ok, thanks (you too dpb1)
[22:51] <jaddison> I'm back in the saddle, folks!
[22:51] <cyphermox> jaddison: if it's a desktop, you're also not likely to have many more buses for new things to appear if you add/remove hardware ;)
[22:52] <cyphermox> jaddison: dpb has a good point, you could add a match:  for the mac address of the device and rename it to something else, that way the name will never change
[23:14] <blackflow> I've seen this happen. Remove/add a GPU and netif changes name.