deleted by creator
deleted by creator
Vested interest? Literally vested stock options. Well, by now they’ve already been used to purchase stock.
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.
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.
Gonna have to disagree with #3 - stopping Vim is not necessary for this. There’s the builtin :!
command.
Don’t forget /auto, for things that get automatically mounted when you first access them (autofs)
Nah. This has happened with every major corporate antivirus product. Multiple times. And the top IT people advising on purchasing decisions know this.
Favorite would be a highly customized zsh.
fizsh (not fish) is what I actually end up using, as I can’t be bothered to copy that config around and retune it for each machine. Gives me the syntactic sugar of zsh with common default options on by default, an OK default prompt, and doesn’t break POSIX assumptions like fish. Also Installs quickly from the package manager without needing to run through the zsh setup each time - unlike oh-my-zsh. And if I still need customization, all the zsh options are still there.
And that assumes no second hand
Exactly.
Having known multiple trans people and heard them talk about the arguments for and against early disclosure: Fear.
They may not be public about their status, and fear exposure to family or coworkers seeing their public profile.
They may fear harassment from transphobes. This could range from DM accusations of pedophilia to religious screeds to doxxing to death threats.
They may be trying to avoid “chasers.” There are some people for whom a trans body (particularly a transfem body) is a fetish, who don’t actually care about the person inside. Plenty of transpeople don’t appreciate that kind of attention.
Fear of rejection. They may believe that nobody will respond if they’re open about not being cis.
Also two less fear-related (and less common) possibilities:
Ideology. To some people, specifying “transman” or “transwoman” reinforces a social distinction they find invalidating or don’t accept. How many profiles have you seen that specify themselves as “cisman” or “ciswoman”? For these people, it’s a way of rejecting cisgender normativity.
Maybe they just aren’t ready to talk about their genitals yet, or have their first conversation be about their surgical plans or history. Not only can get really repetitive having that be the first conversation with every single match, it means they don’t get any of the information they’re looking for about a potential partner until much later in the process and have to invest a lot of their own time up front. Just like you want the salient information you care about early on, so do they.
To be even more explicit on the last point, that means regularly updating OpenWRT and all your containers, not just the server’s base OS