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