

No, he had access but clearly the router admin interface wasn’t set up to allow remote access. He then needed to access the router from a browser inside the LAN, and he did have the proxmox host configured correctly to access remotely.
No, he had access but clearly the router admin interface wasn’t set up to allow remote access. He then needed to access the router from a browser inside the LAN, and he did have the proxmox host configured correctly to access remotely.
Yeah knocking them over while active would probably not be the best, you can even hear the stress on the spindle bearings if you rotate a running hard drive. However you should be free to mount them (securely) in almost any orientation given the discussion in this old post: https://www.silentpcreview.com/forums/viewtopic.php?t=21533&postdays=0&postorder=asc&start=0
Then why does the post say “we are looking” as if you are part of a group or team related to this?
Yeah… I’m laughing at this guy saying the AUR is much better than installing from a random Github repo. Same level of trust haha.
Also, not everybody NEEDS to know how something works to use it. And, just getting someone onto Linux in the first place with a 90% working system seems better to me than them working hours and hours to build a minimal system in Arch … because it would take even more hours to replicate their workflow on Windows or Mac. I think this is a great example of “perfect is the enemy of good” when trying to get people to adopt something.
However, I definitely believe that if you want perfection, you go to Arch or a derivative and you do it yourself, no automation. But that should be a choice… I do plan on one day switching from Tumbleweed to Arch, but I am not ready for the time commitment. Plus, NVIDIA finally fixed their shit, so I want to enjoy playing games for a while now that the weird issues and visual artifacts caused by the old non-explicit-sync drivers are gone!
Short TL;DR: nothing burger
Longer TL;DR: Linus sees bad changes to the git tree by Kees Cook that he interprets as being of human origin and intentional, calls them “malicious” changes and orders that Kees Cook’s privileges be revoked. Turns out that the “git-filter-repo” tool being used was actually the culprit as it is very powerful and incorrect usage explains the changes. Discussion then moves toward implementing safety checks in the tooling. Kees gets his permissions back.