Linked by Eugenia Loli on Sun 19th Mar 2006 02:24 UTC
Linux "The recent emphasis of the Linux community has been on desktop distros that make it easy to install and configure the system without venturing beyond the GUI. Despite the success of these beginner-friendly systems, a significant segment of the Linux population prefers a simpler approach. These back-to-basics users want clarity, stability, and speed, and they do not care about the proliferation of redundant tools and glossy configuration helpers that populate the GUI-based systems. In the past, no-frills Linux users gravitated to systems such as Slackware, Gentoo, or Debian, but another back-to-basics distro is gaining favor among the Linux faithful: Arch Linux."
Thread beginning with comment 105673
To view parent comment, click here.
To read all comments associated with this story, please click here.
jaboua
Member since:
2005-09-08

a) You'll have a choice about this: Either fiddle around with modprobe and choose the modules in /etc/rc.conf, or compile your own kernel or use some hardware detection system. Of the hardware detection systems, either set MOD_AUTOLOAD="yes" in /etc/rc.conf or install lshwd and set hwd as a daemon in /etc/rc.conf

b) IMO pacman exceeds apt-get. Examples of pacman use:
- "pacman -S package" installs package and all dependencies
- "pacman -Sy package" syncs to mirrors and installs package and all dependencies
- "pacman -Syu" syncs to mirrors and updates the system (like apt-get update && apt-get dist-upgrade iirc)
- "pacman -R package" check for dependencie conflict and remove package
- "pacman -Rcs package" removes package, and it's dependencies that are not needed by any other packages and everything depending on it

Pacman will always ask for confirmation before installing anything.

c) Search http://www.archlinux.org/packages.php for the packages you want. In http://aur.archlinux.org/packages.php you'll find the community maintained packages, some of them are in the binary "community" repo, while others are "unsupported" and you have to compile them yourself (either with "makepkg" or with a frontend like "aurbuild"). Many of the unsupported packages, plus some more, can be found in unofficial user respiratories.

Arch's philosophy want you to configure stuff yourself, and therefore does not autoconfigure stuff for you.

Reply Parent Score: 2

da_Chicken Member since:
2006-01-01

IMO pacman exceeds apt-get. Examples of pacman use:
- "pacman -S package" installs package and all dependencies
- "pacman -Sy package" syncs to mirrors and installs package and all dependencies
- "pacman -Syu" syncs to mirrors and updates the system (like apt-get update && apt-get dist-upgrade iirc)
- "pacman -R package" check for dependencie conflict and remove package
- "pacman -Rcs package" removes package, and it's dependencies that are not needed by any other packages and everything depending on it

Pacman will always ask for confirmation before installing anything.


Apt-get is just one frontend to APT (Debian's dpkg based Advanced Package Management system). I don't see how any of your examples should prove that pacman somehow "exceeds" APT.

On the other hand, APT has many features that pacman lacks, for instance, sorting dependencies to "depends", "recommends" and "suggests". This is not to say that pacman isn't a very solid and simple package manager.

Reply Parent Score: 1

vikramsharma Member since:
2005-07-06

So is pacman like pkg_add in FreeBSD. I haven't yet tried Arch Linux, pacman sounds like a promising package manager to me.

Reply Parent Score: 1

jaboua Member since:
2005-09-08

Does apt support recursive removal?

This is subjective, but I like the interface when downloading and the configuration files better...

Reply Parent Score: 1