Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

Soplos Linux

  1. Home
  2. English forums
  3. Tyson
  4. Sd-Boot

Sd-Boot

Scheduled Pinned Locked Moved Tyson
2 Posts 2 Posters 24 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    JoeDirt
    wrote last edited by
    #1

    More of a curiosity question. I know it has been said Soplos follows Debian bug for bug, so... Traditionally using Debian, or any other distro that allows it, I've installed it with or after the fact with sdboot. I just like the simplicity of it. How bad would it mess everything up you have directed towards Grub anytime there is an update if I were to swap bootloaders/managers? Thanks

    1 Reply Last reply
    0
    • subdesS Offline
      subdesS Offline
      subdes
      wrote last edited by
      #2

      Hi JoeDirt,

      You wouldn't break much. The only thing that stops working outright is grub-btrfs (Timeshift snapshots as boot entries — tied to GRUB by definition), and Soplos GRUB Editor, which obviously becomes pointless.

      Dracut isn't affected. It only generates the initramfs, independent of the bootloader — if anything the integration is more natural with systemd-boot via kernel-install.

      One thing worth knowing since you asked about every update: our soplos-release package (the version-identity package, updated frequently) runs update-grub in its postinst, guarded by command -v update-grub. If you fully purge the GRUB packages when switching, that check just fails cleanly and the step is skipped — no error, no broken update. If you instead keep the GRUB packages installed alongside systemd-boot, that hook will keep quietly running update-grub on every soplos-release update, rewriting a grub.cfg nothing reads — harmless, just wasted work.

      Also keep in mind our tools (Soplos Welcome, Kernel Installer) write kernel parameters to /etc/default/grub — e.g. nvidia-drm.modeset=1 when installing NVIDIA drivers. With systemd-boot that file goes unread, so you'd need to add those parameters manually to your boot entry.

      Other than that, updates won't give you trouble either way.

      🐧 Sergi Perich — Creator of Soplos Linux


      soplos.org · YouTube

      1 Reply Last reply
      1

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups