it’s embarrassing but for me it’s thinkfan. Instead I wrote my own solution in bash.
it’s embarrassing but for me it’s thinkfan. Instead I wrote my own solution in bash.
I don’t think it would be great for a pie hole on a gigabit connection. (if you have s slow connection then it’s good ofc)However there are use cases it’s good for. Print server, smb server, kitchen radio with Pyradio, retro gaming etc
Immutable distros like Silverblue or Bazzite are the only path I see that can work for normies. However flatpak itself has to mature more, theming anomalies need to be dealt with somehow for example.
Mint is only good to ease a technically inclined person into the linux world.
You have to reboot yes, however only once. The step where you boot into your snapshot is redundant.
You are making it unnecessarily difficult for yourself. Rolling back a snapshot that you made before the intentional messing around is less effort than rebooting twice for seemingly no reason. Booting into a snapshot is not sandboxing, it’s not an added layer of security against a malicious package.
Don’t recommend leaving it like this, because if Awesome ever releases an update you’ll lose your config.
Where exactly did you copy your rc.lua?
Here’s mine;
Flatseal’s job is to do that. As for the note app, that’s not great, but you can use flatseal to take away those permissions after installation.
I don’t blame the guy for being human and it’s free software etc, but this is reality bad optics for immutable distros. If my nephew and grandma are going to need manual interventions like this one, then might as well use a less restrictive system. The promise of seamless and easy updates are the main draw for me.
It would be much appreciated if UniBlue made the update process more robust and more resistant to such mistakes.
(also curl piped into sudo bash is way more common than it should be)
New users shouldn’t be recommended to use Arch flavors.