Comment # 22 on bug 1078358 from Joey Lee

(In reply to Mario Goppold from comment #19)
> (In reply to Mario Goppold from comment #17)
> > (In reply to Franck Bui from comment #15)
> > > (In reply to Joey Lee from comment #14)
> > > > 
> > > > Looks that creating a link to null can not prevent the rule to be executed.
> > > 
> > > This is supposed to be the official way for disabling a rule file.
> > > 
> > > After creating the symlink in /etc, was udevd asked to reload its rule
> > > files, this can be achieved with "udevadm control --reload" ?
> > 
> > Yes, i have done exact this command to activate the /etc/.. rule. 
> > 
> > Does it make a difference if I?
> > 
> >   * symlink to /dev/null
> >   * touch an empty file
> >   * maybe: symlink to /bin/true or /bin/false
> 
> You have to look closely, if the correct link is set, it also works and
> overrides the global rule:
> 
> doest not work:
>    virtserv2:~ # ls -l /etc/udev/rules.d/80-hotremove-acpi-container.rules
> /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
>    lrwxrwxrwx 1 root root   9 Feb  6 17:55
> /etc/udev/rules.d/80-hotremove-acpi-container.rules -> /dev/null
>    -rw-r--r-- 1 root root 527 Jan 30 16:25
> /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
> 
> work as expected:
>    virtserv2:~ # ls -l /etc/udev/rules.d/80-acpi-container-hotplug.rules
> /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
>    lrwxrwxrwx 1 root root   9 Feb  8 21:29
> /etc/udev/rules.d/80-acpi-container-hotplug.rules -> /dev/null
>    -rw-r--r-- 1 root root 527 Jan 30 16:25
> /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
> 
> because:
>    80-acpi-container-hotplug.rules!=80-hotremove-acpi-container.rules

Ah! The 80-hotremove-acpi-container.rules is the old name for the rule. Sorry
for I didn't aware that the name is changed to 80-acpi-container-hotplug.rules
in systemd package.