Hah that’s what I always had on Debian on my laptop back in the version 9 days (buster?). Nothing’s stopping you from doing it now with runlevels. I think with systems it’s just systemctl set-default multiuser.target
You can then always get the full boot with systemctl isolate graphical.target
Might not be the exact command but it’s something like that for sure.
The default systemd target to boot into can be overriden from the kernel command line.
If the GUI ever gets broken, having a such fallback boot entry just for the (VT) console mode is invaluable. (The boot-entry can reuse the same kernel and initrd images from the regular boot.)
Hah that’s what I always had on Debian on my laptop back in the version 9 days (buster?). Nothing’s stopping you from doing it now with runlevels. I think with systems it’s just
systemctl set-default multiuser.targetYou can then always get the full boot with
systemctl isolate graphical.targetMight not be the exact command but it’s something like that for sure.
The default systemd target to boot into can be overriden from the kernel command line.
If the GUI ever gets broken, having a such fallback boot entry just for the (VT) console mode is invaluable. (The boot-entry can reuse the same kernel and initrd images from the regular boot.)
Did not know that! Thanks for the tip!