Linked by Eugenia Loli on Sun 19th Mar 2006 02:24 UTC
Permalink for comment 105673
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



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.