Slashdot Mirror
Debian GNU/Linux 8.1 (Jessie) Officially Released
prisoninmate writes: The Debian Project has announced the immediate availability of the first maintenance release of Debian GNU/Linux 8 (Jessie). As expected, Debian GNU/Linux 8.1 comes with a new Linux kernel, version 3.16.7-ctk11, which fixes the well-known EXT4 data corruption issue caused by delayed and unwritten extents, blacklists queued TRIM on Samsung 850 Pro SSDs, adds support for XHCI on APM Mustang USB, and updates Crucial/Micron blacklist in libata.
This is the second release in the history of Debian I didn't give a fuck about.
This releases also fixes a grave bug in systemd. Depending on several conditions, it would SIGKILL things way too aggressively on shutdown, causing data corruption and data loss if the service it just SIGKILLed in haste had anything worthwhile to do.
Interestingly enough, that bug was fixed post-haste by Ubuntu, and a bit more sluggishly by Debian the moment someone came across the issue and found a bug report in Fedora that described the root cause... while the same bug still lingers in the Fedora bug tracking. In fact, it is still open in Fedora and systemd upstream. Note that said bug was reported to Fedora in 2014-09 !!
https://bugzilla.redhat.com/show_bug.cgi?id=1141137
I sure hope this attitude is not prevalent in the RHEL side.
Does it have an SELinux policy now?
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
Real time kernels? Did they resolve the funding issue?
Let's not pretend everyone has issues with systemd. Plenty of people are totally ok with it.
Until they have to debug a boottime issue (which crops up quite frequently in production environments with systemd). Some overworked desktop/power-management developers and lazy devops folks have been seduced by the promises of systemd, but all it takes is one morning wasted tracking down boottime issues within binary logs and quirky systemd corner cases to make it clear just how bad an idea systemd has turned out to be.
Unfortunately, by then their strategy of subsuming other projects (sianara ntp, it was nice knowin' you), enforcing dependencies, making it more difficult to maintain alternatives (dropping support for biosdevname=0 for example) will have made it difficult if not impossible for those who wake up to switch to something that adheres to more sensible unix norms. I have used Linux since 1993, on my desktop since I could get X running with twm, and later through the gauntlet of enlightenment, gnome, KDE, e17 etc., but I fear this really is the beginning of the end for Linux as a viable alternative to anything. Unless of course Google steps up to the plate with a solid alternative (after all, they don't seem to use systemd in chrome OS). OpenRC is great, but with power management developers refusing the support anything other than systemd, it faces an uphill battle despite being a well established and in most ways a superior init system.
Perhaps the Debian Fork, Gentoo, Funtoo, Arch without Systemd, etc. will succeed in joining forces to maintain a sensible alternative or two. Because otherwise you might as well run OS X ... you get the same byzantine init and config crap, without the other hassles that in the past were worth it to run a clean Linux system, but certainly aren't with systemd in the mix.
The Future of Human Evolution: Autonomy
If you don't want systemd then in your /etc/apt/preferences, add:
Package: systemd
Pin: origin ""
Pin-Priority: -1
Especially for multimedia manipulation. Our project FreeSWITCH http://freeswitch.org/ needed most of the updates in jessie to be able to run properly. All the libraries like libavcodec, libavformat and vlc etc. it's harder than it looks to swap out libraries because you need harmony among all the software it supports. Sometimes changing one library can cause a lot of issues that are not always immediately visible. New releases, even if not exciting on the outside, often have a lot going on behind the scenes.
Time to move to Slackware then? Or pick another: http://without-systemd.org/wik...
> Gentoo + OpenRC here, fuck systemd. If the rest of you enjoy having something shoved down your throats for political purposes
THANK YOU FOR TELLING US WHAT YOU USE!
His point is that you have more reasonable options for a server Linux system than a distribution that has adopted an opaque init system like systemd that is being pushed largely by the desktop crowd (not that you need it for a good desktop...lots of people have been running modern Linux desktops since the 1990s, and have kept up with the latest changes, without adding the complexity and opacity of systemd).
Some options for a systemd desktop OR server Linux system:
and many more. All of which many find to be much more suited for servers than Fedora or Debian with systemd.
The Future of Human Evolution: Autonomy
Now they're shilling slashvertisements for Linux!
No, it's not possible for systemd to have a bug. Our very own Peter H.S. told us that systemd is "rock stable". "Rock stable" software systems don't have bugs! And Peter H.S. has a 5-digit Slashdot UID! Clearly he knows what he's talking about, and couldn't possibly be wrong.
i had read all the negative stuff about systemd - expected a nightmare - updated a couple of machines - small learning curve - but guess what - I ended up liking it. The system found some bugs for me that had eluded me for a long time.
Big deal - I type systemctl start daemon (tab complete works here) instead of /etc/init.d/daemon . I suppose some of you are just too old to learn anything new. Yes change is work - and I'm lazy - but this is obviously the future.
And despite the disinformation posted here - you could remove systemd if you want - but it would be stupid to.
About systemd - Louder isn't righter..
Why do you keep enforcing what your other aliases write? Nobody else will agree with you?
Coward!
damn, people complaining about system D, red hat linux software not safe or reliable, ect.... If bsd and linux are such a headache why use them in the first place? Why not just spend $99 on Windows 7/8.1 or 10 when it comes out and make it a 5($19) to 10($9) year desktop/workstation investment. Plus, you can download and run most of the linux applications on windows anyway. I have run both bsd and linux as a desktop and I just don't see the benefit of using them over Windows when I need photoshop, visual studio, gaming, plus easy offline installation of drivers and software unlike linux which is internet dependent.
:D
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
On a VM on your mom's MacBook that you take down to Starbuck's in a record bag slung over the crossbar of your fixie.
It is exactly because the systemd-hater camp apparently consist of technical illiterates like you, that they have lost each and every technical argument on all major distros. Ad hominem attacks and poisonous threats and trolling systemd threads are all you can do. Almost all volunteer developers have left the non-systemd camp because of its toxic atmosphere where attacking open source developers and users are as normal as breathing air.
Think about it; the anti-systemd faction couldn't even muster 5 Debian developers to sponsor a GR bill to overturn the technical committees decision of making systemd default init.
The negative, hate-driven anti-systemd campaign have resulted in that 100% of all commercial general Linux distros and most of the community driven distros are behind systemd and are supporting it. Talk about a losing campaign strategy.
look dude you are on dilbert!
You really don't know what are talking a about. Vague opinions dont count for real world actions.
Systemd will fail in the long run. Systemd lovers are just like the windows fanatics of yester year. My company has thousands of Linux systems guess what none of them are moving to a distro the uses systemd and never will. We will still keep making money. And will have a freedom of choice. So go suck it systems lovers.
Not convincing at all. Systemd still sucks. Funny my system runs better after I delete all the systemd binaries and libs.
Agree my company is also never moving to a distro that supports systemd.
Systemd will fail in the long run. Systemd lovers are just like the windows fanatics of yester year. My company has thousands of Linux systems guess what none of them are moving to a distro the uses systemd and never will. We will still keep making money. And will have a freedom of choice. So go suck it systems lovers.
Why should I care that you don't use a systemd distro? If you are making money on Linux, great. If you are using eg. Slackware to do so, hey, that is great too. I respect mr. Volkerding and his way of making a distro.
I like freedom of choice and I think systemd provides exactly that. Even if you don't like it, you benefit from the fact that there now are several udev-implementations (before there was just udev and the limited mdev) and several ConsoleKit/systemd-logind implementations (before systemd there was only CK).
But apparently the freedom of choice doesn't include the right to choose systemd.
That is a major problem with the behaviour of the anti-systemd camp; they won't accept that highly skilled Linux developers (including Kernel developers) and experienced distro and system maintainers, thinks that systemd is superior to whatever else out there, and therefore chooses to build their distro around it.
This lack of accepting other peoples freedom of choice is why you are trolling a Debian thread, even though you don't use the distro and claim you never will.
So think about what you are actually doing before saying "freedom of choice" again.
Anybody know if this will fix the BSOD?
When I use kernel 3.5 everything is fine. With 3.16 I get lock-up withing 24 hrs - sometimes within a few hours (2?).
I will try it when it filters thru the Ubuntu pipeline. I live in hope.
And my company is 100% Debian with systemd.
So what?
Watch this Heartland Institute video
"I work with RedHat, Centos, and Fedora systems every day, and the fact is Red Hat has selected a core piece of software that is neither reliable or safe. It works well enough in most cases, but for any serious tweaking of the system (as most serious shops find themselves needing to do), systemd starts displaying some very nasty behaviours." - I never believe these types of statements/anecdotes.
"Many system engineers, Dev Op guys, and admins have seen this, which is why in the server world there is so much push back against the systemd coolaid." - there isn't that many that push back, just a very vocal few and plenty of thick trolls
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
You mean one developer, who's known for throwing shit together in a crufty way, managed to convince three people at the "PNELV" by either boring them shitless or throwing a tantrum.
Never underestimate the influence of slimy sycophants close to the levers of power.
I apologise for calling you a total ponce.
I missed out "lying".
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
You mean one developer, who's known for throwing shit together in a crufty way, managed to convince three people at the "PNELV" by either boring them shitless or throwing a tantrum.
No, I mean many many kernel developers, including the guy who maintain all long term stable Linux kernels for the Linux-foundation. Basically the second guy besides Linus Torvalds that the LF employ.
I have seen zero kernel developers backing any other Linux init-system. In fact, the Linux developers seems to actually flee from the rather toxic systemd-hater camp that you and your juvenile behaviour are stellar examples of.
Seriously, who would ever work in a project with a poisonous guy like you?