On 1/11/2013 09:14, Nikos Chantziaras wrote:
On 11/01/13 16:04, walt wrote:
This seems to me like very happy news indeed, but I'm interested in
contrary
opinions. There's a recent thread discussing how udev-197 breaks
lvm2, but
that's a trivial fix once you know about it.
The problem is caused because many apps including lvm2 install their udev
config scripts in /usr/lib/udev/rules.d/ (where they never belonged in
the
first place IMO) and they should instead now go in /lib/udev/rules.d/.
All you need to do is to re-emerge all of those packages *after*
installing
udev-197 and the config scripts will go in the correct place.
You should do this before rebooting the machine because lvm2 won't
work until
its udev scripts are in the correct directory.
Running this command (all in one line):
emerge -p1 $(for p in $(qfile -Cvq $(find /usr/lib/udev/) | sort -u); do
echo "=$p"; done)
should re-emerge all packages that still have files there. After that,
/usr/lib/udev should no longer exist. If it still does, then there are
files in it that don't belong to any package. Check them manually and
delete them as needed or move them over. Then delete /usr/lib/udev.
Or, without a loop (easier to read and type, IMHO):
qfile -Cvq /usr/lib/udev | awk '{print "="$1}' | xargs emerge -pv
or, using gentoolkit instead of portage-utils (slower, but will not fail
if the installed version of a package no longer exists):
equery belongs -n /usr/lib/udev | xargs emerge -pv
--
♫Dustin
