Linux Questions

1069 readers

3 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 1 year ago

MODERATORS

possiblylinux127@lemmy.zip

How do you realistically build your own OS with Arch Linux? (lemm.ee)

submitted 2 months ago by jonathanvmv8f@lemm.ee to c/linuxquestions@lemmy.zip

8 comments fedilink hide all child comments

As a Linux newbie, all I know about Arch Linux is that it is a DIY distro where you assemble the entirely of the OS by scratch. Somehow it feels like it is too easy than it needs to be, even if it is primarily meant for experienced users. I imagine it to be less like building your PC from parts bought from the market and more like building each and every component of the PC by scratch along with building the PC, which I assume to be much harder for the average consumer. It seems absurd how it is possible for a single person to incorporate the innumerable components required for functionality in a personal system that does not crash 100% of the time due to countless incompatibility errors that come with doing something like this.

I would like someone to elaborate on how it feels to 'build' a system software by yourself with Arch and how it is reasonable to actually do so in a simple language. I do have some experience in programming, mainly in webdev, so it's not like I need a baby-like explanation in how this works but it would be nice to get to know about this from someone who could understand where this confusion/curiosity is coming from.

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

[–] CaptDust@sh.itjust.works 5 points 2 months ago* (last edited 2 months ago)

To use a web dev analogy, Arch is like node, pacman is like npm. You can install node and it'll do basic functions - just like you can install arch and have basic functions with the base package. Then you need to just install additional packages to include the functionality and libraries you want to use.

Following the installation guide highlights many packages needed for a "fully functional" desktop, and there's a lot of choices to make along the way. It's not considered good for a novice because most users don't know (or care) about the difference between pipewire or alsa, i3 or gnome, network-manager or systemd-networkd - they just want a GUI, sound and a network connection.