Well, it was worth a shot.
data1701d
joined 1 year ago
I don't do it for my desktop because 1) I highly doubt my desktop would get stolen. 2) I installed Linux before I was aware of encryption, and don't have any desire to do a reinstall on my desktop at this time.
For my laptop, yes, I do (with exception of the boot partition), since it would be trivial to steal and this is a more recent install. I use clevis to auto-unlock the drive by getting keys from the TPM. I need to better protect myself against evil maids, though - luckily according to the Arch Wiki Clevis supports PCR registers.
I wouldn’t necessarily say that - Debian and FreeBSD releases have roughly the same support lifespan, meaning if installed on release day, you’d get a few (~5 years) years of support without major upgrades.
I’d say both systems have a high chance of success at upgrading to the immediate next version, so that becomes maybe 7 or 8 years when adding the years of support left on the now older immediate next version.
For a second immediate next upgrade, you might be right that a BSD has a better chance of surviving.
I wouldn’t know about Open SD, though, as they operate on point releases and I don’t know to what extent they prevent breaking changes.
I think you might win.
That might me it - when I search older media, say The Andy Griffith show, sure enough there are a crap ton of plates.
It might be a sort of Venn diagram thing - Trek/Wars plates came at the dusk of the commemorative plate era, while the fans were more likely than others to buy collectibles like plates, making them seem unique from other fandoms.
I just realized another thing about April - assuming humans live 120 years on average in the Trek universe and April got turned roughly 20 in Counter/Clock, an elderly April could still be alive in the 2360s or 70s.
I never get why people use RAR anymore when tar archives are good now.
I would love that! Give the lost part of the Monster Maroon era (mid 2290s-2340s) some love.
The weird thing is April from SNW should canonically still be alive due to TAS:”Counter-clockwise Incident”.
I feel like I had a problem very much like this with Debian Testing on my Surface Go 1 (and I think my desktop too) a couple years back, and it turned out there was issues with /etc/nsswitch.conf. I can't remember exactly what I did, but this is the current contents of that file:
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: files systemd
group: files systemd
shadow: files
gshadow: files
hosts: files mdns4_minimal [NOTFOUND=RETURN] dns myhostname
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Compare yours - maybe even post it so I can try to reproduce the issue on my machine. Anyhow, hope it helps, and good luck.
Do your servers have TPM? Clevis might be the way to go; I use it on my Thinkpad and it makes my life easy. If the servers don’t have TPM, Clevis also supports this weird thing called Tang, which from what I can tell basically assures that the servers can only be automatically decrypted on your local network. If Clevis fails, you can have it fall back to letting you enter the LVM password.