• Digit@lemmy.today
    link
    fedilink
    English
    arrow-up
    1
    ·
    23 hours ago

    [ps. preface warning: dangerous whimsy here… rtfm… don’t dive in eager and blind and then “break” your system and come blame me.]

    Debian user here. I want to switch to arch but dont want to troubleshoot my pc after each update. How do u folks deal with that?

    I don’t [switch]. Instead I [(having already thoroughly read through all the documentation several times)]

    • go to https://bedrocklinux.org/
    • click on Installation Instructions
    • click on the first from here link
    • scroll down select the correct line for my architecture, e.g. https://github.com/bedrocklinux/bedrocklinux-userland/releases/download/0.7.31/bedrock-linux-0.7.31-x86_64.sh and paste it to a terminal as target for wget, wget https://github.com/bedrocklinux/bedrocklinux-userland/releases/download/0.7.31/bedrock-linux-0.7.31-x86_64.sh
    • make it executable chmod +x bedrock-linux-0.7.31-x86_64.sh
    • run it ./bedrock-linux-0.7.31-x86_64.sh
    • run it again remembering the need to add --hijack
    • run it again remembering the need to run it as root. (… I know, I could just remember to do sudo and --hijack first time, but I like this silly ritual).
    • and type in the “Not reversible!”, knowing how non-trivial a change to my operating system is about to happen in an instant.
    • reboot
    • enjoy seeing the new init select screen after the grub screen (albeit with only one option yet)
    • once back at a tty or once back in gui with a terminal emulator (… maybe after some more configuration tweaks, e.g. in /bedrock/etc/bedrock.conf), brl fetch arch
    • et viola, done. can do sudo apt update ; sudo apt upgrade ; sudo pacman -Syu.

    … And more likely I’d do brl fetch void ; brl fetch gentoo ; brl fetch -r ceres -n ceres devuan ; brl fetch artix. But ^ that’s for if “I want to switch to arch but dont want to troubleshoot my pc after each update.”

    Could also do frequent brl copy arch arch-fallback-(date) or some such, so then if something goes wrong with an upgrade, you could just carry on unperturbed, or even disable the stratum that had something go wrong, or even delete it, and brl rename arch-fallback-20260806 arch, and carry on with your day, sure it’ll resolve the upgrade properly next time tomorrow. ;)

    But of course, this is a bit overkill, like starting a huge complex science and production logistics project just to crack a nut.

    But it is my honest answer of how I deal with that. ;)