Am Sonntag, 27. November 2005 23:56 hackte Philip Dillon-Thiselton in die Tastatur:
> Please can someone explain why hwdetect has been hardcoded into the Arch > initscripts rather than provided separately as most similar tools are. It is not hardcoded because you can say MOD_AUTOLOAD="no" in your rc.conf and run hotplug as before in the DAEMONS array. > How's that? Better? I find the way good how it is. There was an announce about testing hwdetect with your configuration and if you don't spend some time to do this than nobody could know what happens with your custom configuration at home. I suggest that you see this coming of new versions of initscripts more than as fast reactions of the devs and the reason for it is for me that the devs can't have all this possible hardware combinations around the world. I'm only a user but i think sometimes we normal user have to make some testings too because arch isn't a big company with hundred of people working in the test center. So the devs haven't a chance without the informations about our custom configurations. At last: I have some problems during hwdetect in testing, write an email to Judd and all works here at home in the final hwdetect . For me this is the only possible way to go and i see this positiv. See you, Attila _______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
