So it's intention is never to be a user friendly distro, but one which people can make their own, as you say: It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems. The distribution is intended to fill the needs of those contributing to it, rather than trying to appeal to as many users as possible. Whereas many GNU/Linux distributions attempt to be more user-friendly, Arch Linux has always been, and shall always remain user-centric. To quote the description of philosophy of Arch on the Arch wiki: Asking people to go read forum posts about libraries they know nothing about aside from it being a dependency somewhere is not a user friendly or a safe, efficient process. If you are gonna use Arch as a workstation, dot your "i"s, cross your "t"s because no one else will do it for you. The fact is, it is unstable, that's why you have to manually check everything before you hit OK. Don't use Arch if you aren't willing to do the work. If you treat it like a workstation that 99% of the world uses, then yeah, you probably will have issues. That said, this is arch, it is your responsibility, and thats why I love it. Because they give you a safe and reliable experience most of the time. And thats why most workstations are bought and paid for from those 2 companies. If Windows or Mac required you to go read forum posts every single time you update, untold man hours would be wasted on making sure what you are doing is okay. With a subvolume layout like this most snapshots are measured in MB (see my screenshot above, the unshared column is the extra space any snapshot uses.) The only time my snapshots consume significant amounts of space are if they include /home. ├─/var/lib/flatpak/repo btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= ├─/opt/steamlib btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= ├─/var/cache btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= ├─/home btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= ├─/var/log btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= ├─/run/timeshift/backup /dev/nvme0n1p6 btrfs rw,relatime,compress-force=zstd:1,ssd,space_cache,subvolid ![]() btrfs rw,noatime,compress-force=zstd:1,ssd,space_cache,subvolid= I make subvolumes for things that I don't need snapshots of (like my steam library) and I split the high-churn directories under /var into their own subvolumes so they're not included in a root snapshot. That depends on how you split your root filesystem up. Make sure you have the correct drivers installed for your hardware. Have an LTS kernel installed alongside the upstream kernel so you can drop in to that should anything weird happen on an update.Īlways read and use the official documentation. Every time updates become available, I first check which packages can be updated ( checkupdates), then go to the recent Arch news posts to see if any of the updates need manual intervention.ĭon't install random packages off Github/AUR/Internet if you're not 100% certain they do what they say they do.ĭon't just copy and paste commands you don't understand in to the terminal. ![]() The way you break Arch 99% of the time is because you didn't properly maintain your system. It has that reputation because people don't do basic maintenance on their rolling release system, break it themselves, and then complain that Arch is unstable on forums. They say that Arch crashes on system updates are pretty frequent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |