You can find the "old" commits using "git reflog".
I've fixed a lot of botched rebases with that :)
561 karma · joined September 21, 2020
You can find the "old" commits using "git reflog".
I've fixed a lot of botched rebases with that :)
I think a COP of 2 at 5°F (-15°C) is pretty good.
But when if the first train is experiencing something it shouldn't, like a big accident/derailment, the landscape could be a way better brake than the train's own brakes. When does the second train start its emergency braking?
libvirt/kvm supports it, Hyper-V supports it, Virtualbox supports it, ESXi supports it.
Current users weren't automatically updated to the new plan, so for them it's a big storage upgrade at no extra cost.
People don't have to opt in for you to keep the data for technical reasons, for instance if you keep IP addresses for while to find and block abuse, but you can't keep data longer than strictly necessary and can't use the data for other purposes than you declared beforehand.
Write down your policies and put them in an (again, easy to read, understand and find) privacy statement and you should be pretty much GDPR-proof.
I've set up my RAID to not haeve a "bad block list" so I _think_ it will try fixing it a few times, and drop the drive if there are too many errors in a row.
Should be easy enough to try with a "test" RAID made out of a bunch of files (or even USB sticks).
The biggest downsides I can think of are:
1. You have to do an initial initial initialization of checksums on the disk, which takes forever.
2. Automatically bringing up the dm-integrity layer of the plain disks at boot time is a bit of a dark art involving udev rules.
If you skip the checksum initialization step and add the device to the RAID immediately, it _mostly_ works, because disk blocks are rewritten by the resync/reshape, but then on reboot it fails because some part of the system tries to read an otherwise unused sector (probably to find metadata or a partition signature of some kind?), and then determines the device is unusable because of read errors (dm-integrity errors show up as read failures to the next layer in the stack).
Putting the HBA in the second x16 ("electrically x8") slot makes both work at x8 speeds, as those lanes are "shared".
In my home server for instance, which is built on a consumer μATX board, the wider PCIe slots are filled with a GPU and HBA, which leaves no way to add 10GigE without spending a lot of money on a new motherboard and CPU - or finding a way to use the M.2 slot.
And they're not very good at their job (or maybe they are, if you're Facebook): https://www.euractiv.com/section/data-protection/news/irelan...
In the Netherlands, in the 80s-00s at least, hanging up cleared your line, so picking it up again would get you a fresh dialtone even if the other side didn't hang up (and the other side would get a modified "busy" signal if you hung up on them).