I come from a Slackware heritage. I'd probably be running Slack today but for 3 reasons listed in decreasing order of importance to me: (1) It doesn't have a package management system that understands dependencies, (2) It doesn't support PAM, (3) It uses BSD style init scripts. Arch seemed to solve all of these problems to my satisfaction while retaining a lot of the feel of Slack. I have seen it mentioned in numerous places that Arch ends the distro search. That certainly seems to be the case for me in terms of my personal use. Now I'm just trying to figure out how I can comfortably extend my use of arch to a production setting.
There have been some suggestions that a different distro such as Debian, Ubuntu, or RHES might be better suited to these particular needs. I hear what these commentators are saying. It's just that those distros all leave me working in a environment in which I'm not really comfortable. I'm really trying to come up with a way that I can keep Arch up to date on a series of production servers in terms of bug fixes and security patches while not pushing the update envelope too far so as to possibly introduce new unexpected problems.
Anyway, I have received a wealth of information to ponder. I thank all commentators for their input.
... doug
_______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
