• 1 Post
  • 36 Comments
Joined 1 year ago
cake
Cake day: February 9th, 2025

help-circle
  • OpenSUSE Tumbleweed has a GUI for almost everything. It has a nice GUI for basic system config, and uses YaST2 for deeper settings, and it uses Discover for Flatpaks as well as system library updates.

    Although, I have seen a couple people say Discover shouldn’t be used for doing system updates because it can fail, and to only use it for Flatpak updates and installs. I dunno. But it’s not like typing sudo zypper dup to do a distro upgrade is hard, so I just do that out of an abundance of caution.

    OpenSUSE has some other cool features too, like having Snapper installed by default for system snapshots. It’s pretty easy to roll back if an upgrade goes sideways. There’s a boot entry that lets you open a previous snapshot as read-only and then you can make that snapshot permanent by creating a new top-level snapshot from it. So then you can at least use your computer while you try to figure out why the upgrade you did failed.

    You’ll probably want to use KDE as your desktop environment. It’ll be somewhat familiar if you’re use to Windows, and it has a lot of features that make it comfortable to use.

    There are lots of good YouTube videos on why OpenSUSE is pretty cool. Check some out.





  • I can’t tell you how many times I’ve accidentally pasted random private stuff from that goddamn middle click into WEB PAGES! Things that can read whatever text you type without having to explicitly submit anything. It’s a horrible thing for a new user to discover by accident. It’s such an unexpected feature to new users, and no one gets told about it, ever. You simply discover it by accident.

    This is a good change, not having it on by default.

    To all the haters of this idea, god forbid we make Linux less weird by default for people migrating from Windows.

    All that said, I have learned to love select-to-copy and middle-click paste. Especially in the terminal.




  • Yes, every distro requires a password for sudo. That’s the whole point of it. But editing .bashrc does not require sudo. You can add aliases and functions to .bashrc. A malicious script can append to .bashrc, and by doing so, it can alias sudo to be whatever command it wants. For instance, a malicious function. So the next time you run sudo it runs the malicious command, instead, which itself can act just like sudo and prompt you for your password. So now you just entered your password into a malicious function. Do you see the problem with this?






  • You don’t need to do anything special. Take an NVMe or SSD and put it internally in some PC—ideally the same computer you want to use it on, for driver reasons—then install Windows on it. (Windows won’t let you install to a USB device, so you have to put the drive internally in the PC.) Then take it back out, put it in an external enclosure, plug it into USB and it boots right up. (Well, as long as you know how to choose a boot device at startup or make USB a higher priority than your internal drive.)

    I just did that on my laptop by taking out the Windows NVMe, putting in a new one for Linux, and then sticking the Windows NVMe in an enclosure.

    Obviously, this can’t work on a thumb drive, but it’s not terribly inconvenient to carry around an enclosure and a cable.

    (An LLM told me I should change some registry settings to make loading the USB drivers occur earlier during boot, but that doesn’t make much sense. How could it boot enough to load the Registry in order to know to load the USB drivers earlier? It’s already booting. But if you try this and have any troubles, I can probably figure out what Registry settings I changed. I’ve also done this with an M.2 SSD from one PC and booted it from a USB enclosure on a different PC, and I definitely made no registry changes then.)