Slashdot Mirror
Ubuntu 16.04 LTS Will Ship With Linux Kernel 4.4 LTS
prisoninmate writes: The current daily build of the Ubuntu 16.04 LTS (Xenial Xerus) remains based on the Linux 4.2 kernel packages of the stable Ubuntu 15.10 (Wily Werewolf) operating system, while the latest and most advanced Linux 4.3 kernel is tracked on the master-next branch of the upcoming operating system. In the meantime, the Ubuntu Kernel Team announced plans for moving to Linux kernel 4.4 for the final release of the Ubuntu 16.04 LTS (Xenial Xerus) operating system.
Took me some time, but eventually could get used to Unity. Usable now, less bugs and quite convenient - again give it time to get used to it.
Slashdot, fix the reply notifications... You won't get away with it...
And, it's dropping of stderr that makes troubleshooting problems starting services very difficult.
systemd works just fine for casual desktop users. Of course on servers, swallowing stderr and a lot of syslog messages makes it a pain.
Just because it is old doesn't make it bad, Mr systemd fanboi.
Same experience here. I was KDE only but after using Unity for a while (since 14.04 IIRC), I think it's one of the best (if not the best) UI for a desktop.
My only complain are notifications. Not being able to interact with them is just plain stupid.
sudo apt-get install mate-desktop
sudo apt-get purge unity*
sudo reboot
Hmmm http://askubuntu.com/questions/187022/how-can-i-send-a-custom-desktop-notification ... http://askubuntu.com/questions/110969/notify-send-ignores-timeout
To customize a few stuff like notifs time
Also some applications, eg skype, allow to enter a script path in the settings, triggered each time a notification is sent.
Slashdot, fix the reply notifications... You won't get away with it...
I thought 15.10 was going to be a LTS release. They push it back to every two years now instead of 18 months?
Understanding the scope of the problem is the first step on the path to true panic.
Just install Xubuntu or MATE and don't worry about it. XFCE has advanced far enough to be a suitable replacement for MATE and is less resource hungry.
Even the crap GNOME3 is better than Unity.
KDE is the only "full" DE that doesn't kill OpenGL performance though. I don't care for it though, it's always been so buggy (does QT breed bad code or something? QT apps tend to be the buggiest). The only other alternative is to run something like OpenBox as the XFCE or MATE window manager, that keeps OGL performance where it should be.
Can someone explain why ALL THE MAJOR DISTROS have switched to systemd, when all I've seen is universal hate for it?
Either distro maintainers are masochists, or there's someone pulling strings somewhere to get this bullshit into every distribution.
We've slowed our move to newer versions of RHEL and Ubuntu at my workplace because of systemd. Eventually we're going to have to deal with it, but we're putting it off as long as we can. Everyone I know hates this thing. HOW did it become so pervasive?
Except it doesn't. The examples provided in the past supposedly proving this used the wrong Type= value (should have been forking, not left to the default which is 'simple').
Sure. systemd is fine. People hate change. Hate is louder than praise.
I like it.
This must be debian-specific. On my 4 personal machines running one distro using systemd, and all the systems at work running a totally unrelated distro that also uses systemd, I have never seen this (neither distro is Debian-based).
Most of us who dislike systemd have absolutely no problem with change. In fact, it's the one thing we've come to expect, especially those of us who are professional system administrators. People like us have each dealt with more versions of UNIX, Linux, Windows and other OSes than you could possibly imagine. Change is the least of our concerns. It's something we've dealt with every day, for decades on end, without even thinking about.
The problem with systemd isn't that it's a change. The problem with systemd is that, in our experience, it suffers from a huge number of serious problems! We're talking about problems ranging from logging output that's not easily usable through to systems that unexpectedly stop booting properly and that are difficult to diagnose.
We dislike it because it causes us nothing but problems, and these problems can't even be easily fixed. A bad architectural decision, like the use of binary logging, can't simply be patched away! The only reasonable way to "fix" it is to not use systemd and any Linux distro that uses systemd.
I'm sure there's plenty of reading material out there.
It was written by the same cadre of villains responsible for PulseAudio. Unfortunately they're Redhat employees. Debian's governance bodies had slowly been stacked with Redhat sympathizers who snuck it in through the backdoor (used an inappropriate committee to make the decision) and a Redhatter cast the tie breaking vote. When the community demanded a general vote, there was one option for "let's just go with systemd" and like 4 options for differing levels of rejection. By splitting the opposition into 4 categories, the systemd-friendly option managed to get a plurality of the votes.
Ubuntu had to follow suit because Canonical doesn't want to expend the resources to maintain an init system anymore.
It is a genuinely surprising outcome. There are attempts to fork Debian (Devuon (sp?)), but it seems many people who are serious about avoiding it are moving to BSD (where systemd will not appear since it relies on features specific to the Linux kernel).
universal hate? No, there's just a very very small vocal minority. in places that matter, like dev lists, people who want to make linux better welcome systemd. I think the hold outs are the ones that have never done reinstalls, customized their system to the max, etc. They already have 'fast' systems, and see any change to the old way of doing things as bad. They are the minority. Also, most of them are users and don't contribute back.
the only reasonable way to "fix" it is to not use systemd and any Linux distro that uses systemd.
Which means pretty much every major distro out there .
But stderr is dropped by systemd by policy. That makes it very difficult to troubleshoot start-up problems.
But will unity suck any less?
Unity is one of the rare remaining DEs that don't have the amateurish flat look. Windows 10, OS X, KDE, GNOME, all went with it.
systemd has a policy against logging stderr. On a desktop system that is fine, but in a server that is a showstopper.
And that is why people hate systemd. Its creator doesn't understand UNIX.
Stderr is not and never has been dropped. RTFM.
Of course on servers, swallowing stderr
It doesn't. Not per design, not per default configuration. stderr is logged and can be redirected to the console. That is if you ever bothered to read the manual.
Just as I scrolled into this article, 15.10 hung on me again.
http://michaelsmith.id.au
Try updating /etc/speech-dispatcher/speechd.conf and restart the daemon. Systemd will state everything is fine, but it isn't; it fails to kill the old process. Maybe this isn't casual desktop usage, but it's just not supposed to work that way.
Please login to access my lawn
And that is why people hate systemd. Its creator doesn't understand UNIX.
Of this whole stupid shit-fest, THIS is the comment that needs to be modded up. And I'm typing this on a systemd-based Linux distro.
It is dangerous to be right when the government is wrong.
Can someone explain why ALL THE MAJOR DISTROS have switched to systemd, when all I've seen is universal hate for it?
The hate isn't universal.
It's certainly easier for distribution integrators than the old RC scripts. Also, there has been considerable external pressure because some of the major packages like Gnome more or less depended on systemd, so not having it meant no Gnone which was a showstopper. Actually you can now run Gnome without systemd but for a while that wasn't possible.
Another reason for the hate is that there are a lot of awfully obnoxious systemd fanbois out there who make claims like:
* You hate change (literally ad-homenim, attaxking the person not the message)
* Making claims about things that are only possible with systemd that demonstrably are not (I debunked a bunch of these in the last thread)
There's a lot of FUD on both sides, and frankly after the PulseAudio debacle, a lot of people have a deep distrust of Lennart Pottering (well justified IMO), and are incredibly leery of making the core of a Linux system depend on code written by a cowboy coder who doesn't seem to care about stability or quality.
SJW n. One who posts facts.
[sarcasm]the biggest gnu/linux server company (redhat) clearly does not know what they're doing by implementing systemd into their distribution. [/sarcasm]
btw, i also hated systemd until i was forced to use/learn it. now i only hate aspects of it but overall perceive it as an improvement.
That doesn't work. systemd throws away stderr as is its policy.
Is not reading the manual also a policy among sysadmins these days? Hint, it doesn't throw it away. Just tell it where it should go and it will go there.
Debian had some early issues when they switched to systemd in the testing distribution, the one that you are not supposed to run in production or anything that you think of as important. But of course that's what people did. I have used Debian 8 now for a while and never run into something like that.
You claim
doesn't work?
On what system, what does the unit file look like, where is the bug report?
Watch this Heartland Institute video
And KDE is about the only one left that you can configure to your own taste, including non-flat.
"The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
stderr is send to the logging facilities by default. Which makes debugging issues easier instead of harder...
Wish I had mod points for you. Linux: *still* no bundled compressing file system.
Amateurish? Gradients look tacky and 90's; Flat and clean is so much nicer. All of those OS' you named moved to clean designs for a reason...
I don't mean gradients but a sense of depth.