this post was submitted on 19 Aug 2024
21 points (92.0% liked)

Linux

8118 readers
22 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
MigratingtoLemmy@lemmy.world
21
How do you realistically build your own OS with Arch Linux? (lemm.ee)
submitted 3 months ago by jonathanvmv8f@lemm.ee to c/linux@lemmy.world
11 comments fedilink hide all child comments
 

cross-posted from: https://lemm.ee/post/40063668

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
[–] seaQueue@lemmy.world 3 points 3 months ago* (last edited 3 months ago)

The best way to keep an Arch daily driver stable is to use a CoW filesystem like btrfs or ZFS and use a pacman hook that takes a snapshot before package installation or updates. If you run an update or package install that breaks something in an inconvenient way 20 minutes before you have to be on a call using said system you just revert to the snapshot, reboot and you're rolled back. I've run Arch as my daily driver like this for 4-5y now and can count the number of times I've needed to roll back like this on one hand (mostly I just don't run updates when I'm under time pressure.) Arch really doesn't break in a major way all that often once you're over the first 6-9mo of the learning curve, ie: it usually stops breaking once you stop fucking around and poking things while you're learning about them.

I wouldn't recommend Arch as a daily driver to someone who isn't generally competent at linux admin and troubleshooting, it's a handful for people who aren't up on their skills yet. On the other hand it definitely will help you develop those skills, that just takes some time. A snapshot and rollback system gives you the freedom to break most things with a reliable way to roll back to a known good state afterwards.