

For someone who is famously not a people person, Linus Torvalds is surprisingly nice and chill.
(BTW, he lost a lot of weight. Does his treadmill actually works?!


For someone who is famously not a people person, Linus Torvalds is surprisingly nice and chill.
(BTW, he lost a lot of weight. Does his treadmill actually works?!


Secureboot is a security measure to make sure the boot environment have not been tampered with. It would detect malwares that attempt to modify the boot environments. According to ArchWiki, it ensures “core boot components (boot manager, kernel, initramfs) have not been tampered with”, which would protect against initramfs-swap attacks like de-LUKS, however there are conflicting reports on the internet, and I have not tried myself.
I personally don’t find it makes Linux harder to install, like others suggested. Unless you use a surface device, it will happily accept the key for most common linux distro, including Ubuntu, Debian, Fedora, and many more. For most custom distros, you can easily register its key via MOK (require root privilege and confirmation in the UEFI, for security purpose). In fact, Debian project is quite clear on SecureBoot not being a tool for MS to monopolize the desktop market: https://wiki.debian.org/SecureBoot#What_is_UEFI_Secure_Boot_NOT.3F .
However, if you need to load additional kernel modules, like NVIDIA drivers, secureboot can get quite annoying. I am actually quite interested in why Windows don’t have a problem loading additional drivers, yet Linux do.
In the end, I feel if you are using a distro that works with secureboot, there is no reason to leave it off; if you find it annoying, yet okay with a downgrade in security, then you might want to leave it off.
I hope image-based distro can solve this issue. In general I feel a lot of these breakages are caused by repeatedly migrating configuration files, yet fresh install usually fixes these issues.
I think one of the advantage of image based distros is that they are much more principled in migrating config files.


What brand of VPN do you use to bypass it, many of my friends are there quite frequently, none of them have a mainstream solution for it.


Last time I was there, express does not work, and I heard proton also does not work. However, my mobile carrier by default routes all roaming traffic through UK, so that did work.


China blocks most IPs from foreign cloud providers like AWS or Digital Ocean. And if I am not mistaken, they can also block some VPN protocols (tor is not a VPN protocol, but it is very blocked, I don’t know if tor bridge works), but I am not sure which exactly.


Is this where pika-pika-chu came from?
I think the best tip is to not be too hard on yourself. Using linux doesn’t mean abandoning Windows, even if you feel overwhelmed and need to go back to Windows, that is totally okay, just try again when you feel comfortable.
If you are confused please ask questions, people love to help beginners. Finally, like others, I think mint is a great starting point. If you have time, you can also follow some linux content creators on YouTube or PeerTube.


What about bottles?


I think most people would use the publisher’s website first and then resort to scihub, because scihub requires a doi or publisher’s link to get the paper.
I don’t think this causes much concern, even if so, I believe a good amount of blame should still fall on the publishers and academic systems that encourages gatekeeping knowledge. Especially when these knowledges are generated by public money, then the public should rightfully have access to them.


It is also insecure with possiblity to crash your computer, the only advantage is that it is cheap.
My strategy is to always install program with flatpak, SDKs are also installed as flatpak, find graphical alternatives to command line programs. I don’t use command line a lot, so I don’t need fancy tools for it.
I only have one system package installed for inputting unicode math symbols. So that I have a clean and easily migratable system.
I might add, everyway actually seek to “consolidate” all the older ways, and always ends up adding to the ways needing to be consolidated.
I think by ARM you mean RISC-V? Both of them are RISC-based, but very different. RISC-V is not very close to consumer adoption anytime soon.