- 0 Posts
- 113 Comments
It might be my lemmy client but when I go to that link I just see a basic steam next fest post with a Linux picking section from a different user.
What am I missing?
If you don’t mind me asking, why did you choose Zorin? How do you hear about Zorin?
That’s not actually true. Technology connections made a few videos about it.
Beta bs VHS: https://youtu.be/hWl9Wux7iVY
The broadcasting Beta format was basically a whole different format compared to that you could get at home. Completely unrelated.
Studio Beta https://youtu.be/hGVVAQVdEOs
mholiv@lemmy.worldto
Linux@programming.dev•Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
3·4 months agoExactly this. The people who designed secure boot and TPMs were not idiots. You can’t trick a properly set up TPM configured with secure boot in any realistic setup.
mholiv@lemmy.worldto
Linux@programming.dev•Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
14·4 months agoIt won’t refuse to boot. It’s just that any automatic metric based decryption won’t work.
If you are using a TPM to automatically unlock luks and also manually removed the password backup before hand you could lose your data forever. That is true.
But if you kept the password based decryption stuff you could still manually unlock stuff. Just like secure boot was never there.
The difference would be that there could be no secure attestation that the kernel count trust/use without secure boot.
Like secure boot is really cool on Linux if you learn about it. Like sbctl alone is great for verifying backups and stuff.
I recommend reading through the arch wiki if you want to learn more. It covers a lot of stuff. https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot
mholiv@lemmy.worldto
Linux@programming.dev•Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
163·4 months agoIt won’t brick your system forever??? You just turn it off in your bios. Then you have no secure boot. Just like it was never there.
mholiv@lemmy.worldto
Linux@programming.dev•Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
311·4 months agoIf you don’t care about boot chain attacks it isn’t bad at all.
If you do care about boot chain attacks it’s bad because it allows someone to replace things like the efi binaries, grub, or your kernel with backdoor-ed versions and there would be no way to detect this from the running system.
Secure boot checks for this stuff. You can read more here:
mholiv@lemmy.worldto
Linux@programming.dev•Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
171·4 months agoYou can but then you don’t have secure boot.
mholiv@lemmy.worldto
Linux@programming.dev•systemd has been a complete, utter, unmitigated success
2·5 months agoYou can if you want to. But I don’t think that is best practice. The idea of quadlets is the bring Linux norms to containers. You contain and manage all permissions for that container in that user.
I personally have completely separated users and selinux mls contexts for each container group (formerly docker compose file) and I manage them thusly. It’s more annoying but it substantially more secure.
This being said I think you can do it as root. I think this might work but I am not certain
sudo systemctl --user -M theuser@ status myunit.service
mholiv@lemmy.worldto
Linux@programming.dev•systemd has been a complete, utter, unmitigated success
1·5 months agoAre you placing your service files in
~/.config/containers/systemdof the home dir of the user you want them to run as?Here is a link: https://linuxconfig.org/how-to-run-podman-containers-under-systemd-with-quadlet
mholiv@lemmy.worldto
Linux@programming.dev•systemd has been a complete, utter, unmitigated success
4·5 months agoNot true. I run them rootless on my server as we speak. :)
I mean it could be Mutex, or Rwlock or anything atomic. It’s just when I have to put stuff into an Arc<> to pass around I know trouble is coming.
You’ll be fine. You will learn the lifetime stuff and all will work out. It’s not that bad to be honest.
I mean yah. That’s what it takes. But like when I try to write code around Arc<_> the performance just tanks in highly concurrent work. Maybe it’s an OOP rust skill issue on my end. Lol.
Avoiding this leads, for me at least, to happiness and fearless, performant, concurrent work.
I’m not a huge fan of go-lang but I think they got it right with the don’t communicate by sharing memory thing.
Skill Issue.
For reals though adopting a functional style of programming makes rust extremely pleasant . It’s only when people program in object oriented styles that this gets annoying.
No loops, and no state change make rust devs happy devs.
They probably won’t get specific.
But I will say that the comment here is a quintessential example of an anti Wayland/SystemD complaint.
Nothing specific ever. Just “it’s a mess and buggy and slow”.
This being said by me making this comment the original poster might come up with the some specifics just because they feel called out.
It makes sense to stick with something that’s good. I think the small gain going from Colemak to Colemak-DH wouldn’t be worth the struggle.
I use Engram and don’t plan on changing even though I suspect better layouts do exist. The effort is too high for a 1% gain. Lol.
It’s slow to install but I strongly recommend the services of keybr.com They have modes that install those specific layouts.


Prusa printers are MUCH better than Ender 3s just FYI. Not even in the same class. If you end up getting a modern prusa you’ll get something like the Bamboo but more community driven and with real technical support.