Hey fellas, I noticed a lot of people will install/boot headless versions of this software on raspi to conserve resources. If I go through installing what I need to install via the GUI/Terminal, will I have any issues when I’m finished turning on the boot to CLI? I assume this won’t affect the background process too much...
I appreciate it, I was more so wondering whether or not I could keep my existing build as is aside from the GUI. I’ve done it the headless/CLI via ssh route previously but thought I’d check out using the GUI during the setup stages and being able to enable/disable the GUI at will and how that would affect performance vs installing only CLI at the start of the build.
You ask too much of him (startrek.website)
Every goddamn time (sh.itjust.works)
Do grown-ass lions and other big cats enjoy standard cat-treats?
[Not cats as treats, cats are - treatz friends...
Raspi/Debian Bookworm OS help
Hey fellas, I noticed a lot of people will install/boot headless versions of this software on raspi to conserve resources. If I go through installing what I need to install via the GUI/Terminal, will I have any issues when I’m finished turning on the boot to CLI? I assume this won’t affect the background process too much...