As the bosses will do analyses like "Which are the 1% I should fire", the matching algorithm (no AI in there) will resort to partial syntactic matches when it cannot fulfill the quota otherwise. Even a name with suspicious parts will get you fired then.
People will just use other channels for that type of communication. And there is also a serious risk: Many people will not communicate needed information for fear to be caught by this. In the ultimate consequence this can do much more damage than it helps.
For one thing, many unemployed have no marketable skills. Their skills may have gone out of demand or they may not have been able to acquire any currently useful skills in the first place. That is going to become very common, as we are moving into a post-labor economy where producing goods and services takes much less effort than is needed to keep a workforce employed. In addition, many remaining jobs have far higher skill requirements.
Unless that problem is solved, society as a whole will disintegrate. For example a basic free income is a possible solution to keep society functioning. There are others, but "work" as primary means to distribute money is becoming less and less able to do the job.
The other thing is that a 2 month commitment is not worth moving or making larger changes in your life and quite likely, they did not offer reasonable conditions.
Probably more that in a server you can be systemd-free with current Debian without much trouble (well and some non-functional systemd-cruft lying around). I expect Devuan will become fully functional pretty fast once that changes. If it does.
But nice fail to understand what is going on on your side. Fits the picture.
Rust is a full-on irrelevant language for the purpose of this discussion. Nobody is going to rewrite all that software. (Rust has other severe problems, among them the blindness and fanaticism of its followers.)
If the people behind systemd had any actual Unix-development skills, that is exactly what they would have done. Instead we have a monster that tries to assimilate everything. Huge egos often coincide with small skills. This is a nice example.
It is not that bad. 2to3 already does a pretty decent job of converting. Some manual work required after that, but a "different language" is just hyperbole.
Indeed. And the good news is that there are now two larger distros that can can maintain eudev. Unless the systemd-cabal manages to get the kernel dependent on systemd (and that would be really bad for compatibility and security, so I doubt it is going to ever happen), it is actually not that hard to do a systemd-free (i.e. classical stable and reliable) Linux distro. You just have to maintain what is already there and works well, an idea that the systemd fanatics do not understand, of course. And applications that depend on systemd will be Linux-only anyways, which is not really smart, considering that there are a lot of Unix-like systems out there and in use.
For variable values of "certified" and the machine is not a secure device. Can still be enough to fulfill some formal process-requirements, even if it does contribute nothing on the security side. For that I agree.
SSDs keep a pool of erased sectors and a pool of ones to be erased. The latter contains non-erased sectors and is not necessarily reached or completely cleared by an overwrite. It requires special, disk and firmware specific software to access it, but still.
If you only want to sell a disk with not that critical data, an overwrite with zeros should be enough though.
One option would be to use, say, AES in counter mode with a key gotten from/dev/(u)random and overwrite with that. Should give you > 100MB/s on a modern CPU. But it seems nobody cares enough to implement that (would take maybe a few hours), I know that I do not.
By "modern disk" I mean "disk", not "disk emulator" (what an SSD essentially is), of course.
For an SSD, if you want an "eBay safe" erase, just do the zeroing. Some expensive data-recovery software may still recover buffers and the like. If you need more, do physical destruction. You cannot really trust that the ATA "Secure Erase" command does what it claims.
But the whole discussion here is not about disks with any really high-value data on them. For those, always do full zeroing, ATA Secure Erase (if an SSD) and then physical destruction. For those disks the small amount of money a sale can recover is not even worth the additional effort.
That already qualifies as a number of hoops for the average user, and that is the problem. Apparently, even googeling "erase disk" is far too complicated for the average user. Of course, you and me will have that Linux boot CD/DVD/USB-key already laying around, but the average user is apparently so limited that companies like Blancco make good business on something that is easy to do with free tools.
You can do that if you do not mind it taking much longer./dev/urandom only gives you something like 10...20MB/s. And nobody has data so secret that a few recovered bits put them at risk.
Was about to post that. For a nice progress indicator, use
dd_rescue -w/dev/zero/dev/target
Apparently, a single zero-overwrite is entirely enough for modern disks (say, newer than 15 years or so), as these are used close enough to the surface data density limit that even magnetic force microscopy can recover a few scattered bits at best after a zero-wipe.
I think the main problem here is that to do something like this under Windows, you have to jump through some hoops. And the other main problem is (of course) that people do not understand how disk storage works in the first place.
Slashdot Mirror
As the bosses will do analyses like "Which are the 1% I should fire", the matching algorithm (no AI in there) will resort to partial syntactic matches when it cannot fulfill the quota otherwise. Even a name with suspicious parts will get you fired then.
People will just use other channels for that type of communication. And there is also a serious risk: Many people will not communicate needed information for fear to be caught by this. In the ultimate consequence this can do much more damage than it helps.
Rushing in "Agile" in 2 months will not work. Anybody with the skills would have declined on that alone.
And that sums it up nicely.
For one thing, many unemployed have no marketable skills. Their skills may have gone out of demand or they may not have been able to acquire any currently useful skills in the first place. That is going to become very common, as we are moving into a post-labor economy where producing goods and services takes much less effort than is needed to keep a workforce employed. In addition, many remaining jobs have far higher skill requirements.
Unless that problem is solved, society as a whole will disintegrate. For example a basic free income is a possible solution to keep society functioning. There are others, but "work" as primary means to distribute money is becoming less and less able to do the job.
The other thing is that a 2 month commitment is not worth moving or making larger changes in your life and quite likely, they did not offer reasonable conditions.
Probably more that in a server you can be systemd-free with current Debian without much trouble (well and some non-functional systemd-cruft lying around). I expect Devuan will become fully functional pretty fast once that changes. If it does.
But nice fail to understand what is going on on your side. Fits the picture.
Using /dev/random would be funny, It gives you down to 10 bytes/sec and less on a lightly loaded system. Use /dev/urandom.
Other than that (and the gun obsession), I agree. Hammer to the PCB, remove cover, hammer to the platters, done.
Rust is a full-on irrelevant language for the purpose of this discussion. Nobody is going to rewrite all that software.
(Rust has other severe problems, among them the blindness and fanaticism of its followers.)
Indeed. They should have bought Sun and have it continue doing Java. Would have been cheaper than what is now happening.
And so we have both of them, for the time being. I do not see a big problem.
If the people behind systemd had any actual Unix-development skills, that is exactly what they would have done. Instead we have a monster that tries to assimilate everything. Huge egos often coincide with small skills. This is a nice example.
It is not that bad. 2to3 already does a pretty decent job of converting. Some manual work required after that, but a "different language" is just hyperbole.
Indeed. And the good news is that there are now two larger distros that can can maintain eudev. Unless the systemd-cabal manages to get the kernel dependent on systemd (and that would be really bad for compatibility and security, so I doubt it is going to ever happen), it is actually not that hard to do a systemd-free (i.e. classical stable and reliable) Linux distro. You just have to maintain what is already there and works well, an idea that the systemd fanatics do not understand, of course. And applications that depend on systemd will be Linux-only anyways, which is not really smart, considering that there are a lot of Unix-like systems out there and in use.
For variable values of "certified" and the machine is not a secure device. Can still be enough to fulfill some formal process-requirements, even if it does contribute nothing on the security side. For that I agree.
SSDs keep a pool of erased sectors and a pool of ones to be erased. The latter contains non-erased sectors and is not necessarily reached or completely cleared by an overwrite. It requires special, disk and firmware specific software to access it, but still.
If you only want to sell a disk with not that critical data, an overwrite with zeros should be enough though.
For /dev/urandom, you assume wrong, unless you have a very, very slow disk. For /dev/zero, you are right.
One option would be to use, say, AES in counter mode with a key gotten from /dev/(u)random and overwrite with that. Should give you > 100MB/s on a modern CPU. But it seems nobody cares enough to implement that (would take maybe a few hours), I know that I do not.
Still not trustworthy unless you trust the secure erase. I don't.
Unless it is a report digitally signed by a secure erase device, that report is worth about as much as a person certifying the erasure.
Ooops ;-)
By "modern disk" I mean "disk", not "disk emulator" (what an SSD essentially is), of course.
For an SSD, if you want an "eBay safe" erase, just do the zeroing. Some expensive data-recovery software may still recover buffers and the like. If you need more, do physical destruction. You cannot really trust that the ATA "Secure Erase" command does what it claims.
But the whole discussion here is not about disks with any really high-value data on them. For those, always do full zeroing, ATA Secure Erase (if an SSD) and then physical destruction. For those disks the small amount of money a sale can recover is not even worth the additional effort.
That already qualifies as a number of hoops for the average user, and that is the problem. Apparently, even googeling "erase disk" is far too complicated for the average user. Of course, you and me will have that Linux boot CD/DVD/USB-key already laying around, but the average user is apparently so limited that companies like Blancco make good business on something that is easy to do with free tools.
DBAN is nice though. Had not heard of it before.
You can do that if you do not mind it taking much longer. /dev/urandom only gives you something like 10...20MB/s. And nobody has data so secret that a few recovered bits put them at risk.
Was about to post that. For a nice progress indicator, use
dd_rescue -w /dev/zero /dev/target
Apparently, a single zero-overwrite is entirely enough for modern disks (say, newer than 15 years or so), as these are used close enough to the surface data density limit that even magnetic force microscopy can recover a few scattered bits at best after a zero-wipe.
I think the main problem here is that to do something like this under Windows, you have to jump through some hoops. And the other main problem is (of course) that people do not understand how disk storage works in the first place.
Aehm, do you know what an endoscope is?