There is nothing to refurbish in drives. They are just second hand devices. You can check if they are fine pretty easy and you need to take a look at the age (power on hours). I replace drives at 50k-60k hours, no matter if they are fine.
There is nothing to refurbish in drives. They are just second hand devices. You can check if they are fine pretty easy and you need to take a look at the age (power on hours). I replace drives at 50k-60k hours, no matter if they are fine.
Mine doesn’t satisfy them, either. I switched off TPM in BIOS.
I laughed a bit. Thanks.
If you break trains programmatically (by software) you’re an industrial saboteur.
That’s much worse than to hack them to work again.
Most of these observations are subjective. I’ve had some Seagate drives that worked well but were very hot and wasted energy. On the other hand WD was crap so far, starting with 3 TB. Not because of quality, but because of power saving features that were a major annoyance to me (green and some blue drives). Red drives I had were mostly fine, even they wore out pretty quickly (Load_Cycle_Count bugs). They ran at 0% health left for a few years and had other awful SMART and on-drive controller bugs.
Since Seagate and WD are essentially the same company and they lied about SMR before, I wouldn’t buy either of them.
I’ve seen someone using Adobe Acrobat just for splitting PDF documents.
Mutual agreement “look ok, but no touch” is perfect.
In 2020 there have been around 3000 data centers in Germany. Sounds more plausible to me.
Germany only 521? Seems a bit low.
What counts as a “data center”? How many rooms and how many racks does it need to have?
I don’t like the term “clever” in code, because sometimes it means “I’m too dumb to understand it”. Simply don’t touch clever code, unless you really understand it.
Best example is the fast inverse square root function in Quake. Yeah… it’s clever, but replace it by simple maths and let Quake have performance problems.
On the other hand, using AI for more than assisted coding is never clever. Some day some fuck will use it in medicine and will actually kill people. AI is not at fault here! It’s the programmer who killed a patient in this case by being irresponsible and lazy.
Devs care to debug code only if they believe in its quality. Otherwise they write the code again from scratch. This is also cheaper than debugging.
AI code is not clever. It’s all developers averaged. Even if it worked properly, you’d get average quality code.
It’s rather lazy and cheap. This is where the quality is lacking.
I only know pasta with sugar and:
How? I have cups in my kitchen, but no ozes.
Are you looking for something like cached credentials?
touch 'C:\WINDOWS\SYSTEM32'
Read above please. You cannot import GPL code into BSD licensed code without restricting the code distribution. In the other direction, you can do it and just add a notice about the license. It does not add restrictions to the distribution. Otherwise Linux distributions wouldn’t even have OpenSSH in base install images.
Of other software, yes. For example Linux distributions can use the BSD or MIT licensed code without any problems.
But it does not allow to remove the license from the software.
On the other hand GPL code cannot be imported into BSD code without introducing restrictions.
If you think about how many people use proprietary Android by Google, it is exactly comparable.
Comparing numbers is pointless here. Fact is that GPL has more conditions when you’re allowed to use and modify the code. More conditions means more restrictions. And this means, less freedom.
KVM > VMWare