Slashdot Mirror
Ubuntu 15.04 Received Well By Linux Community
jones_supa writes: Canonical released Ubuntu 15.04 a couple of weeks ago, and it seems that this release has been a success. The community is mostly reporting a nice experience, which is important since this is the first Ubuntu release that uses systemd instead of upstart. At Slashdot, people have been very nervous about systemd, and last year it was even asked to say something nice about it. To be fair, Ubuntu 15.04 hasn't changed all that much. Some minor visual changes have been implemented, along with a couple of new features, but the operating system has remained pretty much the same. Most importantly it is stable, fast, and it lacks the usual problems accompanied by new releases.
Congratulations for specifically missing the entire point of the article.
I've never seen so much evangelizing about a particular subsystem change in Linux before, which makes me think that unlike other past changes, this one needs it rather than having it's own benefits do the selling...
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
A Softpedia article gets linked to Slashdot story these days; can Slash-vertisement get any lower than this?
A friendly reminder that if you hate Unity, Ubuntu also supports KDE, Xfce, LXDE, Enlightenment, Cinnamon, GNOME Shell, MATE, and the CLI.
>As far as I can tell, there is no root account I could log into directly
Seriously?
$ sudo passwd
$ sudo passwd -u root
There, now you can log into root directly and have all the security issues you want. Thanks for playing the "I don't know how to use linux" game
15.04 is not an "LTS" (Long Term Support). So we will continue to run 14.04 LTS on our servers, and on my workstation. I guess we will stick to it for another year, until April 2016. Ah well. Good Luck, gang, and thank you for the good job, Ubuntu.
I installed in on my HP ProBook 6475b laptop the other day and have only run into some minor issues.
1. I opted for full disk encrypted LVM. It didn't ask for a separate Swap partition password, instead using the main one. Fine. However, when booting, I have to enter it twice -- once for the main partition, once for swap. [Bug reported and acknowledged]
2. It hangs on reboot. I have to boot twice every time to get it to get past the boot loader. I've tried "shut down", then letting it sit for 10 minutes. Next boot -- hang and I reboot and then it works.
3. My wifi doesn't come back after suspend. I think it has to do with the particular laptop firmware, because it does this with every distro I've tried. Everything else works, but the wifi never makes it out of suspend.
The rest works fine. Changing to the proprietary AMD video drivers was a snap, and it sped up video playback to what I would expect (no stuttering on HD).
Learning HOW to think is more important than learning WHAT to think.
It follows the same path that OS X and Solaris 11 do, with the root user disabled by default, with the first user created having sudo access to root. A quick change of root's password can enable this if needed.
All and all, this is a good thing. There are a lot of security audit checklists that are starting to require root not be able to be logged on directly, so shipping an OS that has this locked down is not unusual.
For personal use, there isn't anything wrong with unlocking root and using that with su or just logging directly in. However, in business/enterprise settings, it does make sense to have a user stage, even if it is just having different RSA keys in root's authorized_hosts file that belongs to each individual user. I like unlocking root locally, so I can log in with that in single user mode, but having remote root access completely disabled.
I always tell new folk around here that there are three stages of competency in System Administration.
There is the newbie, that is afraid to do much because they don't know what they can do.
There are the old farts, that don't do much because they know what they can do.
And then there are the really dangerous ones in between, who do too much because they think they know what they can do.
How come Slashdot never gets Slashdotted?
I'm pretty sure the entire point of the article was that a good systemd flamewar is good for the hit count.
I've seen a lot of posts in this thread about how people have massively hosed a system while logged in directly as root. I'd be curious to know exactly what command(s) caused the issue. I'm guessing some variant of rm or dd. How would sudo have prevented it? I log in as root directly when I know I need to do something that requires it. My root shell colors the prompt red as a reminder. I log out when I'm done. I think at the end of the day, not hosing up your system is best prevented by constant awareness when you're logged in as root or running something as root. You could just as easily trash your box with a mis-typed sudo command.
The 'article' is an editorial presented as something to be taken as representative of the community at large. My impression is that Canonical is losing mindshare quickly to Mint on the desktop, that Canonical really doesn't care that much about desktop anyway as they pin their business hopes and dreams on servers and embedded (where it also is failing to get much traction business wise).
Note that none of this has to do with the parents referenced points: Gnome 3 (which is largely defined by Gnome Shell, which Ubuntu doesn't even use by default) and systemd (I'm sympathetic, but not sure it's making much of a difference either way in the desktop distribution selection right now).
XML is like violence. If it doesn't solve the problem, use more.