3 ms·
I have to say that even as a person who strongly prefers Debian, one of the greatest things about Arch is its wiki. In terms of reference material to many commo
by walrus01 6y ago
I have to say that even as a person who strongly prefers Debian, one of the greatest things about Arch is its wiki. In terms of reference material to many common daemons and linux related subsystems, it's second to none.
I would recommend that everyone maintain an Arch virtual machine and know at least its basic differences (vs debian or centos, etc). By doing so, you can can make the most effective use of the wiki, to understand what material in it is specific to Arch, vs specific to the individual daemon being documented.
Somewhat randomly chosen daemon example:
https://wiki.archlinux.org/index.php/Postfix https://wiki.archlinux.org/index.php/Postfix
- capableweb 6y agoHear hear! Arch's wiki is the top resource I'd bring with me to a deserted island that only has unix computers on it and I could only bring one resource. Not sure if there is anything on there is actually specific to Arch Linux, as everything you can run/is run on Arch Linux can be run elsewhere. Even pacman/articles about packaging is not specific to Arch but specific to pacman and it's packaging. You have any examples of Arch-specific articles on there?
- walrus01 6y agoMostly I would say the arch specific material is related to how arch's package management system updates daemons, and any arch specific configuration for systemd vs how systemd is implemented on a more 'mainstream' linux like Debian stable. Generally the arch specific stuff is less than 5% of the content vs general configuration info about the daemon. And other fundamental system level stuff like how grub2 and booting is handled on Arch, or full disk encryption, etc. I have also seen some instances where the arch maintainers who package some daemons choose the installation location and configuration location for stuff in a different file tree structure. And cases where the default out of the box configuration for the daemon is different on Arch than on another Linux.
- podiki 6y agoYes, love the wiki! I'd say that's one of the reasons I (and I'm guessing others) decided to try Arch. If that's where you are getting the best info, it's a good indication of the quality of the distribution and active community. I know Arch users at times have a reputation of being not very newbie friendly, but when you have such a great resource like the wiki, it really does answer just about anything. I've used it to set up full disk encryption, resize partitions, and fix many random quirks in all sorts of programs. Happy to run Arch as my only OS on a desktop, laptop, and Pi.
- kelp 6y agoI first started using Debian with 1.3 and even admined a substantial number (hundreds) of Debian systems in the early part of my career. I still find it very comfortable. Up until a few years ago I'd never even looked at Arch, when I got into it, I went pretty deep and mostly used it for a year or so. Then recently I tried going back to Debian for a while. I didn't even bother with stable, and installed a testing snapshot, because I like new software and Arch hooked me on rolling releases. I was doing all this on a quite new Thinkpad which required some tweaks to get things working. I found myself ending up on the Arch Wiki over and over. The Debian wiki does have some good Debian specific stuff, but it's also full of really old and maybe outdated information. And then Debian didn't have some needed audio firmware packaged, and Arch did, so I made the switch back to Arch. I'd at first resisted it, because Arch has such a higher upfront cost to get installed and going. Especially with my more complex btrfs on LUKS2 (no LVM) setup. (I also had this working on Debian, it took a bit of doing). And now I'm probably going to stick with Arch (on my laptops), though I remain wistful about Debian. It was my first real Linux experience and a lot of my early career. The things that strike me about Arch vs Debian: They have comparable numbers of packages available, and if you count AUR, Arch has basically everything. But Arch has FAR fewer people working on it. By my count Arch has: 57 trusted users (they do packages in the community repo) https://www.archlinux.org/people/trusted-users/ https://www.archlinux.org/people/trusted-users/ 28 develpers (they do core and extra package repos, and other things) https://www.archlinux.org/people/developers/ https://www.archlinux.org/people/developers/ 85 people in total Debian's has: 1434 people on their contributor list for 2020 contributions: https://contributors.debian.org/ https://contributors.debian.org/ these can include bug reports and things. 978 uploading developers: https://nm.debian.org/public/stats/ https://nm.debian.org/public/stats/ So Debian has over 10x more people working on the project. Arch is generally more up to date than Debian testing and unstable (a lot more than stable, but that's obvious) but not by a ton. Generally on Arch for popular packages you'll see a new version show up within 24-48 hours and you'll be rebooting into new kernels very often. Latest kernel.org stable kernel is 5.9.6 Arch is on 5.9.4 https://tracker.debian.org/pkg/linux https://tracker.debian.org/pkg/linux Debian is on 5.9.1 https://tracker.debian.org/pkg/linux https://tracker.debian.org/pkg/linux I don't know the specifics, but Debian is probably even more conservative with the Kernel than they are with other things. That said, you can also run LTS kernels on Arch. Arch rarely changes upstream defaults, so sometimes you have to tweak and configure things. Debian generally has sensible defaults and takes care of things for you, but does modify upstream more frequently. I find apt, apt-get and dpkg to be a bit more intuitive to use. But under the hood Debian's package management system is a lot more complex than Arch's relatively simple PKGBUILD. My last point, and something I've been pondering, is the results from their different philosophies. As an outsider observing and using the results of each communities efforts, these are some things I think. Arch has a pretty extreme view on simplicity. But because of that, they have a rich, and fast moving ecosystem, with many many packages available. Some of those choices and results: rolling release - don't bother with releases, freezes, promoting from one branch to another, etc. This saves a TON of effort, and for desktop / personal use, works great. It's by far what I prefer. Even when I was using Debian, I just would run testing or unstable anyway, so would be rolling there too. I haven't come up with a non-insane way to make this work for production systems, but still pondering that. no real installer - arch just gives you a boot image that basically lets you manually partition your drive and then some tools (pacstrap, arch-chroot) to get things setup and going. This is radically more simple, this also saves a ton of effort for the developers. So much less to test and maintain. avoid modifying upstream - Also a massive time saver. Just package up what upstream provides and constantly track that. wiki instead of doing any real setup or defaults - this is also a huge time saver for the developers. Just let people document how to do things and provide the most bare building blocks. Most arch packages just put files in place, and leave all the rest up to the user. don't split packages - Arch generally doesn't split packages out like Debian does with the -dev packages, etc. This seems simpler and easier to deal with to me. At the cost of a bit more disk space for users. All that said, everything I've listed above basically offloads a ton of work to each individual user. That may be the fundamental trade-off here. Debian tries to do a lot more for it's users. But they need 10x more developers to do it.
- Fnoord 6y agoArch is supposedly a good distribution to learn Linux under the hood, but I learned a lot about Linux and the CLI when Arch did not even exist (back then you had Slackware which was all about DIY, later on Gentoo had all the rice, ...). I frankly don't understand the hype. If you want a rolling release, you can also run Debian Testing or Unstable or any BSD-CURRENT. From a technical PoV I don't see what Arch does different (in contrast to an OS like NixOS, QubesOS, Tails, or Kali). The Arch wiki is excellent, so perhaps that is what Arch brings to the table, AUR being the other (its huge). Fragmentation, when it makes sense (such as the examples I mentioned) is OK but all these thirteen in a dozen distributions won't be missed by me. Isn't it bloody annoying already when you're a Debian person and work at a RedHat shop? Why would I add another factor to that? And a rolling release OS is great on your main primary desktop. It isn't on a server, nor on a secondary computer on the side. Hence instead of Arch I recommend to play around with both Debian and RedHat based OSes to get familiar with both. As both of these are the standard in the industry (not Arch). That and a distribution tailored for a purpose, such as the ones I mentioned. The other distribution I never understood the popularity about is Manjaro. It used to be top on Distrowatch (its #2 now). Why though? I don't know anyone who uses that. It has no market penetration in the server space AFAIK. That being said, we are talking in a thread for and by Arch users. It ain't nice to break their party. I'll end my post wishing all to enjoy Arch Conf 2020!
- sergeykish 6y agoManjaro is Arch based. It is hard to find stats, Steam [1]: > Arch: 11.20% > Manjaro: 11.41% GamingOnLinux [2]: > Arch: 23.16% > Manjaro: 15.68% Servers... I've seen mostly Ubuntu, replaced by docker Alpine these days. [1] https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam?platform=linux https://store.steampowered.com/hwsurvey/Steam-Hardware-Softw... [2] https://www.gamingonlinux.com/index.php?module=statistics&view=trends https://www.gamingonlinux.com/index.php?module=statistics&vi...
- dataflow 6y ago> From a technical PoV I don't see what Arch does different I can't speak for everyone, but here are some things I see: - Arch minimizes modification of code in packages, which is nice in reducing bugs or idiosyncrasies introduced via distros. - Pacman (and its surroundings) is far more convenient, far more robust, and generally far less of a headache to deal with than apt. Hell, even figuring out what flags apt-get install accepts is an ordeal (--help? you must be joking?), let alone the nightmare it is every time you need it to do a serious job. Not sure if these qualify as "technical" to you, but they're important. (Unless they don't and you consider anything nontechnical to be unimportant.)