The only "minimalist" Linux install I've ever wanted was one so stripped down it would boot off of a 3.5" floppy. It's amazing what you can do with a kernel, a baked in read-only filesystem and a tiny loopback device for storing configuration files.
Less is more.
My Arch system doesn't inundate me with pop-ups to update my system with out-of-date libraries. It doesn't integrate "the social web" into my "desktop." In fact it doesn't do anything unless I specifically want it to.
Some people are happy with everything and the kitchen sink. I don't need all of that, so why have it? It takes up resources, clutters my space, requires maintenance, and often just gets in the way for no good reason. I don't need that and Arch serves me well.
All these things are also true with Ubuntu.
(Windows is probably a worse offender with its Windows Live integration, though.)
I don't see that on my Window Maker desktop.
(People either forget or have never been told that Ubuntu is still actually Linux, and can run all the same software Arch and Slackware and CentOS can run. That's the charitable explanation, anyway.)
At some point you have to make a distinction between the desktop environment, and the increasingly meaningless term "operating system"; once you stray from the defaults, there's no point distinguishing between distros at all.
You can remove some of the defaults and not all of them. For example, I still use the default Ubuntu package repos. I'm still getting value out of the default Ubuntu system without needing to run every single default.
There's a finite distance you can run this train of thought, but i'll continue: At what point does your system stop being Ubuntu, and start being identical to someone's WindowMaker distro, customised to use ubuntu repos? (Lots of desktop debian users add ubuntu repos for the occasional package.)
On a complex system I don't know what is installed and how it's installed. It's just too big to apprehend, I will never hold all this in memory. For instance I used Ubuntu for years before discovering that I do not use 'GNU bash' at all, it was a fork called 'dash'. It may be silly and won't make a big difference, but the fact remains that I didn't know for so long. If I had bash and 10 other binaries in total on my system, I would have realized earlier. A lot earlier.
Even root has /bin/bash as its log in shell.
/bin/dash is more like the original bourne shell which helps people write more portable shell scripts and it's faster(especially for startup).
Dash is also /bin/sh in Debian.
I'm pretty sure even unix V6 had > 11 binaries, http://man.cat-v.org/unix-6th/1/
maybe some systems using busbyox may have < 11 binaries.
If I'm reading this right, you must be one of the very few people on Earth to use dash when you have the option to use bash.
Anyway, I don't use bash, either, but that's because I moved to zsh before Ubuntu even existed. I think I was using Slackware then.
I think you misread that. It sounds to me that he didn't realise he was using dash because it was bundled with Ubuntu and Ubuntu being a large distro with lots of defaults, it took him a long time to find this out. Your comment just validates his point because he didn't want to use dash at all, he just didn't know he was using it until a lot later (possibly after the differences already wasted his time).
For my desktop, I still value 'just works' over minimalism. Things like Spotify just work out of the box. And any software I may want to play with in the future that has to choose which distro to target will most likely target Ubuntu and Fedora first.
Also, the Debian repo is extensive, and the Ubuntu PPA system almost always compensates for when the Debian package is too outdated.
I also like where Ubuntu is going with the UI/UX. At first I hated the idea of the sidebar, but after trying it and realizing it autohides and stays out of your way most of the time, I switched my opinion. And I'm really looking forward to HUD in 12.04. I've been wanting an integrated Gnome-Do/Synapse for a long time now.
Finally, I get my minimalism fix where it's most important - on the servers. I can set up a local dev environment using vm's that mirrors production - database server on one vm, app server on another vm, and Nginx running on the desktop and pointing to the app server vm.
It does annoy me to start up htop on the desktop, and compare the plethora of stuff I see there with what htop on the servers displays. But I just accept it for now.
Compared to that best-of-both-worlds setup, Arch seems like it would require more compromises than is worth the time and effort to deal with it. I still intend to learn it, just because I value things that will help me learn Linux (or any of my primary tools) better. But I don't see fully making the switch to Arch.
Thoughts?
What's fascinating is that AUR packages get voted up. Packages past a certain threshold get the choice to become a main repository package. Creating and maintaining community packages is a snap with their build system (though I've never done it personally, but understand the mechanism).
On top of that, re-building your kernel, should you ever need to (I did), is dead simple.
So to your main argument of more compromise, I believe it to be false. It's less compromise to me. I feel I have to compromise with an Ubuntu distro that has made all the choices for me (and for a client-services company at least, you'll come to the day where you need to know what those choices were). Now I have the power and ability to make the decisions I want to make, especially following the extensive wiki and super helpful forums (I feel like you could compare the helpful responses there with the type of intelligence that this community possesses).
To your final point, of the "just because I value things that help me learn Linux", this will absolutely help you learn Linux. And once you know it the Arch way, most of the other ways seem completely opaque. The standards of packages in Arch allow you to find all the important bits of all the software you installed. My company uses Arch for our servers as well because we know we can count on the standards and have up to date software that, for us, "just works".
Spotify doesn't work for me in Mint. In Arch worked flawlessly. Anyway, YMMV.
Now I'm willing to have time to switch back to Arch and enjoy the minimalist (and speedy) desktop experience and the easy way to use bleeding-edge software in a (almost) safe way.
But all isn't bad in Mint. I like the performance of its kernel with the 200-lines patch scheduler. For any archer: any idea of some AUR kernel with that? Or does it get in mainstream kernel already?
This is admittedly my first day of not being just a lurker here, so forgive me if I shouldn't ask this here, but what is your setup and environment like?
I've considered running VMs for each client I work on, but am unsure if it'd just be a hassle or not.
1. I have a rule - never install server software on my base machine. Servers and server frameworks (like Rails, Jetty, PostgreSQL, etc.) are only allowed on server OS's (Ubuntu Server) running in a virtual machine. That keeps a lot of cruft and extraneous processes out of my base install, while also quarantining them into easily clonable virtual machines, should I want to recreate the vm for something. I only break that rule with one thing - I run Nginx on my host OS, and just point it at different vm appservers.
2. It helps separate your work for multiple clients. So you could setup three vm's for client 1 and three for client 2 like so - client1-webserver.vdi, client1-appserver.vdi, client1-dbserver.vdi; client2-webserver.vdi, client2-appserver.vdi, client2-dbserver.vdi.
3. It lets you more accurately simulate the production environment of an n-tier application locally, so your dev environment will be closer to prod than if you ran all these server apps directly on your base machine.
Only caveat is you need the hardware to support this. Enough disk space for multiple ~10GB vm's, enough RAM to hold them in memory, and a CPU with VT-x (and VT-d if possible) and lots of cores. I particularly like Intel's Sandy Bridge chips for this, since every core is hyperthreaded, making it appear to the OS to have twice as many cores as it actually does. Each vm can be assigned one more more core.
That's about it. Try it with Virtual Box and see what you think.
I think I'm a convert. Now, if I could get OSX to boot in a VM, and dedicate the entire HDD to Arch, that would be perfect. For some reason my Macbook won't boot the 64bit Archboot iso. But I'll wrestle that demon another day, heh.
Thanks for sharing your experience.
Just about every Linux distribution offers this, because the distro-makers create none of the window managers, etc. Which other distributions have you tried?
Slackware's package management tools doesn't do dependencies. In Arch you can easily remove a package and everything that is no longer required.
pacman -Rsn package-to-remove
The install phase is a pain if you want to get a full-blown plug-and-play ready-to-go desktop experience that rivals Ubuntu, OS X, or Windows.
It's actually really easy if you just want a bare-bones system that boots into a shell and doesn't install any packages other than what it needs to do just that.
Switch to Arch if you're a minimalist.
My rig only runs Stumpwm on Xorg. I only use xterm, emacs, and the usual GNU toolchain. A couple of interpreters. I have installed GTK so I can use Firefox (and so I can hack on Firefox), but nothing else. I don't have a crap load of applications running in the background waiting to notify me of crap I don't care about or services that I never use. I know exactly what runs on my system and it does no more than that and no less.
I think Arch fills a very nice niche and I'm so happy it exists.