Linux Questions

1068 readers

31 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

[email protected]

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

submitted 2 months ago by [email protected] to c/[email protected]

1 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.

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 month ago

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.

It’s really just the package manager. Every package has a description that tells the package manager what it provides and what it needs(called dependencies). So if you tell it to install X, and X needs y and z to function the package manager will automatically pull them in as well as their dependencies. It’ll also know to avoid incompatibilities the same way, the packages themselves contain the information.

90% of the real work in making a new distro is packaging, I.e. finding a way of feeding the package manager the information it needs to do its job by creating the packages. 0.1% of arch users deal with that shit.