Also , there is and has been a consensus on what levels of exposure to ionizing radiation are harmful and which are lethal. To act like that is speculation is pure idiocy.
There is general agreement on the effects of fairly large acute doses of radiation. There is little knowledge of chronic low level exposure. Our knowledge of exposures to extremities is even poorer. The LNT camp claims that unlike every thing else in existence that can harm a human, radiation has no safe level. Evidence, however suggests otherwise. There is even some evidence that there exists an ideal dose for optimal health where more OR LESS than that amount is harmful. That shouldn't be very surprising since we have actually evolved to live in our naturally radioactive environment.
As for hotspots and hot particles, those would be something to be dealt with inm that region, but they can be dealt with. The people living there now have been there a long time and don't bother with measuring radiation at all. I don't advise that, just not that it hasn't killed them in spite of being there for over a decade. I do note that if people were there measuring and marking, they would fairly quickly have mapped it all out to a fine level and would likely clean up some of the smaller hotspots as they go.
At this point, the highly radioactive iodine is gone along with the other highly radioactive but short lived elements. The risk is dominated by Cs137 at this point, and nearly half of that is gone as well. In another 30 years it will be halved again. The multi-century estimates for absolute safety are just crazy. They are based on background levels far lower than in places people live well and healthy in right now (and since before we even knew about radiation). That includes places where people routinely lay out on thorium and uranium laced sand to sun themselves.
That's where the experts come in. Even the kookiest judge can't stand against the entire field's experts when dealing with someone with significant wealth.
First tell him it will take hundreds of years as far as anyone can guess (not at all a lie if you did it right) without outright refusing. If he demands it sooner, suggest that with help from the NSA you may be able to speed it up. Then it's on the NSA for refusing to cooperate.
While the courts can be quite silly, they cannot order you to sweep back the tide. If something is technically impossible within a relevant timeframe, the court will be SOL. There are plenty of cryptographers who can testify as to the practicality of breaking a good encryption scheme. Just make sure to use a good one so that a cryptographer can fairly testify to a timeframe in the hundreds of years. Even the craziest court will have to admit that there's little point in decrypting the data after all relevant parties (including the judge) will be dead.
Now you clearly don't understand. I DO want VTs. I want them handled by something that is equally happy being launched by sysvinit, systemd, openrc, or from a root shell when I boot with init=/bin/bash.
I want my system time handled by ntpd. Ntpd doesn't care what init is installed or if it is run by hand.
I don't want them to care if dbus is up, down, or modified beyond recognition. They may use it if it exists but shouldn't get out of shape if not.
Do those tangled up utilities you speak of meet those criteria?
Actually, there's a lot more to it. For example, if the padding is lighter the players will naturally stop hitting the way they do now. Go back to the old soft leather helmets and players will quickly learn not to lead with their heads.
Many of the brain injured football players end up broke and alone, possibly in jail. By that point, if they COULD think clearly, they'd probably wish they'd played a different sport or at least taken better precautions.
Football wasn't always played in full body armor.Perhaps it's time to redesign based on a scientific understanding of the risks and how to mitigate them.
Because they are minors and their coaches are presented as experts. That convinces both the kids and parents all is well when it is not. The entire school is seemingly geared to guide minors into school sports.
Beyond that, this is a case where the 'product' is 'used' correctly and causes severe injuries anyway. Your saw scenario is a case of using the product incorrectly. If you're using the saw correctly and the blade pops off and cuts your leg off, it is a fairly clear liability for the manufacturer that got the bolts from the Happee Bolt Company and did no QC.
And note that the suit in TFA demands only reforms to reduce concussion injury, not money.
You have clearly developed no taste in system architecture. The closer to the top of the stack, the more acceptable dependencies are, though even then they shouldn't be piled on without thought.
I don't WANT init to do the things systemd does. I want other utilities that don't give a damn how they came to be running to do those things.
I would list the dependencies needed to build Apache
And again, apache runs on top of the environment created by init, it is acceptable for it to have more dependencies.
It;s one thing to build a house of cards on your dining room table. It's quite another to build your home on top of a house of cards.
Note how many systems have managed to support apache, samba, a GUI desktop and much much more on top of the simple but effective init.
Meanwhile, sysvinit can bring up a system with a degraded btrfs, systemd absolutely refuses and even Lennart can't seem to figure out what to do about it.
There seems to be a big chasm opening in the Linux world. Not to worry though, there is stable Linux out there. There are two forks of Gnome and a large variety of alternative desktops to choose from. You can still install Jessie without systemd and Devuan, Slackware, and Gentoo intend to keep that option open.
As for the lockup bug in TFA, in most projects, the kernel versions in question would be internal release only. The outside world would never see them. For example, my debian system is on 3.16 even when I enabled the backports repo.
The final bit, not all soft lockups are fatal. They are never a good thing, but they sometimes just indicate that something is taking longer than it was ever expected to and it needs to either be speeded up or broken into more manageable pieces so something else gets a chance to run.
Sure if you build everything then you end up with some 60+ components with dependencies out the wazoo but then that is pretty much par-for-the-course in the Linux world anyway.
There's the problem, dependencies out the wazoo. And no, that is not par for the course for system tools in Linux. Look at ldd/sbin/init. Those are the only dependencies. To have a 'normal' system, you'll need to add a shell (ldd/bin/bash)
Uselessd requires code patches to relax the coupling. That means the code was more tightly coupled before. It bolsters my claim that systemd is gratuitously coupled to make it harder to rip out OR that it is a poorly executed project. Hanlon suggests the latter, so I'll go with that.
Were your claim true, there wouldn't be a uselessd project.
We keep trying, and even changing our selection after the first goat is revealed, but we keep getting goats. I'm not sure any of the doors have a car behind them.
Most of us call a mere 14,000 hits, even on a tiny VM, another day at the office. It really doesn't cost much to do a whois and send a quick log extract to the relevant abuse contact (if it's even in the top 10 offenders).
Loser pays is dangerous in civil suits where a small entity sues a large entity. Even the most meritorious case can be lost.
In criminal cases, the prosecutor's office should be on the hook when the defendant isn't found guilty. Not just for legal fees, but for restitution for time spent incarcerated, loss of employment (if that happens), other consequential damages (eviction, missed payments, etc) and publicity to make it well known the defendant was not guilty.
Slashdot Mirror
Possibly because none of the people running on the Libertarian ticket today hold to the core beliefs and values of Libertarianism?
Also , there is and has been a consensus on what levels of exposure to ionizing radiation are harmful and which are lethal. To act like that is speculation is pure idiocy.
There is general agreement on the effects of fairly large acute doses of radiation. There is little knowledge of chronic low level exposure. Our knowledge of exposures to extremities is even poorer. The LNT camp claims that unlike every thing else in existence that can harm a human, radiation has no safe level. Evidence, however suggests otherwise. There is even some evidence that there exists an ideal dose for optimal health where more OR LESS than that amount is harmful. That shouldn't be very surprising since we have actually evolved to live in our naturally radioactive environment.
As for hotspots and hot particles, those would be something to be dealt with inm that region, but they can be dealt with. The people living there now have been there a long time and don't bother with measuring radiation at all. I don't advise that, just not that it hasn't killed them in spite of being there for over a decade. I do note that if people were there measuring and marking, they would fairly quickly have mapped it all out to a fine level and would likely clean up some of the smaller hotspots as they go.
At this point, the highly radioactive iodine is gone along with the other highly radioactive but short lived elements. The risk is dominated by Cs137 at this point, and nearly half of that is gone as well. In another 30 years it will be halved again. The multi-century estimates for absolute safety are just crazy. They are based on background levels far lower than in places people live well and healthy in right now (and since before we even knew about radiation). That includes places where people routinely lay out on thorium and uranium laced sand to sun themselves.
Those very readings you point out suggest that some of the areas are safe and others are mostly safe for people beyond childbearing age.
a number of people have been living there for years now.
That's where the experts come in. Even the kookiest judge can't stand against the entire field's experts when dealing with someone with significant wealth.
First tell him it will take hundreds of years as far as anyone can guess (not at all a lie if you did it right) without outright refusing. If he demands it sooner, suggest that with help from the NSA you may be able to speed it up. Then it's on the NSA for refusing to cooperate.
While the courts can be quite silly, they cannot order you to sweep back the tide. If something is technically impossible within a relevant timeframe, the court will be SOL. There are plenty of cryptographers who can testify as to the practicality of breaking a good encryption scheme. Just make sure to use a good one so that a cryptographer can fairly testify to a timeframe in the hundreds of years. Even the craziest court will have to admit that there's little point in decrypting the data after all relevant parties (including the judge) will be dead.
The 5th amendment would naturally limit the law to orders issued to others. You still can't be compelled to testify against yourself.
Due process would need to be followed in order to comply with the 4th amendment.
Now you clearly don't understand. I DO want VTs. I want them handled by something that is equally happy being launched by sysvinit, systemd, openrc, or from a root shell when I boot with init=/bin/bash.
I want my system time handled by ntpd. Ntpd doesn't care what init is installed or if it is run by hand.
I don't want them to care if dbus is up, down, or modified beyond recognition. They may use it if it exists but shouldn't get out of shape if not.
Do those tangled up utilities you speak of meet those criteria?
Actually, there's a lot more to it. For example, if the padding is lighter the players will naturally stop hitting the way they do now. Go back to the old soft leather helmets and players will quickly learn not to lead with their heads.
Many of the brain injured football players end up broke and alone, possibly in jail. By that point, if they COULD think clearly, they'd probably wish they'd played a different sport or at least taken better precautions.
Football wasn't always played in full body armor.Perhaps it's time to redesign based on a scientific understanding of the risks and how to mitigate them.
Because they are minors and their coaches are presented as experts. That convinces both the kids and parents all is well when it is not. The entire school is seemingly geared to guide minors into school sports.
Beyond that, this is a case where the 'product' is 'used' correctly and causes severe injuries anyway. Your saw scenario is a case of using the product incorrectly. If you're using the saw correctly and the blade pops off and cuts your leg off, it is a fairly clear liability for the manufacturer that got the bolts from the Happee Bolt Company and did no QC.
And note that the suit in TFA demands only reforms to reduce concussion injury, not money.
Here but there's not much there yet.
You have clearly developed no taste in system architecture. The closer to the top of the stack, the more acceptable dependencies are, though even then they shouldn't be piled on without thought.
I don't WANT init to do the things systemd does. I want other utilities that don't give a damn how they came to be running to do those things.
I would list the dependencies needed to build Apache
ldd /usr/sbin/apache2 /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f9742320000) /usr/lib/libaprutil-1.so.0 (0x00007f97420fb000) /usr/lib/libapr-1.so.0 (0x00007f9741ec9000) /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f9741cad000) /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9741921000) /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f974171b000) /lib/x86_64-linux-gnu/librt.so.1 (0x00007f9741513000) /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f97412dc000) /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f97410d7000) /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f9740ead000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9742801000)
linux-vdso.so.1 => (0x00007fff13dfc000)
libpcre.so.3 =>
libaprutil-1.so.0 =>
libapr-1.so.0 =>
libpthread.so.0 =>
libc.so.6 =>
libuuid.so.1 =>
librt.so.1 =>
libcrypt.so.1 =>
libdl.so.2 =>
libexpat.so.1 =>
That wasn't hard.
And again, apache runs on top of the environment created by init, it is acceptable for it to have more dependencies.
It;s one thing to build a house of cards on your dining room table. It's quite another to build your home on top of a house of cards.
Note how many systems have managed to support apache, samba, a GUI desktop and much much more on top of the simple but effective init.
Meanwhile, sysvinit can bring up a system with a degraded btrfs, systemd absolutely refuses and even Lennart can't seem to figure out what to do about it.
That doesn't always happen, but for example, MATE is a fork of the GNOME 2 code doing more of less what you request.
So your claim is that the bug you are talking about is unknown? That you haven't seen it? My, that's quite a problem in logic, isn't it?
There seems to be a big chasm opening in the Linux world. Not to worry though, there is stable Linux out there. There are two forks of Gnome and a large variety of alternative desktops to choose from. You can still install Jessie without systemd and Devuan, Slackware, and Gentoo intend to keep that option open.
As for the lockup bug in TFA, in most projects, the kernel versions in question would be internal release only. The outside world would never see them. For example, my debian system is on 3.16 even when I enabled the backports repo.
The final bit, not all soft lockups are fatal. They are never a good thing, but they sometimes just indicate that something is taking longer than it was ever expected to and it needs to either be speeded up or broken into more manageable pieces so something else gets a chance to run.
Sure if you build everything then you end up with some 60+ components with dependencies out the wazoo but then that is pretty much par-for-the-course in the Linux world anyway.
There's the problem, dependencies out the wazoo. And no, that is not par for the course for system tools in Linux. Look at ldd /sbin/init. Those are the only dependencies. To have a 'normal' system, you'll need to add a shell (ldd /bin/bash)
It's like choosing a door on "Let's make a Deal".
Uselessd requires code patches to relax the coupling. That means the code was more tightly coupled before. It bolsters my claim that systemd is gratuitously coupled to make it harder to rip out OR that it is a poorly executed project. Hanlon suggests the latter, so I'll go with that.
Were your claim true, there wouldn't be a uselessd project.
We keep trying, and even changing our selection after the first goat is revealed, but we keep getting goats. I'm not sure any of the doors have a car behind them.
If they make you wait in jail longer than the average sentence would last, they should have to let you go free and clear.
I think it was two years ago in Atlanta that a judge ruled exactly that and let a lot of people awaiting trial for minor offenses go.
Tar and feathers come to mind...
Still, that's a LOOONG time to be locked in a cage like an animal compared to a misdemeanor and a fine.
Most of us call a mere 14,000 hits, even on a tiny VM, another day at the office. It really doesn't cost much to do a whois and send a quick log extract to the relevant abuse contact (if it's even in the top 10 offenders).
Loser pays is dangerous in civil suits where a small entity sues a large entity. Even the most meritorious case can be lost.
In criminal cases, the prosecutor's office should be on the hook when the defendant isn't found guilty. Not just for legal fees, but for restitution for time spent incarcerated, loss of employment (if that happens), other consequential damages (eviction, missed payments, etc) and publicity to make it well known the defendant was not guilty.