From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Sat, 12 Feb 2005 00:17:50 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050212001750.GA23906@wonderland.linux.it> MIME-Version: 1 Content-Type: multipart/mixed; boundary="UugvWAfsgieZRqgk" List-Id: References: <20050211004033.GA26624@suse.de> In-Reply-To: <20050211004033.GA26624@suse.de> To: linux-hotplug@vger.kernel.org --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Feb 12, Roman Kagan wrote: > Then do use modprobe.conf, reading as >=20 > include /etc/modprobe.d Having both files would be confusing. > Well, there are many possible scenarios, what I'm trying to say is that > the current modprobe.conf syntax is sufficient for blacklisting. It's still not enough, because by using install: - blacklisted modules would never be loaded, not only when requested by hotplug - the syntax would not be backward compatible --=20 ciao, Marco --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCDUsuFGfw2OHuP7ERApCqAKCcDOtcS3WgW8pgsxBF18PYEIgqEQCdGd7r Lt9PZT0/WXjf9EObZOC7AFc= =UJ8y -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel