OP’s already running LXC on the host, so… Namespaces are namespaces…
I don’t see what performance issues there would be with that.
OP’s already running LXC on the host, so… Namespaces are namespaces…
I don’t see what performance issues there would be with that.
Just create an LXC container to run your dockers, all you have to do is make sure you run the LXC as privileged and enable nesting.
My guess is you didn’t install virtio drivers. That should help immensely with graphic acceleration.
And my 25 year old MIPS machine still runs BSD and Linux
MakeMKV can do that for you.
Canada did the same thing as well around the same time period.
Well not if you own a block of IPs ;)
If you self host, its mandatory
Technically there’s nothing in the SMTP specs that forbids using IPs directly, but yeah good luck with that 😅
I’m good. I know very well there are uses cases for a self signed cert. LE is still far more practical for 99% of use cases, even internally.
But then you have to distribute CAs to all the devices that will reach this service, and not all devices allow that.
I’m with you, but that’s why I’m automating certificate expiry checking somewhere else (in my home assistant install to be exact).
Nothing in there is incorrect.
I don’t think I’ve ever seen people say it has CIA financial backing. It did however until only a couple of years ago have strong ties to the State Department’s Open Tech Fund (from the same financial envelope that brings you RFA/RFE/VOA).
KeePassXC has an option for shared database.
https://keepassxc.org/docs/KeePassXC_UserGuide#_database_sharing_with_keeshare
Pretty damn easy.
qemu-img convert -f vdi -O qcow2 Windows10.vdi Windows10.qcow2
Here’s a more complete guide: https://cubiclenate.com/2024/05/30/converting-vdi-to-qcow2-step-by-step-guide-for-virt-manager-migration/
https://virt-manager.org/ is a no brainer. Built upon libvirt/Qemu/KVM it’s way more powerful and pretty much just as easy to use. There is zero reasons to use anything else.
There are plenty of certificate authorities that will sign a personal S/MIME cert. For example: https://www.digicert.com/tls-ssl/secure-email-smime-certificates
That’s incorrect there’s full SSL on deb.debian.org
Oh maybe i should look for a used one! It would make a decent mobian device I think (though it’s a little low on RAM 8Gb would be amazing)
Yup, you’re all set. You’ll need to use
cryptsetup resize
as well