271–280 of 303 posts
Been using 16.04 on my XPS 13 for a week or so now, it finally supports nearly everything (bluetooth is a couple of extra commands) out of the box, and I've not had any issues so far.
Notes from my 15.10 -> 16.04 upgrade: 1) If you use the nvidia drivers from the graphics-drivers PPA, starting the default non-root X server will hang with no graphics output. Installing xserver-xorg-legacy fixes this. 2) LXC+Linux 4.4 seems to be very broken: https://github.com/lxc/lxd/issues/1666#issuecomment-21290311... 3) Pulseaudio now uses shared memory and playing audio inside a firejail will break the pulseau…
After all the Issues i had with intel/amd/nvidia stiwching gpus in the ivy bridge days i just gave up buying nvidia and AMD, and boy has it made linux easier.
Vagrant box for 16.04: https://atlas.hashicorp.com/ubuntu/boxes/xenial64
Earlier quoted context omitted.
A hundred times this. When some library upgrade happened to break stuff on my system, I could roll it back selectively, while still getting the updates for everything else (as long as it does not strictly depend on this new library version). That's gone now. Good thing I abandoned Ubuntu a long time ago.
What did you switch to? Fedora is switching to xdg-app, which basically does the same thing. Now that those two are using such an approach, I imagine that app developers are increasingly going to drop support for distros that don't use snap, xdg-app or docker. Snap/xdg-app/docker are a lot more convenient for those app developers. Edit: forgot appc. Thank goodness they're all planning on supporting the Open Container…
Earlier quoted context omitted.
Except upstart actually allowed shell code in its configuration files[1]. Now, it did have the "exec" stanza which was far cleaner, but if you look through what Ubuntu actually did in practice, I think you'll find quite a lot of "script" stanzas in there. [1] http://upstart.ubuntu.com/cookbook/#script
That was always an option. It's the same for systemd - you can always configure: `ExecStart=/etc/init.d/something start`. But the context of the comment was - you as a developer writing the config. And you can do it the modern/proper way instead with both upstart and systemd.
Yes, but you cannot embed shell script directly in the job/service definition... thus making the "good path" simpler and more natural, which is a Big Deal(TM) in software usability. (As evidenced by the fact that many many upstart jobs on Ubuntu at least used "script" sections.)
Earlier quoted context omitted.
> Which of course still leaves OS X, bsd, Solaris AFAIK. AFAIUI OS X has launchd, and Solaris has OMF[1]? ... so basically the BSDs are the ones left behind? [1] I think that is the acronym for Solaris' XML-based standardized system service files? (I don't care that they're XML. It care that they're standardized .)
Solaris 10 and 11 have SMF
For anyone like myself who isn't a big fan of the Unity interface, check out Ubuntu MATE[0]. The MATE desktop environment is very similar to pre-Unity Ubuntu. It seems like the final 16.04 release hasn't landed yet but I'm sure it will later today. Ubuntu MATE is also one of the derivative distros that has been granted LTS status by Canonical. [0] https://ubuntu-mate.org/
I'm a small breed of people that actually really like Unity. I used to use Awesome WM and tiling WMs for pretty much my whole Linux 'career' but now I quite like how my desktop looks like with Unity. It's my favorite DE at the moment. Screenshot: https://imgur.com/nvsf24E
At the moment, I think Unity is the only one that is not a horrendous misdesign (Gnome 3) or consists of a shoddy and insecure plugin framework that is a moving target stability wise (Gnome 3 and Cinnamon). I never liked the fussiness and the looks of KDE. So far, Unity has been the most stable, configurable (Compiz) and, most importantly, productive experience for me.
Earlier quoted context omitted.
Right click, turn live tile off. I don't know why you even bother with Linux if you didn't even try the first logical graphical gesture that one can reasonably expect to lead to fixing this problem. You can even remove most/all default tiles, like any sane poweruser would do. The same as in Windows 8. On live tiles - Apple has dashboard that has seen more success than widgets on Vista+, Microsoft decided to push some…
I think you missed the part of my comment that mentioned me being in a computer store - I just played with it for ten seconds to check out the keyboard and touchpad of the machines, I have no plans to use Windows 10 thus no need to try to disable it. Useful to hear that it is possible though! :) WRT disabling telemetry - probably the best way to go about it would be to set up a firewall or similar and try to kill all…
Not really. You mentioned Linux, you should be able to right click.
> probably the best way to go about it would be to set up a firewall or similar and try to kill all outgoing to microsoft.com
It wouldn't be.
1. I don't want to kill updates. 2. I'm more interested in whether I should trust Microsoft. If the telemetry sends how many times I opened built-in whether app and such then I suppose I'm fine with that. I'm also fine with online searches in start menu if they can be turned off, as well as services related to Cortana if they can be turned off. I wouldn't be okay with Windows scanning my computer and sending telemetry on what third-party software I use or documents I view. There were articles on the internet that were later debunked, but I can't seem to find something well sourced on what exactly is going on beyond tutorials on how to turn various knobs.
Earlier quoted context omitted.
I have seen several people use #!/bin/sh and write bash code. This is going to break on debian machines when you do ./foo If more people used #!/usr/bin/env bash, it wouldn't be that big of a deal.
And they would have non portable code. If they wrote posix compatible shell scripts it wouldn't be any big deal because they'd just work.
PSA: If you're running a HTTP/2 server like NGINX on the 14.04 LTS you'll want to upgrade to this release. Google Chrome will no longer support HTTP/2 on vanilla 14.04 after May 15th [0], even if you're using the latest official upstream NGINX packages. This is because 14.04 ships with a version of OpenSSL that does not support the ALPN extension (prior to OpenSSL 1.0.2 you're limited to NPN, now deprecated). There w…
It looks like Ubuntu 16.04 comes with Nginx 1.9.15, which is both not the latest stable release (it's a development, aka MAINLINE, release, although Nginx development branch is pretty stable) and it's one minor version ahead of Nginx's own development PPA, which is at 1.9.14. The ppa[1] notes there's a newer version[2] also [1] https://launchpad.net/~nginx/+archive/ubuntu/development [2] https://launchpad.net/ubuntu/…
The stable branch will fork from the mainline branch shortly. The version shipped in 16.04 is very close to what the stable will be, because the fork hadn't taken place before 16.04's release. I expect there to be very few changes, which is why (as someone else pointed out) we expect to update 16.04 to the stable branch as soon as it is available.
> The ppa[1] notes there's a newer version[2] also
That's just noting that the version released in 16.04 is newer than the version provided in the PPA.
> Nginx's own development PPA
Actually it's a PPA maintained by a team that care about Nginx's availability in Ubuntu. In this case, the uploads to that PPA were made by the very same person who looks after the official Ubuntu Nginx packages available to Ubuntu users by default.