1 |
Joseph wrote: |
2 |
> On 02/15/13 07:58, Florian Philipp wrote: |
3 |
>> Am 15.02.2013 03:38, schrieb Canek Peláez Valdés: |
4 |
>>> On Thu, Feb 14, 2013 at 7:06 PM, Joseph <syscon780@×××××.com> wrote: |
5 |
>>>> Is it safe to unmerge "sys-fs/udev-171-r9" it is blocking udev-197 |
6 |
>>> |
7 |
>>> As long as you don't stop udev, nor try to reboot before merging the |
8 |
>>> new version, yes. |
9 |
>>> |
10 |
>>> Regards. |
11 |
>>> |
12 |
>> |
13 |
>> The more important question is: Why does it block? udev is not slotted. |
14 |
>> An update shouldn't block itself. Something's not right here. |
15 |
>> |
16 |
>> Regards, |
17 |
>> Florian Philipp |
18 |
> |
19 |
> That is a good question. I had three blocks: |
20 |
> [blocks B ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is |
21 |
> blocking sys-fs/udev-197-r4) |
22 |
> [blocks B ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking |
23 |
> sys-fs/udev-init-scripts-22) |
24 |
> [blocks B ] <sys-kernel/genkernel-3.4.25 |
25 |
> ("<sys-kernel/genkernel-3.4.25" is blocking sys-fs/udev-197-r4) |
26 |
> |
27 |
> I upgraded genkernel and lvm2 and the udev bloc resolved itself. |
28 |
|
29 |
I ran into something like this too but no genkernel here. I switched to |
30 |
eudev so not sure how to get around it since I had to unmerge udev to |
31 |
install eudev anyway. I would suggest going to the boot runlevel at |
32 |
least tho. Then unmerge things until it is happy. That was what I had |
33 |
to do. |
34 |
|
35 |
Don't forget udev is a service so after the update, either reboot or |
36 |
restart the service. I would restart the sservice because the device |
37 |
nodes should already be there but will be gone if you reboot. |
38 |
|
39 |
Dale |
40 |
|
41 |
:-) :-) |
42 |
|
43 |
-- |
44 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |