On Tue, Aug 30, 2005 at 02:58:12PM -0500, Peter Samuelson wrote:
> I don't have a /etc/hotplug/blacklist file. I do have a
> /etc/hotplug/blacklist.d/ which other packages have installed things
> into. Since I don't have hotplug installed, I am not sure if hotplug
> is supposed to create and maintain this file, or what.
>
> If yaird cannot cope without a /etc/hotplug/blacklist file, it probably
> ought to declare a dependency on hotplug. Even better would be not to
> require this file at all, and to read /etc/hotplug/blacklist.d/*.
Thanks for reporting this issue.
The upstream 0.0.11 tarball has the attached fix to make the blacklist
optional; workaround obvious.
Note that even if you don't have hotplug, you may want to create a blacklist
file if you find that yaird includes more modules than you want.
Regards,
Erik
--- aap/usr/lib/yaird/perl/Blacklist.pm 2005-08-03 16:24:05.000000000 +0200
+++ noot/usr/lib/yaird/perl/Blacklist.pm 2005-08-25 21:33:36.000000000
+0200
@@ -36,7 +36,17 @@
}
my $blackMap = {};
my $hotplugDir = Conf::get ('hotplug');
- parseBlackList ("$hotplugDir/blacklist");
+ my $blackListName = "hotplugDir/blacklist";
+ if (-e $blackListName) {
+ # The blacklist does not have to exist:
+ # there are machines without hotplug,
+ # and blacklist support in hotplug is
+ # likely to be replaced with a keyword in
+ # the module-init-tools config file.
+ # If it does exist, but is unreadable,
+ # that's an error.
+ parseBlackList ($blackListName);
+ }
my $dir;
my $dirName = "$hotplugDir/blacklist.d";
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
