• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle





  • As well as the package manager (and release type/schedule as mentioned in a different reply) you might want to look at the overall structure.

    Does the distro use selinux or app armor (you probably want at least one)? Does it follow traditional distro structure like Ubuntu/Debian or is it weird like atomic (ex Silverblue) or declarative (ex Nixos) distro? Is it a minimalist distro (Arch is the big modern one) it maximalist (Suse)? Those kinds of things can also be informative.






  • See the start of this post talking about device tree models vs boot time hardware discovery.

    There’s no reason an arm chip/device couldn’t support hardware discovery, but by and large they don’t for a variety of reasons that can mostly be boiled down to “they don’t want to”. There’s nothing about RISC-V that makes it intrinsically more suited to “PC style” hardware detection but the fact that it’s open hardware (instead of Apple and Qualcomm’s extremely locked down proprietary nonsense) means it’ll probably happen a lot sooner.


  • There’s also the fact that Arm doesn’t really work with arbitrary PC style hardware. Unless this got fixed (and there have been some pushes) you have to pretty much hard code the device configuration so you can’t just (for example) pull a failed graphics card and swap a new one and expect the computer to boot. This isn’t a problem for phone (or to an extent: laptop) makers because they’re happy to hard code that info. For a desktop, though, there’s a different expectation.

    RiscV does support this, i believe, so in that sense it fits the PC model better.




  • I think you already got a good answer but let me throw in another:

    Fedora’s dnf provides some good history and update reversion tools. You can use:

    dnf history list

    to get a list of all actions taken on the system since install. Use “dnf history info 5” to get info on the 5th transaction. (Get the transaction ID numbers from “dnf history list”.)

    Then to revert a change use either:

    dnf history rollback or dnf history undo

    Using undo reverses a single transaction, so if you have one where you did something like “dnf install tmux” and then ran undo on it then that would be equivalent to running “dnf remove tmux” in terms of what it does on your system.

    Rollback does what you might think: it basically goes through all the updates between the most recent and the one specified and it reverses each of them, theoretically restoring the system to the state it was in at that time.

    I say “theoretically” because this isn’t a perfect system. For example, if you have an update where you removed some software that had some customizations done to it and then went through a rollback it’ll put that software back but may be missing configurations you applied to it, so potentially it could cause some issues if those were important. This gets into a lot of complicated stuff and tbh it is a powerful but imperfect system. Something like Atomic gives you more of a guarantee that a rollback will work because the whole system state is defined by the installer, not just the packages.

    There’s one more note: Fedora removes old versions of packages from its repos so you’ll need to add their historical archives repo to do certain things. I forget how to do that off the top of my head.

    This may not be what you want exactly but it’s a powerful tool that’s good to be aware of.

    See this for more info.