If I decide to put up with this type of attitude

Your the one insulting me.

Would you say pointing the finger at the linux devs and maintainers saying they should work harder does improve anything and drives ppl to volunteer?

Maybe you should take a read on Wikipedia on what gatekeeping is before you insult me. https://en.m.wikipedia.org/wiki/Gatekeeping_(communication)

OC stated those things ‘should be worked on’. What else is it than blaming ppl?

Yes things could be better, but saying things should be better while sitting on their ass and doing nothing is just not correct to say. If you say it should be better then you should take part in it getting better.

I absolutely disagree with you. If a manufacturer does not care about Linux support, it’s on the manufacturer. Do not blame the thousands of unpaid volunteers and a few paid ppl for not supporting a specific BT chip or controller or whatever.

The signing issue is so on OP cause disabling secure boot or using a supported distro like ubuntu could have fixed that, and yes you can run Windows 11 with Linux dual boot without secure boot.

Basically everything you stated, Bluetooth, Controller and GPU is hardware.

Your experience is probably different since you still think and act like you use windows. This is normal. When you are used to something and then switch to something that works differently you will run into problems.

Looks like you used hardware that was designed for windows and are blaming it now on Linux.

I am not understanding the issue you have that requires signing of drivers.

Yes some Bluetooth devices lack the support from the manufacturer’s for Linux, the Controllers i have used work great, at least for my needs.

Controllers have better support Linux for ages. Not understanding the issue here either.

Troubleshooting on Windows sucks at least to the same degree. The same non specific error message gets you 50 possible solutions.

No need to announce your departure.

Lennart Poettering intends to replace “sudo” with #systemd’s run0. Here’s a quick PoC to demonstrate root permission hijacking by exploiting the fact “systemd-run” (the basis of uid0/run0, the sudo replacer) creates a user owned pty for communication with the new “root” process.

To my understanding that actually solves issues. A lot of ppl already prefer other tools like doas since sudo is basically “too big” for what it does.

More code means more potential bugs. run0 has to my knowledge significantly less code. And the benefit of not relying on SUID.

In the end, you do you. The big distros will adopt what is good for them and good to maintain. You do not have to use it.

Depends on the root setting. And depends on your goal. What is the purpose of the proxy? I doubt that it is easy to bypass, but you still could run a Proxy or VPN as user, this would not bypass the proxy but any filtering/blocking would not be possible. Etc

You can simply just download a binary and run it.

I’m also of the opinion that if a bad actor capable of navigating the linux file system and getting my information from it has physical access to my disk, it’s game over anyway.

I am sorry but that is BS. Encryption is not easy to break like in some Movies.

If you are referring to that a bad actor breaks in and modifies your hardware with for example a keylogger/sniffer or something then that is something disk encryption does not really defend against.

With initramfs and dropbear you can make the password prompt accessible over ssh, so you can enter the password from anywhere.

Edit: For debian it is something like

• install dropbear
• configure dropbear for initramfs
• generate key pair
• generate initramfs
• You are done.

Full disk encryption on everything. My Servers, PCs etc. Gives me peace of mind that my data is safe even when the device is no longer in my control.

deleted by creator

https://en.m.wikipedia.org/wiki/Initial_ramdisk

In Linux systems, initrd (initial ramdisk) is a scheme for loading a temporary root file system into memory, to be used as part of the Linux startup process. initrd and initramfs (from INITial RAM File System) refer to two different methods of achieving this. Both are commonly used to make preparations before the real root file system can be mounted.

As i said 2 different things, initrd was used to create a ramdisk, a block device. Initramfs basically directly offers a filesystem instead of a block device.

systemd has now a interface called systemd-initrd: https://github.com/systemd/systemd/blob/main/docs/INITRD_INTERFACE.md

initrd was deprecated see here: https://lkml.org/lkml/2020/7/14/1508

Initramfs and initrd are 2 different things, the problem where the confusion happens is that initrd is deprecated since a few years.

Now, systemd has implemented an interface called systemd-initrd which basically is initramfs.

I guess here is were the confusion lies. Nowadays everything is initramfs even if it called initrd.

The original initrd differs from initramfs, but it is no longer a thing.

Sorry if i came across a little bit snappy have not had a great week so far.

That they are 2 different tools. Here

Nope, both do the same thing but they are not the same thing.

This does work anymore for some ISOs. Depending on the version and Region i actually could not continue without connecting it to the internet. The oobe\bypassnro does work more reliably.