/etc/udev/rules.d nightmare - orphaned files in /etc

Sven Köhler kirjoitti:
> Hi,
> 
> i had some orphaned files in /etc/udev/rules.d. Namely
40-fuse.rules and
>  60-fuse.rules.
> 
> The files were never removed, since they are protected
- aren't they?
> 

Yeah config protected files are never removed. That is the
whole point
of configuration file protection. It would't be that bad to
turn off
configuration projection for /etc/udev/rules.d like we do
for
/etc/env.d, but that is for the udev maintainers to decide.
In the
meantime you can use something like the following to find
orphaned udev
rules:

for file in  /etc/udev/rules.d/*; do qfile $file || echo
$file "is
orphaned"; done

Regards,
Petteri

Petteri R??ty <betelgeusegentoo.org> wrote:
> Sven K??hler kirjoitti:
> > i had some orphaned files in /etc/udev/rules.d.
Namely 40-fuse.rules
> > and 60-fuse.rules.
> > 
> > The files were never removed, since they are
protected - aren't
> > they?
> 
> Yeah config protected files are never removed. That is
the whole point
> of configuration file protection. It would't be that
bad to turn off
> configuration projection for /etc/udev/rules.d like we
do for
> /etc/env.d, but that is for the udev maintainers to
decide. In the
> meantime you can use something like the following to
find orphaned
> udev rules:
> 
> for file in  /etc/udev/rules.d/*; do qfile $file ||
echo $file "is
> orphaned"; done

Or, something like the following, to find every orphaned
file:

# eval $(emerge --info | grep '^CONFIG_PROTECT=')

# find $CONFIG_PROTECT -type f | xargs qfile -o

Naturally, that list will require a lot of scrubbing before
you start
deleting stuff.

-- 
Every absurdity has a champion to defend it.
  -- Oliver Goldsmith