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 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.
How many of those 'plenty of people' use their Linux machines for more than desktops?
There are some serious open 'show stopping' bugs in systemd for power users.
I've switched over to FreeBSD for all non-Windows machines in my house. If you go through the supported hardware list and pick good hardware everything 'just works'. Everything I've tried out so far is "Do or do not, there is no try". If you find hardware with vendor FreeBSD support it's good support. (Intel GigE vs RealTek GigE).
Jails is all I need for 'visualization'. I don't need an entire new ESXi or Xen instance. My FreeNAS server has 8-10 Jails running everything from Nginx for web development to Transmission+OpenVPN for torrents.
ZFS is a great filesystem for root. When I had a PSU take out a motherboard and 1 hard drive I was able to toss the remaining good drive in a new computer and my whole system booted like nothing happened. Replaced the degraded device and didn't lose anything. My Windows machine kept crashing on boot and required some drivers.
Until they have to debug a boottime issue (which crops up quite frequently in production environments with systemd).
You are just talking bullshit here. I have been using systemd for +4 years now and it has been rock stable.
Besides, systemd systems are so much nicer to debug than distros glued together with shell scripts.
Just the fact that you can have full logging and the systemd tools working from initramfs is a vast improvement, and the systemd journal beats all other Linux logging options by a huge distance; field based filtering and monotonic timestamps are just great when debugging boot problems.
Being able to do a "journalctl -b -1 -p err" is so much better than faffing around with grep and regex. (the line shows all log entries from the previous boot with the syslog severity level "error" and above, try that with grep!).
Unfortunately, by then their strategy of subsuming other projects (sianara ntp, it was nice knowin' you)
You are seriously misinformed here; systemd provides a sNTPv4 client, not a ntp-server. It is a compile time option, so no distro ever needs to use it instead of their preferred sNTP-client. It is included in the systemd project for two main reasons; clock-less ARM boards and OS containers. Both have special timing needs since eg. an OS container can be "frozen" and "unfrozen" without warning. systemd provides them both with a solution so they don't gets confused by time jumps.
But perhaps you think choice is bad and there are too many sNTP clients so systemd developers should be banned from providing one?
, enforcing dependencies
Like what? systemd have extremely few external dependencies. And don't try the provable falsehood that systemd inserts "hard dependencies" in other projects like Gnome/KDE.
That Gnome have had problems supporting non-systemd distros was because those distros didn't care to maintain ConsoleKit. Gnome kept on supporting CK despite it having been abandoned for +1½ year with no upstream to provide bug-fixes or security fixes.
But thanks to systemd, there are now several alternatives to ConsoleKit. Choice is good.
, 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.
Again, you are really misinformed here; how can systemd ever make it harder for non-systemd distros that are using mdev or vdev or eudev?
If a non-systemd distro wants to use unpredictable network names they can do so.
With systemd distros here is how you turn off predictable network interface names:
http://www.freedesktop.org/wik...
Again, thanks to systemd the Linux ecosystem went from just having udev and mdev, to also having eudev and vdev and probably several more. So if you like choice, praise systemd for providing it.
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.
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.