Live data from Hacker News

Ubuntu 17.10 Artful Aardvark released

releases.ubuntu.com

101–110 of 208 posts

Re: Ubuntu 17.10 Artful Aardvark released

#101
post #38

Earlier quoted context omitted.

I have bought a new desktop this spring. The first thing I did was configuring wake on lan (in France, we have 7 days to cancel a purchase). The second one was to configure ssh and gnome to be able to administer it remotely (line DisallowTCP=false in /etc/gdm3/custom.conf). I use Linux at work since 1999 and I have used a local display less than 1% of the time. An application that does not work remotely does not exis…

1% of users with very particular requirements should not hold back the experience of the other 99%.

Something as fundamental as remote desktop should not be sacrificed for the convenience of a tiny minority of developers.

Re: Ubuntu 17.10 Artful Aardvark released

#102
post #68

32-bit installer images are no longer provided for Ubuntu Desktop. The Ubuntu Desktop now uses GNOME instead of Unity. On supported systems, Wayland is now the default display server. The older display server is still available: just choose Ubuntu on Xorg from the cog on the log in screen. GDM has replaced LightDM as the default display manager. The login screen now uses virtual terminal 1 instead of virtual terminal…

In other words, they've made a lot of big changes right before an LTS version so that they can get wider usage with those who don't mind being on the bleeding edge. Sounds like they're doing it right :) I'm putting a lot of hope into 18.04. Been using Ubuntu for over a decade now and my happiness with it has been steadily decreasing. Mostly at this point due to very laggy graphics performance (whether using OSS or cl…

If 18.04 isn't awesome, I'd suggest you give 18.04.1 a try. Even LTS releases have a fair number of issues just after release, in my experience, which the first point release fixes.

Re: Ubuntu 17.10 Artful Aardvark released

#103
post #66

Earlier quoted context omitted.

+1 for rg, it's amazing

Has anyone made a good and detailed comparison of all these grep replacements? People keep saying how great they are, but I can never trust them to what I expect the way I trust grep.

From the creator of ripgrep, so might be biased comparison, but anecdotally ripgrep feels faster to me too http://blog.burntsushi.net/ripgrep/#methodology

Re: Ubuntu 17.10 Artful Aardvark released

#104
post #47

Earlier quoted context omitted.

I recommend everybody intending to run Linux to avoid nvidia GPUs. The experience with amd and intel GPUs is vastly superior.

I use nothing but Nvidia on Linux. Their performance and stability is greatly superior to AMD on high-end 3D applications such as Maya. I'll admit, I have not revisited AMD cards in a while, so perhaps I'm out of touch with the current generation. I also do not consider the open source nouveau driver to be acceptable. I've had too many problems with it in 3D apps.

But their proprietary driver is lagging behind a lot of the ecosystem. E.g. until recently their driver did not work with Wayland/mutter because NVIDIA was pushing their own device memory allocator (via the EGLStreams API). It seems that it now finally works, but is very slow.

In contrast, AMD is actively contributing to the open source amdgpu driver.

Re: Ubuntu 17.10 Artful Aardvark released

#106
post #88
post #82

Earlier quoted context omitted.

Fabric is still not supporting py3, it's important tool for a lot of admins.

Fabric is reacting to what the most conservative group or Linux users (sysadmins for RHEL) are asking for. That's why RHEL moving to Python 3 would be the last push needed.

> Fabric is reacting to what the most conservative group or Linux users (sysadmins for RHEL) are asking for.

I'm not familiar with the details, but does this mean that they're resisting patches to support 3.x? Given the existence of a fork it seems likely. It's not-at-all difficult to write a single Python package that works on both 2.7 and 3.x. Especially if you are willing to use `six`.

I'll admit that it's a little harder to stay compatible with earlier-than-2.7, though.

Re: Ubuntu 17.10 Artful Aardvark released

#107
post #82

Earlier quoted context omitted.

Fabric is still not supporting py3, it's important tool for a lot of admins.

Plenty of things don't have python 3 support, but you can still use python2 without it being /usr/bin/python.

There is no /usr/bin/python in the default Ubuntu install. There's a /usr/bin/python3, and if you `apt install python` you can get /usr/bin/python. But all of the system's code that uses Python has been converted to Python 3.

Re: Ubuntu 17.10 Artful Aardvark released

#108
post #14

> ifupdown has been deprecated in favor of netplan and is no longer present on new installs [...] > Given that ifupdown is no longer installed by default, its commands will not be present: ifup and ifdown are thus unavailable, replaced by ip link set $device up and ip link set $device down. Sad to see this go; I always use ifup, ifdown and ifconfig. Yes, they're old and clunky tools but in a way they are the staple o…

> ifup and ifdown are thus unavailable, replaced by ip link set $device up and ip link set $device down.

That's weird, they do two very different things. ifup and ifdown apply / unapply the configuration in /etc/network/interfaces, like setting IP addresses, setting routes, running other commands you might have like configuring card-specific hardware things or sending notifications to other processes, etc. ip link set dev $dev up/down only enables or disables the card. They also require the card to exist already, in the case of bridges or bonds or VLANs or similar things.

Does netplan cause all of these things to be done automatically when the card is upped or downed?

> ifconfig ... staple of a proper Linux installation to me.

To be honest, I have a lot of muscle memory for ifconfig because it's what I grew up with, but also Linux's ifconfig has gotten very different from the BSD ifconfig (or ifconfigs? I know FreeBSD's and macOS's support different things), so it's not like it was a standard tool across UNIXes, just a standard name. I'm honestly happier with the Linux tool having its own name.

Also, ip supports things that ifconfig straight-up doesn't, like having multiple IP addresses on an interface (without configuring alias interfaces), creating various types of virtual devices, creating VLANs without using an even more awful tool, getting card stats (ip -s -s link) in a vendor-neutral way, etc.

I do really really hate the ip command's syntax though.

Re: Ubuntu 17.10 Artful Aardvark released

#109
post #88

Earlier quoted context omitted.

Fabric is reacting to what the most conservative group or Linux users (sysadmins for RHEL) are asking for. That's why RHEL moving to Python 3 would be the last push needed.

So we'll get it in 2024?

There is overlap between RHEL release support periods, from what I see it's about 3-4 years on average. So 2021? :)
Post reply on HN