The cost of Arch over anything else is 100% in the installation. After that, it IS Manjaro except you are using the real thing, not a derivative. I've had to trouble shoot Arch far less than any other distro I've ever used.
https://www.archlinux.org/packages/core/any/netctl/
Why in the fuck is dialog an optional dependency?
Which sort of ties into my next problem which is that Arch simply isn't opinionated enough. Which is fine for people who want that kind of experience, but if you used Ubuntu before and you want a similar "install and go" experience, Arch really isn't the right answer. It is if your goal is to tinker with Arch, but that isn't what everybody wants.
Not all people who use netctl want wifi-menu.
> it isn't mentioned anywhere in the documentation
It sure is. https://wiki.archlinux.org/index.php/Installation_guide -> https://wiki.archlinux.org/index.php/Network_configuration -> https://wiki.archlinux.org/index.php/Netctl And there on the top of the netctl page it lists in a table dialog as a dependency of wifi-menu.
> Which sort of ties into my next problem which is that Arch simply isn't opinionated enough.
Maybe, but not all people have the same opinions...
> Maybe, but not all people have the same opinions...
Yes. And that's fucking fine. Arch Linux isn't opinionated. Which is great, but not what I (or others) might be looking for in a distro.
# cfdisk /dev/hda && mkfs.xfs /dev/hda1 && mount /dev/hda1 /mnt/gentoo/ && chroot /mnt/gentoo/ && env-update && . /etc/profile && emerge sync && cd /usr/portage && scripts/bootsrap.sh && emerge system && emerge vim && vi /etc/fstab && emerge gentoo-dev-sources && cd /usr/src/linux && make menuconfig && make install modules_install && emerge gnome mozilla-firefox openoffice && emerge grub && cp /boot/grub/grub.conf.samp le /boot/grub/grub.conf && vi /boot/grub/grub.conf && grub && init 6
That's the first one... http://bash.org/?464385
Sure, if you want to remain a Linux beginner forever, the Arch docs would be terrible.
> Don't worry about getting all the packages you want - you can easily install more of them once the basic system boots by itself. The only exception to this rule is installing any packages you need for setting up internet connectivity. These packages usually are:
> dhcpcd
> wvdial
I had fresh install recently, rebooted three times in LiveUSB to pick wifi-menu, wpa_supplicant, dialog (rechecked with pacman -Qe). That's fine, I still use Arch. And it is good Manjaro provides another set of defaults.
> DON'T PANIC!
> The Arch Linux system is assembled by the user, from the shell, using basic command line tools. This is The Arch Way.
I miss it much http://web.archive.org/web/20080720082349/http://wiki.archli...
I find arch refreshing.
by the way, I like yad.
Arch is pretty much exactly as opinionated as I want a distro to be. Hell, there are LOTS of folks who think it's too opinionated for forcing you to use systemd. The real installer is pacstrap, and it installs, I think, 300+ megs of stuff. That's all someone's opinion. And keeping it to just 300 megs is an opinion too, I guess.
EDIT: Okay, re-reading, and it sounds like installing 20 packages is a pain. But when I used Ubuntu I had to go through way more to get it how I liked it (and OS X is a nightmare 2 hours of clicking menus and buttons, and installing from web pages). I don't remember all of it now, but I had to get rid of the weird mini-vim and replace it with neovim, strip out Libre Office (nothing against them, I just have no use and it's a pain to wait for the giant updates all the time), my printer drivers were on a webpage somewhere, not the repo like Arch, etc. Ubuntu is WAY more work for me to get set up with just because removing and replacing is more work than installing.