| 1 |
On 01/11/2013 09:14 AM, Nikos Chantziaras wrote: |
| 2 |
> On 11/01/13 16:04, walt wrote: |
| 3 |
>> This seems to me like very happy news indeed, but I'm interested in |
| 4 |
>> contrary |
| 5 |
>> opinions. There's a recent thread discussing how udev-197 breaks |
| 6 |
>> lvm2, but |
| 7 |
>> that's a trivial fix once you know about it. |
| 8 |
>> |
| 9 |
>> The problem is caused because many apps including lvm2 install their udev |
| 10 |
>> config scripts in /usr/lib/udev/rules.d/ (where they never belonged in |
| 11 |
>> the |
| 12 |
>> first place IMO) and they should instead now go in /lib/udev/rules.d/. |
| 13 |
>> All you need to do is to re-emerge all of those packages *after* |
| 14 |
>> installing |
| 15 |
>> udev-197 and the config scripts will go in the correct place. |
| 16 |
>> |
| 17 |
>> You should do this before rebooting the machine because lvm2 won't |
| 18 |
>> work until |
| 19 |
>> its udev scripts are in the correct directory. |
| 20 |
> |
| 21 |
> Running this command (all in one line): |
| 22 |
> |
| 23 |
> emerge -p1 $(for p in $(qfile -Cvq $(find /usr/lib/udev/) | sort -u); do |
| 24 |
> echo "=$p"; done) |
| 25 |
> |
| 26 |
> should re-emerge all packages that still have files there. After that, |
| 27 |
> /usr/lib/udev should no longer exist. If it still does, then there are |
| 28 |
> files in it that don't belong to any package. Check them manually and |
| 29 |
> delete them as needed or move them over. Then delete /usr/lib/udev. |
| 30 |
> |
| 31 |
> |
| 32 |
|
| 33 |
Thanks for the command line tip. I wasn't aware of the /lib/ move and |
| 34 |
would've had a handful of problems had I not read the list. |
Archives