The most encouraging thing in the whole talk for me was when he told a roomful of IT folks that they need to join or form Unions and they cheered.
The most encouraging thing in the whole talk for me was when he told a roomful of IT folks that they need to join or form Unions and they cheered.
Not true.
He can’t prevent anyone that received the code under the GPL from using (and distributing it) under the old license. He also can’t relicense code that he received under the GPL only under the new license.
If he receives a new license from the other contributors to distribute under a more restrictive license, he can do that because he has a dual license to the code and is not relying on the GPL for his right to distribute.
Oh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
Gonna have to disagree with #3 - stopping Vim is not necessary for this. There’s the builtin :!
command.
Absolutely not. At those densities, the write speed isn’t high enough to trust to RAID 5 or 6, particularly on a new system with drives from the same manufacturing batch (which may fail around the same time). You’d be looking at a RAID 10 or even a variant with more than two drives per mirror. Regardless of RAID level, at least a couple should be reserved as hot spares as well.
EDIT: RAID 10 doesn’t necessarily rebuild any faster than RAID 5/6, but the write speed is relevant because it determines the total time to rebuild. That determines the likelihood that another drive in the array fails (more likely during a rebuild due to added drive stress). with RAID 10, it’s less likely the drive will be in the same span. Regardless, it’s always worth restating that RAID is no substitute for your 3-2-1 backups.