Attila wrote: >On Mittwoch, 30. November 2005 23:41 Philip Dillon-Thiselton wrote: > > > >>Hmmm but yet a file in /etc/conf.d is fine for everything else? :) >> >> > >Okay, this is a nice place too. Thanks for the hint to have a look >at /etc/conf.d because until now it wasn't necessary for me.-) > >But as a normal user i must say: At the point where i install a new distro the >loading of the necessary modules inclusive the possibility to blacklist some >of them is for me more important than the configuration of a daemon as at >example irda or nfsd. So having the configuration of hwdetect in the rc.conf >helps me more at this point than there is a file in /etc/conf.d. This is more >a story about where a normal user as mine search things but i hope you can >understand better why i like the way how it is. > > Ok, fine, BUT we had a tool knocking about for a while called hwd, which did the same as hwdetect and people clamoured on a regular basis for its inclusion in Arch's base pkgs to help people set up their install but this was repeatedly rejected on the grounds that it was pandering to newbies and not the kind of automation that should be in Arch. Now instead we have something that is built in to the distro, not merely something you can install from the CD if you want it!
I see the devs still remaining tight-lipped on my follow-up questions, I'm sure a lot of us would really like to know why the decision has been made to do this with hwdetect. Thanks again for your comments Atilla, it is nice to have a fresh perspective of what makes it good. >See you, Attila > > > >_______________________________________________ >arch mailing list >arch@archlinux.org >http://www.archlinux.org/mailman/listinfo/arch > > > > _______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
