Linux

48328 readers

613 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Raspi/Debian Bookworm OS help (lemmy.world)

submitted 11 months ago by whostosay@lemmy.world to c/linux@lemmy.ml

3 comments fedilink hide all child comments

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 (unless of course something I install needs a GUI.)

Along with that, will I still be conserving the same amount of resources as if I ran headless to begin with. Running x64 Bookworm on raspi 4 (8gb) if that matters, and have a general self-hosting setup.

Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] whostosay@lemmy.world 1 points 11 months ago

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.