| 1 |
Petteri R??ty <betelgeuse@g.o> wrote: |
| 2 |
> Sven K??hler kirjoitti: |
| 3 |
> > i had some orphaned files in /etc/udev/rules.d. Namely 40-fuse.rules |
| 4 |
> > and 60-fuse.rules. |
| 5 |
> > |
| 6 |
> > The files were never removed, since they are protected - aren't |
| 7 |
> > they? |
| 8 |
> |
| 9 |
> Yeah config protected files are never removed. That is the whole point |
| 10 |
> of configuration file protection. It would't be that bad to turn off |
| 11 |
> configuration projection for /etc/udev/rules.d like we do for |
| 12 |
> /etc/env.d, but that is for the udev maintainers to decide. In the |
| 13 |
> meantime you can use something like the following to find orphaned |
| 14 |
> udev rules: |
| 15 |
> |
| 16 |
> for file in /etc/udev/rules.d/*; do qfile $file || echo $file "is |
| 17 |
> orphaned"; done |
| 18 |
|
| 19 |
Or, something like the following, to find every orphaned file: |
| 20 |
|
| 21 |
# eval $(emerge --info | grep '^CONFIG_PROTECT=') |
| 22 |
|
| 23 |
# find $CONFIG_PROTECT -type f | xargs qfile -o |
| 24 |
|
| 25 |
Naturally, that list will require a lot of scrubbing before you start |
| 26 |
deleting stuff. |
| 27 |
|
| 28 |
-- |
| 29 |
Every absurdity has a champion to defend it. |
| 30 |
-- Oliver Goldsmith |
Archives