On 2013-03-17, Tanstaafl wrote: > On 2013-03-17 2:17 PM, Neil Bothwick <n...@digimed.co.uk> wrote: >> On Sun, 17 Mar 2013 13:46:39 -0400, Tanstaafl wrote: >> >>> Also, should I manually fix the blockers: >>> >>>> [blocks B ] sys-apps/module-init-tools >>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1) >>>> [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking >>>> sys-apps/module-init-tools-3.16-r2) >>> >>> by doing "emerge -C module-init-tools && emerge kmod" *before* >>> upgrading udev? >> >> No, because that adds kmod to world. Just unmerge module-init-tools and >> then emerge world, letting portage install what it needs > > Ah, ok... but as for the rest... I should be able to safely upgrade > udev, with a reasonable (I know there are no guarantees) expectation > of everything 'just working' (ie, my lvm managed /usr partition > shouldn't be an issue like it would have been earlier on in this > process)?
>From what I know (no LVM experience here), if you had it working with 171, it will work with a newer udev. There were no changes regarding how stuff from /usr is used between 171 and the newer udevs. -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/