I'm sorry, what? My macbook is a 2011 and in way better condition as far as wear and tear goes, still perfectly serviceable than the MS Surface Pro 3 I have at work. I only recently upgraded from an iPhone 4-s (which is still getting updates) to an iPhone 6. If you want to cry about planned obsolescence and waste then you ought to be looking at DELL and the Android marketplace.
Depends what inflation numbers you are using, i'd say that comparing such things just leads credence to the thinking that the treasury is massively under-reporting real world inflation due to their habit of selectively excluding figures that aren't in-line with their desired reporting.
The actual false conviction rate is unknown, as many of those falsely convicted never get their convictions overturned. Several have been executed based on convictions for crimes that they did not commit, proven by DNA evidence decades later.
No argument on guantanamo. It is illegal and a disgrace. My point is that if the cops are looking to "solve" something for the public spectacle, they can and will use all of that shit to put you away. As anyone should know by now most of it is theatre, to look like they are doing something to keep people safe. You happen to be the unlucky guy in the wrong place at the wrong time? Too bad. "We got him guys, it's all good!".
Your country had those safeguards, they were thrown away under the guise of national security when the government pulled out the patriot act and other assorted legislation that they conveniently had ready to go for the occasion.
So how many people in Guantanamo have had their day in court yet? If you're linked to someone who is linked to terrorism, you're a suspect. If you have discussed things in sms or email that are critical of the government, you're a suspect. If you have been in close proximity with suspected terrorists, without even knowing it, you may be a suspect. You want to take a punt on whether or not you can be declared an unlawful enemy combatant?
There are patches to fix the vulnerabilities, they just haven't been backported by the developer to the old version of owncloud. The official owncloud path is to upgrade to the supported release. If Ubuntu want to support the old version, it is up to them to backport fixes to the old version(s) themselves, as the FreeBSD ports team often do with the ports tree.
I don't think you understand how software gets included in a distro. The developer doesn't ask for it to be included generally, it is often packaged by some third party who likes the software and wants a debian/redhat/etc. package for it. The developers distribute via source, if a distro wants to include their own custom package for it, that's their own doing.
The developer may have nothing to do with Ubuntu, packages for distributions are often developed by a third party who takes the official sources and packages it up themselves. The developers often do not package anything directly and have no interest in maintaining packages for other people's operating systems. They distribute via source.
As I understand it, this package is not part of the official ubuntu distribution, but part of the third party not officially supported packages, so that should not preclude it from being updated.
It is up to the package maintainer to backport security fixes if they want them. If they don't want to remove the package fair enough, but they should be popping up copious warnings, and maybe push a package update that alerts via script (even if it doesn't secure the package) that "THIS PACKAGE IS INSECURE AND UNMAINTAINED - it is recommended you deinstall and upgrade via original sources" or similar. This is similar to how FreeBSD ports work.
Seriously, why the hell would a company sell their competitor's stuff in their own store when they had just been sued by them? Even if they weren't sued, apple have their own line of audio gear now. It's just stupid to promote your competitor's product in your own store.
systemd is written in C. Terse, poorly commented C. The non-type-safe language with an abysmal history of buffer overflows, by a team of muppets responsible for some of the most bug-ridden, garbage the Linux world has ever seen included in a major distribution (Pulse Audio).
Excuse me if my confidence is not there.
Init scripts, be they BSD style or sysV style can be easily customized, extended, replaced or de-bugged by anyone with a modicum of shell scripting experience. They have not proven to be a cross-platform compatibility problem, as systemd has already.
In 20 years of dealing with plain text unix log files, I am yet to have corruption in them, certainly not to the point where I could not view the logs at least partially.
The fact that these logs are getting corrupted most likely IS due to systemd, the developers simply don't give a fuck. "Assuming the corruption came from another source" is exactly the problem.
Also, what do you do if files are corrupted? You attempt to at least retrieve partial contents. Log files contain valuable information. Or we would not bother logging it!
Sure, there are things that init does not do. That does not mean that systemd is the solution, or even that the architecture systemd has decided to use is a good idea.
And you think re-writing from scratch will produce less bugs? Common rookie mistake. Everyone thinks if only they could re-write they could make something better and less buggy off the bat. That is, in the vast majority of cases due to not fully understanding the problem.
Software gets complex due to fixing edge case bugs as they are discovered. Throwing all of that development away, unless you have a fucking good reason is a bad idea.
I've yet to see any "fucking good reason" for systemd doing the things it does. And definitely no way to force it on everyone as default.
What is starting processes isn't so much the issue. The issue is that systemd is demanding major changes of other software to work with it, and this is then making this software non-portable. e.g., Gnome 3.
People don't want to run Linux everywhere. Despite what some people think it is not always the best fit. There are other Unix platforms which fit better. Platforms that have had application compatibility with Linux up to this point. systemd has changed this. Changes to Gnome to work with systemd for example have made it non-portable to other platforms.
This is a problem for anyone who wants to say, develop a cross platform gnome3 application.
That, and there are the corruptable binary logs, the solution to which in the bug report is to "just delete them" and the bug has been closed as won't fix. Sorry, but if this is the resposne to journal corruption rather than finding out WHY the journals get corrupted and fixing the fuckign problem, then i do not want that in control of my logfiles.
Also, the massive violation of the KISS principle that has been a core guiding principle of Unix design since the start.
Systemd is a poor solution to a non-problem. There are plenty of other problems to tackle first, before trashing and re-writing working, well debugged code and breaking cross platform compatibility for no good reason.
Slashdot Mirror
I'm sorry, what? My macbook is a 2011 and in way better condition as far as wear and tear goes, still perfectly serviceable than the MS Surface Pro 3 I have at work. I only recently upgraded from an iPhone 4-s (which is still getting updates) to an iPhone 6. If you want to cry about planned obsolescence and waste then you ought to be looking at DELL and the Android marketplace.
Depends what inflation numbers you are using, i'd say that comparing such things just leads credence to the thinking that the treasury is massively under-reporting real world inflation due to their habit of selectively excluding figures that aren't in-line with their desired reporting.
The actual false conviction rate is unknown, as many of those falsely convicted never get their convictions overturned. Several have been executed based on convictions for crimes that they did not commit, proven by DNA evidence decades later.
No argument on guantanamo. It is illegal and a disgrace. My point is that if the cops are looking to "solve" something for the public spectacle, they can and will use all of that shit to put you away. As anyone should know by now most of it is theatre, to look like they are doing something to keep people safe. You happen to be the unlucky guy in the wrong place at the wrong time? Too bad. "We got him guys, it's all good!".
Your country had those safeguards, they were thrown away under the guise of national security when the government pulled out the patriot act and other assorted legislation that they conveniently had ready to go for the occasion.
So how many people in Guantanamo have had their day in court yet? If you're linked to someone who is linked to terrorism, you're a suspect. If you have discussed things in sms or email that are critical of the government, you're a suspect. If you have been in close proximity with suspected terrorists, without even knowing it, you may be a suspect. You want to take a punt on whether or not you can be declared an unlawful enemy combatant?
Pretty much. Entire story needs to be tagged "Nope!"
There are patches to fix the vulnerabilities, they just haven't been backported by the developer to the old version of owncloud. The official owncloud path is to upgrade to the supported release. If Ubuntu want to support the old version, it is up to them to backport fixes to the old version(s) themselves, as the FreeBSD ports team often do with the ports tree.
If it's trivially easy, why haven't you done it?
I don't think you understand how software gets included in a distro. The developer doesn't ask for it to be included generally, it is often packaged by some third party who likes the software and wants a debian/redhat/etc. package for it. The developers distribute via source, if a distro wants to include their own custom package for it, that's their own doing.
The developer may have nothing to do with Ubuntu, packages for distributions are often developed by a third party who takes the official sources and packages it up themselves. The developers often do not package anything directly and have no interest in maintaining packages for other people's operating systems. They distribute via source.
As I understand it, this package is not part of the official ubuntu distribution, but part of the third party not officially supported packages, so that should not preclude it from being updated.
It is up to the package maintainer to backport security fixes if they want them. If they don't want to remove the package fair enough, but they should be popping up copious warnings, and maybe push a package update that alerts via script (even if it doesn't secure the package) that "THIS PACKAGE IS INSECURE AND UNMAINTAINED - it is recommended you deinstall and upgrade via original sources" or similar. This is similar to how FreeBSD ports work.
Seriously, why the hell would a company sell their competitor's stuff in their own store when they had just been sued by them? Even if they weren't sued, apple have their own line of audio gear now. It's just stupid to promote your competitor's product in your own store.
systemd is written in C. Terse, poorly commented C. The non-type-safe language with an abysmal history of buffer overflows, by a team of muppets responsible for some of the most bug-ridden, garbage the Linux world has ever seen included in a major distribution (Pulse Audio).
Excuse me if my confidence is not there.
Init scripts, be they BSD style or sysV style can be easily customized, extended, replaced or de-bugged by anyone with a modicum of shell scripting experience. They have not proven to be a cross-platform compatibility problem, as systemd has already.
In 20 years of dealing with plain text unix log files, I am yet to have corruption in them, certainly not to the point where I could not view the logs at least partially.
The fact that these logs are getting corrupted most likely IS due to systemd, the developers simply don't give a fuck. "Assuming the corruption came from another source" is exactly the problem.
Also, what do you do if files are corrupted? You attempt to at least retrieve partial contents. Log files contain valuable information. Or we would not bother logging it!
They are only hiring confessed music/tv pirates now?
No, like various other unix shells that fixed shellshock 30 years ago.
Sure, there are things that init does not do. That does not mean that systemd is the solution, or even that the architecture systemd has decided to use is a good idea.
And you think re-writing from scratch will produce less bugs? Common rookie mistake. Everyone thinks if only they could re-write they could make something better and less buggy off the bat. That is, in the vast majority of cases due to not fully understanding the problem.
Software gets complex due to fixing edge case bugs as they are discovered. Throwing all of that development away, unless you have a fucking good reason is a bad idea.
I've yet to see any "fucking good reason" for systemd doing the things it does. And definitely no way to force it on everyone as default.
Also, I have never, in 18 years of dealing with Windows NT based platforms, ever seen a corrupted event log that wasn't due to storage system failure.
Yup. I could improve on systemd's logging by just piping to /dev/null. Much faster.
FreeBSD is my choice of BSD, it's a little more versatile and better supported in my opinion.
What is starting processes isn't so much the issue. The issue is that systemd is demanding major changes of other software to work with it, and this is then making this software non-portable. e.g., Gnome 3.
People don't want to run Linux everywhere. Despite what some people think it is not always the best fit. There are other Unix platforms which fit better. Platforms that have had application compatibility with Linux up to this point. systemd has changed this. Changes to Gnome to work with systemd for example have made it non-portable to other platforms.
This is a problem for anyone who wants to say, develop a cross platform gnome3 application.
That, and there are the corruptable binary logs, the solution to which in the bug report is to "just delete them" and the bug has been closed as won't fix. Sorry, but if this is the resposne to journal corruption rather than finding out WHY the journals get corrupted and fixing the fuckign problem, then i do not want that in control of my logfiles.
Also, the massive violation of the KISS principle that has been a core guiding principle of Unix design since the start.
Systemd is a poor solution to a non-problem. There are plenty of other problems to tackle first, before trashing and re-writing working, well debugged code and breaking cross platform compatibility for no good reason.
Pretty much. There is plenty of stuff in Linux that needs fixing far more than the "problems" that systemd is attacking.