| donofrio | What do you good folks think? "Using Ubuntu on Windows is safer than Ubuntu on Linux." - Page 46 - http://www.alex-ionescu.com/publications/BlueHat/bluehat2016.pdf | 02:39 |
|---|---|---|
| donofrio | in reagrds to WSL | 02:39 |
| sima | donofrio, you can also use Linux binaries on Joyent's Triton cloud (SmartOS) on illumos. And on FreeBSD. And where else. | 03:02 |
| sima | "Safety" is not bought by weight on market, actually, Safety is a product of many choosing and decisions and operative things one does in setting things up including procedures. And using "MS Windows" in any way, since it's inception as a proprietary product is not safe for a company in the first place. | 03:04 |
| sima | There are examples, where using proprietary platform and depending on their updates (that bring various bugs) actually can be a show-stopper and hurt companies. They are actually black-box products. I for example waited for 6 months or so , for (advertised!) NFS mount support in Win10Pro to start actually working and I think even today it has problems. For free software OS, it allows you to compile your own fixed thing and use it in | 03:07 |
| sima | meantime.. | 03:07 |
| sima | No to mention, it allows you to grow in abilities, learn and be independent (and provide better support for others) then just using some proprietary black-box. | 03:09 |
| sima | Not saying, that paying support should not be done, but as a contrast to "licensing" without support, and paying actual support for actual support service for free software distros, brings much more value to the free software side. | 03:14 |
| sima | And actual "running binaries" is a wrong concept. On Linux distros, binaries are often recompiled to fit distro. Not the other way around , where they see "binaries" as unchangeable bricks. You have the source, baby :) | 03:15 |
| sima | But yes, linux binaries (at least for long support kernel) are slowly changing and standardizing , that brings me back to Triton's solution. But on LInux binaries side, supporting forever some unchanged "binaries" is a more or less brain dead "solution" in the essence. | 03:17 |
| donofrio | tnx | 03:35 |
| hifi | hey, xubuntu looks lika a fairly polished xfce setup but the indicators bother me, for bionic there's still duplicates in the notification area from different sources, I assume it's known and someone's working on the defaults to remove them but just wanted to note that it's one of the few things that looks a bit off | 05:28 |
| hifi | otherwise I've been using bionic for quite some time now and no major issues | 05:29 |
| xangua | You can just remove the indicators applet and leave only the classic notification one (or otherwise) | 05:41 |
| hifi | xangua: I know but it's one of the things that looks unpolished when the defaults look "duplicated" for the end user | 05:49 |
| flocculant | hifi: we're aware of it :) | 05:49 |
| hifi | +1 | 05:49 |
| hifi | what would be the best place to report a bug with the modesetting xorg driver with intel gpus? after resuming and unlocking my session the screen goes blank, vt switching works but xorg remains completely blank, using the 'intel' xorg driver fixes that, I find it odd the screen locker works fine | 05:51 |
| flocculant | hifi: do you have indicator-application installed? if so you could try removing that - we're still using indicator applet for indicator-messages | 05:52 |
| flocculant | hifi: ubuntu-bug <package> | 05:52 |
| hifi | I doubt it can be fixed until bionic ships, unfortunately, it will affect at least X200 series of thinkpads which will likely annoy a lot of people :) | 05:53 |
| flocculant | hifi: possibly - but otoh it might be on radar - at that level it's not Xubuntu but everyone | 05:55 |
| hifi | it's weird the screen locker works, xubuntu is using lightdm as the locker, right? does it do any xrandr magic after unlocking a session? | 05:56 |
| flocculant | using light-locker, not sure about any magic | 05:57 |
| hifi | https://bbs.archlinux.org/viewtopic.php?id=231698 maybe I'm not that far off | 05:58 |
| hifi | need to check with xrandr if it just disabled the only internal display after unlock with the modesetting driver | 05:59 |
| hifi | would at least be nice to know which package I'd need to file the bug against | 06:00 |
| flocculant | hifi: I'd likely start with xorg | 06:00 |
| flocculant | anyway - got to go now - work unfortunately beckons | 06:01 |
| hifi | anyway, great work with xubuntu overall, coming from the fedora camp at this cycle | 06:01 |
| flocculant | hifi: thanks | 06:11 |
| hifi | well what do you know, updated packages and the problem went away, looks like someone else had hit it first :) | 06:18 |
| FredG | hello | 09:09 |
| knome | hello | 09:10 |
| FredG | I installed xubuntu 16.04.04 on laptop and it can't seem to resolve dns names. Is there a place I can | 09:11 |
| FredG | Hardcode a dns server number? I tried adding a static IP in interfaces, but no joy | 09:11 |
| knome | check /etc/hosts | 09:12 |
| knome | though obviously if the issue with dns resolving is with xubuntu, you should fix that and not live by workarounds... | 09:12 |
| FredG | hmm.. I've got 127.0.0.1 Localhost and 127.0.1.1 pihole (which is hostname | 09:14 |
| knome | you can add things like "162.213.33.176 xubuntu.org" | 09:14 |
| FredG | to the hosts file? | 09:14 |
| knome | after which xubuntu.org is resolved to that IP address.. | 09:14 |
| knome | yes | 09:14 |
| hifi | the active dns server configuration is in /etc/resolv.conf and it is usually managerd by NetworkManager or some other application | 09:15 |
| knome | but again, this is just a workaround for your issue, so if your internet connection resolves DNS address for other computers, you should fix the issue | 09:15 |
| hifi | if resolv.conf is empty or has an invalid dns server address your system is unable to resolve names | 09:15 |
| FredG | ok. | 09:17 |
| FredG | the router usually does the DNS resolution, i'm trying to set up a pihole but this problem started upon install | 09:19 |
| FredG | I did change NetworkManager to commment out DNSMasq and add dns=default but that didn't fix anything. I'll try the resolv.conf | 09:20 |
| hifi | just see what's in there first | 09:20 |
| FredG | in /etc/resolv.conf there is interface-order resolf.conf.d update.d and update-libc.d | 09:22 |
| FredG | and in resolv.conf.d is Original base and | 09:23 |
| FredG | head and tail | 09:23 |
| hifi | if there is no 'nameserver 1.2.3.4' entry in the text file /etc/resolv.conf it means you don't have a name server configured | 09:23 |
| FredG | nope. there is no resolv.conf | 09:24 |
| hifi | you could try if you can force a temporary nameserver by adding 'nameserver 8.8.8.8' (it's the Google DNS server) there but that's not a permanent solution but will help you get connectivity | 09:24 |
| hifi | you can also use your router ip address there if you know it will do dns resolution | 09:25 |
| FredG | is it nameserver=8.8.8.8 ? | 09:25 |
| FredG | or whitespace in between = | 09:25 |
| hifi | no '=', just 'nameserver 8.8.8.8' | 09:26 |
| FredG | ok, let me give that a shot. the weird thing is dig 8.8.8.8 works but dig google.com doesn't | 09:27 |
| FredG | argh.. nope | 09:28 |
| hifi | if you've setup your interfaces manually, you have set up a default gateway, right? | 09:29 |
| FredG | yeeessss... | 09:30 |
| FredG | I'm try8ing to think where I did that | 09:30 |
| hifi | if you can't ping 8.8.8.8 and there's no reason why you couldn't (no firewall blocking ping to outside) then you don't have a route out | 09:30 |
| hifi | 'ip r' should show 'default via 1.2.3.4' if you have a default gateway setup currently | 09:30 |
| FredG | I can ping 8.8.8.8 I can't ping google.com | 09:31 |
| hifi | can you 'dig @8.8.8.8 google.com' | 09:31 |
| FredG | ip r did default vi 192.168.1.1 which ish rouuter | 09:32 |
| FredG | digg got anser google.com 172.217.3.174 | 09:32 |
| hifi | then you typoed /etc/resolv.conf | 09:33 |
| hifi | if /etc/resolv.conf has a single line of 'nameserver 8.8.8.8' it should effectively work | 09:33 |
| hifi | then 'dig google.com' is essentially the same as 'dig @8.8.8.8 google.com' and all dns should resolve normally | 09:34 |
| FredG | I checked resolv.conf, its ok. dig google.com times out no servers reached, while dig@8.8.8.8 | 09:35 |
| FredG | seems to resolve normally. | 09:35 |
| FredG | I noticed that in the desktop Network setting, every time I add a DNS number to the middle tab, it removes it on reboot. | 09:36 |
| FredG | hey, it works! | 09:40 |
| FredG | Rebooted and it seems to be ok, so far. thanks Hifi!! | 09:40 |
| === GridCube_ is now known as GridCube | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!