We’re talking about poisoning a single person not a gas cloud. Poisoning a single person vs drone striking a wedding.
We’re talking about poisoning a single person not a gas cloud. Poisoning a single person vs drone striking a wedding.
Nerve agents compared to drone strikes look humane and civilized.
The legal reasons was because the Linux Foundation is based in the USA and the targeted devs worked for companies explicitly sanctioned by the USA. Linus said he knew and trusted the devs he was forced to delist.
The Linux Foundation needs to relocate to some stable neutral country like Switzerland.
Every other square mile is cleared for logging as some sort of forestry preservation/logging compromise. The spaces logged are clear cut.
Western Oregon
Its all over the pacific northwest. Washington, Oregon, Idaho, Montana. Its not a specific spot.
Most frequently I use it as an interactive cd
. Docs on how
Saves me a whole lot of ls
and cd
or tabbing through completions.
Switched from ranger to yazi months ago. There’s some UI choices that I miss but the configuration via toml and lua plugins is way better than rangers.
I would like to find a git modeline plugin. Its wild to me that they have a zoxide integrated and keybound by default but no git integration.
Manipulating vim.g.clipboard
is the trick. I’ll have to write some command that sets the clipboard provider directly.
Thats for sure what’s happening. The remaining error message makes that clear but I couldn’t copy the full message
fwiw headscale is pretty easy to self host and has minimal system requirements.
I think PopOS can safely assume that its being installed on a laptop with only one drive. If there’s multiple drives involved then the setup gets far more complicated as you then must go to something like an LUKS on LVM setup. Basically, for a desktop there’s no safe defaults for FDE.
I’m pretty sure all the major distros have FDE as an option in the installer its just never on by default. Fedora does the same but with BTRFS on LUKS. I’m sure Debian does. Someone else says OpenSuse does. Maybe some derivative distros don’t but I suspect the ones with an graphical installer do.
Looks like they use eCryptFS. Never heard of it before so thats neat. I can see using it on systems where you can’t reinstall the system with Dm-crypt but it most cases I suspect Dm-crypt is a better alternative.
Idk if its faster or slower than Dm-crypt.
The standard route is to decrypt on boot. It happens after GRUB but before your display manager starts. IDK if there even is a setup that has you “decrypt on login”. Thats sounds like your display manager (sddm for KDE) is decrypting system which is not possible IMO.
Unless your laptop somehow has multiple drives you’ll want to use the “LVM on LUKS” configuration. 1 small partition for /boot
. The rest gets LUKS encrypted, and an LVM group is put on the LUKS container. Or you could replace LVM with btrfs.
This will require wiping your system and reinstalling so you have some reading to do.
The arch-install
script in the live iso has options for full disk encryption.
If you suspend to RAM your system will stay unencrypted, because your ram is not encrypted. if you suspend to disk (aka hibernate) your system will be encrypted. You go through the boot loader when waking from hibernation but it just drops you off where you left off.
You need a swapfile for hibernation so make sure its inside the LUKS container.
Unironically try turning your computer off and on again.
Tmux settings are global and persistent. Just deleting your config files is insufficient. You have to kill the server and restart it. Uninstalling and reinstalling will not kill a running tmux server. tmux kill-server
should work too.
Now if it persists across reboots, then there must be a file still lingering somewhere. If you are sure your home directory is clean you can try searching whatever you installed in /etc.
This is all assuming you’re trying to go back to a clean slate and failing. If the borked status bar is the result of your current .tmux.conf
, then you’ll have to post that.
I spent like a week on this last month. Usually you use enumeration, but I wanted to allow client code to define their own strategies. I tried the Box<dyn MyTrait>
pattern because some of my strategies were composed of other strategies, and I wanted to clamp down on generic types. But I kept running into weirder and weirder compiler errors. Always asking for an additional restriction on the base trait. X, must be Copy
, must be Send
, must be Sized
, must be 'static
. On and on. My experience is if I’m getting a bunch of those then I’m off the Golden Path. So I just embraced the verbosity of using generics and its easy. Yes its more code but its better code.
Its going installed binary is rg
.
Who actually hates on declarative/immutable distros as a concept? Its always the actual usability of the specific implementations thats the problem. Stale packages, poor documentation.
Still hosted on GitHub, a property of MicroSoft.