My favorite thing about running on an Arch system is I know what's going on all the time. If an Ubuntu system breaks I'm generally dealing with a mass of preinstalled things, it's hard to know what's relevant. Similarly for increasing boot speed, I really like knowing exactly what I need to be running at any one time. I appreciate it's not for everyone, but I imagine most coders around here who run a Linux system wou…
Getting through the initial hurdles of getting wifi working and daemonized, getting X to start when you boot (if you want to run X), etc. can take a little time because it's not something you normally have to think about with the preinstalled distros. But once you get through those things it's pretty smooth sailing. Pacman is fantastic, and AUR is unmatched. The benefit of knowing exactly what is running is worth the…
On switching to Arch Linux
21–30 of 174 posts
Re: On switching to Arch Linux
#22Re: On switching to Arch Linux
#23If you enjoy doing that, there is always Slackware or NetBSD or debian-unstable as well.
Re: On switching to Arch Linux
#24Everything written here is true re: learning about Linux, having more control, straightforward architecture, bleeding edge software, etc.
But the instability factor eventually will bite you in the ass, and per Murphy's Law, often at the worst possible time. It's happened to me twice in this time span.
My solution is to use a separate data partition for all my files and install Arch and a more stable distro (Mint in my case) in different partitions. Both OSs link to the data partition and grab dotfiles and things from a git repo.
Arch is my preferred environment, with a tiling WM and everything painstakingly set up for my preferred workflow. But when it crashes, I can still use my workstation to get stuff done, and go about troubleshooting when I have free time.
Re: On switching to Arch Linux
#25Earlier quoted context omitted.
Author here. I think we're talking about two different things. By "nothing works out of the box" I mean that you need to set it up yourself. For example, the Beginner's Guide leads you through setup of your video driver [1], ALSA [2], Xorg [3], and wifi [4]. These are all things that require manual work. Maybe there's a more appropriate term for this than "doesn't work out of the box" (?) but it's the first term that…
That's the beautiful thing about arch. While figuring out configurations, tweaks, or problems for yourself may seem daunting Arch has fantastic documentation through the web on tons of issues, ranging from software- to hardware-specific. It is one of the best documented linux distros I've had the pleasure of using.
- The arch way tends to attract users with strong|alternative ideas, IMHO they're a big part in the revival of tiling wm.
- Today I switched to nixos though.
Re: On switching to Arch Linux
#26After struggling a little with the initial setup, I got everything in place, and it has just worked since then. Breakage from upgrades has been no worse than Ubuntu, and my Python work hasn't been disturbed at all.
For those who don't mind rolling up their sleeves and just RTFM'ing it, this is a great distro.
Re: On switching to Arch Linux
#27But Arch seems really cool if you want to rebuild Linux systems for fun & knowledge!
Re: On switching to Arch Linux
#28I like Arch as a whole but I've found that for my purposes it is a time sink compared to Debian for example. Debian has lots of sensible well thought out defaults. Arch has lots of disparate defaults each provided by the package vendor (as they don't customise packages). It's not a criticism, but a difference to bear in mind.
I also reported a major security vulnerability in the default configuration of an Arch package but I had to reopen it because the maintainer said something stupid like "people who install this package should operate on trusted networks". What?
Re: On switching to Arch Linux
#29Re: On switching to Arch Linux
#30I like Arch as a whole but I've found that for my purposes it is a time sink compared to Debian for example. Debian has lots of sensible well thought out defaults. Arch has lots of disparate defaults each provided by the package vendor (as they don't customise packages). It's not a criticism, but a difference to bear in mind.
Glancing through the instructions, it looks like things might have got better than when I installed arch linux around 6 months ago. At the point I felt like installation involved a lot of carefully designed "busy work", which I couldn't imagine not wanting to do, but which had to be done exactly.
The reason I left is because of their incredibly bizarre choice to make /usr/bin/python run python3, and messing headers around so much you couldn't build gcc from source. Between these two features, it made the system basically unusable for me.