udev-146-r2

[Oleg]

Hi list!
I have some problems with new udev-146-r2. First udev cannot start servcice:
udev-postmount|* udev: storing persistent rules...
udev-postmount|/etc/init.d/udev-postmount: line 19: /lib/udev/move_tmp_persistent_rules.sh: No such file or folder [!!]
udev-postmount|* ERROR: udev-postmount failed to start.
There is no /lib/udev folder on my test box.
Also I have 3 udev-daemons running at same time:
956 root 1 -4 12424 800 436 S 0.0 0.0 0:00.01 /sbin/udevd --daemon
1232 root 1 -2 12420 756 396 S 0.0 0.0 0:00.00 /sbin/udevd --daemon
1234 root 1 -2 12420 756 396 S 0.0 0.0 0:00.00 /sbin/udevd --daemon

Regards, Oleg.

[Daniel Robbins]

The 3 daemons may be from re-emerging udev 3 times --

I do have a /lib/udev/move_tmp_persistent_rules.sh - also listed in the portage CONTENTS file for this package, so it is getting installed.

Let me re-merge with clean tree and make sure it is not now skipping this file with an uncaught error during the emerge.

-Daniel

[Daniel Robbins]

On Nov 24, 2009, at 10:30 AM, Oleg wrote:

The short answer is that this is a really strange problem, since udev-146-r2 tries to install move_tmp_persistent_rules.sh, it exists in the tree (/usr/portage/sys-fs/udev/files/146-r2/) and the ebuild will *die* if it can't install it properly. Please confirm that this file is in your tree.

-Daniel

[Daniel Robbins]

On Nov 24, 2009, at 10:30 AM, Oleg wrote:

Another question - what kind of box is this? amd64? Did you turn multilib off by any chance?

-Daniel

[Oleg]

Yes, this file exist:
oleg@oleg ~ $ ls /usr/portage/sys-fs/udev/files/146-r2
blacklist net.sh shell-compat-addon.sh udev.confd udev-mount.initd udev-save.initd
move_tmp_persistent_rules.sh pnp-aliases shell-compat.sh udevd.initd udev-postmount.initd write_root_link_rule
oleg@oleg ~ $
Oleg.

[Oleg]

Yes, this is ~amd64 box with no-multilib profile enabled, probably this is mistake but so far only two problems appeared- baselayout, which is fixed
somehow and new udev.

[Oleg]

I fixed that in artificial way, created a /lib/udev and copied all needed scripts there and it works-probably not the best solution. I forgot to tell
that udev-135-r9 worked fine

[Daniel Robbins]

On Nov 24, 2009, at 11:03 AM, Oleg wrote:
>
> Yes, this is ~amd64 box with no-multilib profile enabled, probably this is mistake but so far only two problems appeared- baselayout, which is fixed
> somehow and new udev.

OK. I am not currently supporting a non-multilib Funtoo system. I am only building and testing multilib 64-bit systems.

I may add no-multilib 64-bit systems to the mix, but until then, I can't give you any assurance that things will work 100% -- like this udev issue.

Thanks for reporting the issue, though -- at least I know what things need fixing :)

-Daniel

[mikehunt]

Silly question: Did you forget to run etc-update (or whatever config
updater you use) after emerging udev ?

-MH