And how exactly does this smoke somehow become invisible and odourless? I don't think I've ever seen a Euro 5 or Euro 6 car emit visible smoke and unlike petrol cars, which produce a noticeable smell when the engine is cold, they are odourless. If I ever see a diesel car or lorry emit smoke, it is at least twenty years old.
I regularly see diesels with 2014 or 2015 registration plates emit nasty black clouds under acceleration. The diesels seem to have fallen out of fashion around 2016, I don't see very many new registrations. But at least until 2015, the emission control doesn't work on diesel passenger cars.
Intel's normal desktop chips are basically all the same performance (within an order of magnitude), so the main difference is the presence of various features, like virtualization.
This does not change the fact that there are two cases:
EURO6 lorry engines, which are in practice free from emissions other than CO2. As a pedestrian, you only notice the exhaust by the heat.
EURO6 passenger vehicle engines, which emit pretty annoying smoke most of the time, and nasty black clouds every time they accelerate.
If we can get all engines to the EURO6 lorry level, we have solved basically the entire non-CO2 pollution problem from engines. After that we'll have to look at e.g. brakes before we do more about the engines.
You have missed the entire point. Millions of diesel engines were sold in Europe, labelled as EURO6, while not living up to EURO6 standards.
You say "No engine can be sold if it does not meet emission targets". I offer you lots and lots of engines which WERE sold despite not meeting targets. That is what the scandal is all about.
EURO6 diesel lorries are just not a problem. They are such an improvement over previous standards that it is simply shocking. You can tell when a lorry passes whether it's EURO5 or EURO6. It is not a slight improvement, it is a complete game changer. This happened because EURO6 lorries are actually road tested before they get type approval. Emissions above target == engine cannot be sold.
EURO5 and EURO6 also apply to passenger vehicles, but passenger vehicles are not tested on the road. Hence the improvement in EURO6 is practically non-existent. Emissions above target != engine cannot be sold.
Personally I am against the death penalty, but I cannot help but hope that all those involved die early of cancer or heart disease.
Diesel lorries are practically free of emissions except for CO2 these days (except when the owners install kill systems). If it's possible to run lorries practically free from emissions, then surely it's possible with smaller vehicles as well.
The main problem is that fitting a $20000 emissions kit on every lorry is quite a bit of money, but it's a reasonable part of the overall lorry cost. Fitting a $20000 emissions kit on every passenger car would kill most of the industry.
When it comes to particulates, the gap is getting narrower. Petrol engines were basically particulate free for quite a long period, since the invention of microcontroller-managed engines.
The new ultra-lean burning engines are unfortunately emitting particulates in such amounts that they will likely need filters. Which could bring the whole AdBlue scandal back.
It would break all the time because systemd internals like logging aren't a stable interface. It would require constant maintenance to be kept compatible with standard systemd. It would be worse than maintaining out-of-kernel modules The only way to avoid that would be to get it into the main distribution, and Poettering would never stand for it.
There is no point in contributing to or changing systemd unless you buy into Poettering's "vision". The only way to go is a full-bore fork and none of the distributions have the manpower for that either.
At this point, Linux is stuck with systemd unless Linus himself makes an init daemon. Personally I switched to OS X on the desktop after almost 20 years of Linux.
Of course if the journal was a real problem it would be pretty trivial to write a version of journald that wrote text logs, or just passed stuff off to syslogd or whatever.
It would be extremely non-trivial to integrate it with systemd. It would break all the time, and the chances of Poettering accepting it as a part of the official distribution of systemd are nil. Not happening.
Hopefully Poettering will tire of systemd soon and pass it on.
Classical init was made to handle monitoring of services, making sure they get restarted if they fail but not over and over if they keep failing. This was done with inittab.
Unfortunately inittab because too limiting, especially when it came to starting order and dependencies, and so everyone abandoned it, replacing it with a bunch of shell scripts, different depending on distribution and Unix variant. Alas, the process monitoring was lost in that change, so everyone had to run stuff like monit and write a bunch more scripts.
SystemD brings proper daemon monitoring back, on steroids. It does away with stupid PID files and it handles dependencies very very well. It is an enormous leap forwards.
Alas, it also decided to solve a bunch of non-problems like logs and DNS resolution and file system mounting. Problems that already had really well tested solutions that could be relied on to never break.
(Yes, snatching STDERR from a daemon is genius. Definitely. But what was wrong with then handing the output to the syslog daemon?)
You got taken by scammers. Sucks to be you. However, you can't expect the rest of the world to let the scammers continue, despite the inconvenience it is for you.
Back before Cimber Sterling went bankrupt, the founder of Cimber, Jørgen Nielsen, did a barrel roll in an (sadly otherwise empty) ATR42-500. This was in 2008.
He got told off by the Danish air authorities despite being a certified test pilot, because he had declared the flight to be a normal flight instead of a test flight.
The server probably had something sensible in/etc/fstab that systemd didn't happen to like. It causes systemd to stop booting without giving any kind of error.
Yes, plain-old-DPI is a fairly useless metric. But the whole premise is that Gnome should do magic when DPI isn't set in the X-server, invoking incantations until the right DPI suddenly appears in the wisps of smoke. Consensus on Slashdot is that the Gnome team are a bunch of ridiculous bastards for not being willing to do that.
Whereas that seems like the entirely correct solution to me -- if there has to be magic spells involved, put them in the X server, not in each toolkit. And if the magic incantations break, the way they usually do, there is only one place to put the override.
The turnaround story has changed a lot over the years. They no longer talk about their failed outsourcing strategy or about how their push for extreme automation made their production lines so inflexible that they were constantly producing the wrong products.
If the Gnome code can calculate the DPI from the screen dimensions and the resolution, then so can X. Put the workaround where it belongs, in the X code where it only needs to be maintained once, rather than in each toolkit.
The "force 96" code looks like it only activates if X doesn't know the DPI. This seems like a quite sensible proposal: If X doesn't know the DPI, then fix X.
Without a licence, you do not have rights and it's just piracy.
Easy, but wrong. Not very helpful. For instance, in the US you generally have the right to sell the software to someone else, second hand, even though the license says you can't.
You decide it is not. Then you're not allowed to use the software, as its copyright protected and you have absolutely no permission to use it
USING software was not considered an act that could infringe on copyright, when the GPL was originally created. It was argued that any copies made for the purposes of using the software were merely incidental and didn't count for copyright purposes -- they were merely mechanical acts. Even today, few argue that a core router at an ISP needs to obtain a copyright license to transfer bits of Mr Robot from Netflix's servers to the TV.
Back then, you could grab all of FSF's software from someone and use them to your heart's content, not giving a flying fuck about the GPL or any other license. The license was only a concern for whoever gave the software to you, it would only concern you if you tried to pass the software to others (and then only if you didn't simply follow the standard rules for second hand software).
Today the situation is clear as mud. Software licenses can say pretty much anything they want, and they apply to use, not just to copying. Except when they don't.
[..]sophisticated transfer switch with power monitoring[..]
Those break. Way more than they should. Often with interesting results that aren't just "power went off".
And you fundamentally can't make them redundant. You can have two of them on completely separate feeds of course, feeding into different power supplies on the servers. That sometimes helps, except when the overvoltage is sufficiently great to get through the protections of the power supply.
a) The Lenovo lock wasn't done by UEFI, it was done by preventing the hard drive controller from speaking AHCI. Linux does not have a driver for Lenovo's proprietary RAID protocol. Lenovo came to their senses. b) Nothing stops a UEFI BIOS from keeping a whitelist of keys.
Slashdot Mirror
And how exactly does this smoke somehow become invisible and odourless? I don't think I've ever seen a Euro 5 or Euro 6 car emit visible smoke and unlike petrol cars, which produce a noticeable smell when the engine is cold, they are odourless. If I ever see a diesel car or lorry emit smoke, it is at least twenty years old.
I regularly see diesels with 2014 or 2015 registration plates emit nasty black clouds under acceleration. The diesels seem to have fallen out of fashion around 2016, I don't see very many new registrations. But at least until 2015, the emission control doesn't work on diesel passenger cars.
Intel's normal desktop chips are basically all the same performance (within an order of magnitude), so the main difference is the presence of various features, like virtualization.
Are the Ryzen chips the same?
This does not change the fact that there are two cases:
EURO6 lorry engines, which are in practice free from emissions other than CO2. As a pedestrian, you only notice the exhaust by the heat.
EURO6 passenger vehicle engines, which emit pretty annoying smoke most of the time, and nasty black clouds every time they accelerate.
If we can get all engines to the EURO6 lorry level, we have solved basically the entire non-CO2 pollution problem from engines. After that we'll have to look at e.g. brakes before we do more about the engines.
You have missed the entire point. Millions of diesel engines were sold in Europe, labelled as EURO6, while not living up to EURO6 standards.
You say "No engine can be sold if it does not meet emission targets". I offer you lots and lots of engines which WERE sold despite not meeting targets. That is what the scandal is all about.
EURO6 diesel lorries are just not a problem. They are such an improvement over previous standards that it is simply shocking. You can tell when a lorry passes whether it's EURO5 or EURO6. It is not a slight improvement, it is a complete game changer. This happened because EURO6 lorries are actually road tested before they get type approval. Emissions above target == engine cannot be sold.
EURO5 and EURO6 also apply to passenger vehicles, but passenger vehicles are not tested on the road. Hence the improvement in EURO6 is practically non-existent. Emissions above target != engine cannot be sold.
Personally I am against the death penalty, but I cannot help but hope that all those involved die early of cancer or heart disease.
Diesel lorries are practically free of emissions except for CO2 these days (except when the owners install kill systems). If it's possible to run lorries practically free from emissions, then surely it's possible with smaller vehicles as well.
The main problem is that fitting a $20000 emissions kit on every lorry is quite a bit of money, but it's a reasonable part of the overall lorry cost. Fitting a $20000 emissions kit on every passenger car would kill most of the industry.
When it comes to particulates, the gap is getting narrower. Petrol engines were basically particulate free for quite a long period, since the invention of microcontroller-managed engines.
The new ultra-lean burning engines are unfortunately emitting particulates in such amounts that they will likely need filters. Which could bring the whole AdBlue scandal back.
It would break all the time because systemd internals like logging aren't a stable interface. It would require constant maintenance to be kept compatible with standard systemd. It would be worse than maintaining out-of-kernel modules The only way to avoid that would be to get it into the main distribution, and Poettering would never stand for it.
There is no point in contributing to or changing systemd unless you buy into Poettering's "vision". The only way to go is a full-bore fork and none of the distributions have the manpower for that either.
At this point, Linux is stuck with systemd unless Linus himself makes an init daemon. Personally I switched to OS X on the desktop after almost 20 years of Linux.
Of course if the journal was a real problem it would be pretty trivial to write a version of journald that wrote text logs, or just passed stuff off to syslogd or whatever.
It would be extremely non-trivial to integrate it with systemd. It would break all the time, and the chances of Poettering accepting it as a part of the official distribution of systemd are nil. Not happening.
Hopefully Poettering will tire of systemd soon and pass it on.
But you can't disable the useless binary log system.
Mod parent up...
Classical init was made to handle monitoring of services, making sure they get restarted if they fail but not over and over if they keep failing. This was done with inittab.
Unfortunately inittab because too limiting, especially when it came to starting order and dependencies, and so everyone abandoned it, replacing it with a bunch of shell scripts, different depending on distribution and Unix variant. Alas, the process monitoring was lost in that change, so everyone had to run stuff like monit and write a bunch more scripts.
SystemD brings proper daemon monitoring back, on steroids. It does away with stupid PID files and it handles dependencies very very well. It is an enormous leap forwards.
Alas, it also decided to solve a bunch of non-problems like logs and DNS resolution and file system mounting. Problems that already had really well tested solutions that could be relied on to never break.
(Yes, snatching STDERR from a daemon is genius. Definitely. But what was wrong with then handing the output to the syslog daemon?)
You got taken by scammers. Sucks to be you. However, you can't expect the rest of the world to let the scammers continue, despite the inconvenience it is for you.
Sex is a market. There are the suppliers (women) and the consumers (men).
WTF. I realize that I'm doing an ad-hominem now, but there is just no other appropriate response. Don't they have an education system where you live?
And no one even challenged you on it.
Back before Cimber Sterling went bankrupt, the founder of Cimber, Jørgen Nielsen, did a barrel roll in an (sadly otherwise empty) ATR42-500. This was in 2008.
He got told off by the Danish air authorities despite being a certified test pilot, because he had declared the flight to be a normal flight instead of a test flight.
There's a picture in this article: http://politiken.dk/indland/ar...
The server probably had something sensible in /etc/fstab that systemd didn't happen to like. It causes systemd to stop booting without giving any kind of error.
Yes, plain-old-DPI is a fairly useless metric. But the whole premise is that Gnome should do magic when DPI isn't set in the X-server, invoking incantations until the right DPI suddenly appears in the wisps of smoke. Consensus on Slashdot is that the Gnome team are a bunch of ridiculous bastards for not being willing to do that.
Whereas that seems like the entirely correct solution to me -- if there has to be magic spells involved, put them in the X server, not in each toolkit. And if the magic incantations break, the way they usually do, there is only one place to put the override.
That is not how it happened, though. They outsourced and discovered that their bricks no longer stuck together properly.
As for the thing about producing locally, Technic at least tends to come from all over the place, if you buy it in Denmark or England.
The Lego reinvention story is primarily a marketing device.
By the way, I completely support Lego, I think the vast majority of what they do is great and that they manage to act ethically most of the time.
The turnaround story has changed a lot over the years. They no longer talk about their failed outsourcing strategy or about how their push for extreme automation made their production lines so inflexible that they were constantly producing the wrong products.
If the Gnome code can calculate the DPI from the screen dimensions and the resolution, then so can X. Put the workaround where it belongs, in the X code where it only needs to be maintained once, rather than in each toolkit.
The "force 96" code looks like it only activates if X doesn't know the DPI. This seems like a quite sensible proposal: If X doesn't know the DPI, then fix X.
Without a licence, you do not have rights and it's just piracy.
Easy, but wrong. Not very helpful. For instance, in the US you generally have the right to sell the software to someone else, second hand, even though the license says you can't.
You decide it is not. Then you're not allowed to use the software, as its copyright protected and you have absolutely no permission to use it
USING software was not considered an act that could infringe on copyright, when the GPL was originally created. It was argued that any copies made for the purposes of using the software were merely incidental and didn't count for copyright purposes -- they were merely mechanical acts. Even today, few argue that a core router at an ISP needs to obtain a copyright license to transfer bits of Mr Robot from Netflix's servers to the TV.
Back then, you could grab all of FSF's software from someone and use them to your heart's content, not giving a flying fuck about the GPL or any other license. The license was only a concern for whoever gave the software to you, it would only concern you if you tried to pass the software to others (and then only if you didn't simply follow the standard rules for second hand software).
Today the situation is clear as mud. Software licenses can say pretty much anything they want, and they apply to use, not just to copying. Except when they don't.
[..]sophisticated transfer switch with power monitoring[..]
Those break. Way more than they should. Often with interesting results that aren't just "power went off".
And you fundamentally can't make them redundant. You can have two of them on completely separate feeds of course, feeding into different power supplies on the servers. That sometimes helps, except when the overvoltage is sufficiently great to get through the protections of the power supply.
a) The Lenovo lock wasn't done by UEFI, it was done by preventing the hard drive controller from speaking AHCI. Linux does not have a driver for Lenovo's proprietary RAID protocol. Lenovo came to their senses.
b) Nothing stops a UEFI BIOS from keeping a whitelist of keys.
Intel managed to kill of the Alpha and the PA-RISC with the Itanium. MIPS left the high end. SPARC and POWER looked quite endangered at one point.
All this was done while not being actually competitive at any point. You have to admire that, in an Evil Corp sort of way.