sys-fs/udev-168-r1 runtime directory /run/udev not writable

e3k

any idea why i get this error after updating udev and rebooting the machine?

delan · n00b Joined: 01 May 2011 Posts: 15

It's all about udev's move to put their own runtime data in /run/udev, which is a recent change from upstream.

http://lists.fedoraproject.org/pipermail/devel/2011-March/150031.html

Bascially, it's because udev was storing data its own runtime data in /dev/.udev and it was semantically incorrect and ugly. Some have suggested the use of /var/run/udev, but then again, not everyone has /var on the root partition. So the decision was made to create a top-level directory, /run.

Binary distros like Fedora got the new directory through an update to the systemd package, but I'd imagine (though I haven't tried this, and this message still appears in my boot output) that you'd have to create it yourself. Then, udev would stick its files in /run/udev, and the error message would be no more.

depontius · Advocate Joined: 05 May 2004 Posts: 2156

Shouldn't the ebuild have created /run directory during installation?
_________________
.sigs waste space and bandwidth

delan · n00b Joined: 01 May 2011 Posts: 15

Maybe the ebuild should run

SlashBeast · Moderator Joined: 23 May 2006 Posts: 2722

The /run is a crap from systemd, now udev support and use it, if can.

If there should be /run, it should be included in openrc, and as early as possible openrc should mount tmps wiht 1777 there I think. I see no other option.
_________________
github

e3k · Posted: Tue May 03, 2011 10:49 am Post subject:

as there is a fallback option i will ignore this error and wait until somebody does something

billydv · Posted: Wed May 04, 2011 2:30 am Post subject:

I created the directories with full write access and when I booted I had no keyboard or mouse control.
_________________
Billy DeVincentis

Raphux · n00b Joined: 11 Sep 2004 Posts: 41 Location: Paris

billydv · Posted: Fri May 06, 2011 1:03 am Post subject:

I think it's best to just leave this as is until the devs get it sorted out.
_________________
Billy DeVincentis

Etal · Veteran Joined: 15 Jul 2005 Posts: 1633

cwr · Veteran Joined: 17 Dec 2005 Posts: 1462

Even with /run and /run/udev 777, udev still complains. I also get a message
about a missing udev file, /lib/udev/move_tmp_persistent_rules.sh (but the
keyboard still works).

Another strikingly effective upgrade of an essential package.

Will

SlashBeast · Moderator Joined: 23 May 2006 Posts: 2722

Because when udev starts the rootfs is not writable.
_________________
github

depontius · Advocate Joined: 05 May 2004 Posts: 2156

darkphader · Veteran Joined: 09 May 2002 Posts: 1086 Location: Motown

Shouldn't need an initrd. The article linked to in the second post makes it clear that /run is supposed to be a tmpfs and that /var/run will eventually symlink to. Problem is currently that some apps store non-volatile data under /var/run which has to be addressed first.
_________________
What I need is an exact list of specific unknown problems we might encounter.

kaszynek · Posted: Mon May 09, 2011 4:40 pm Post subject:

I have the same error :/
But my keybord and mouse don't work after boot...
Any solutions?

SlashBeast · Moderator Joined: 23 May 2006 Posts: 2722

The solution is, stop creating /run dir when you have no idea what you are doing. When this dir exist, it should be writable, propably tmpfs mounted before udev starts, openrc nor udev init does not mount it at this moment.
_________________
github

thumper · Guru Joined: 06 Dec 2002 Posts: 406 Location: Venice FL

Any new information on this /run directory with respect to Gentoo?

I've been noticing this in the output of df lately.

e3k · Posted: Mon Oct 10, 2011 8:37 pm Post subject:

seenxu · n00b Joined: 19 Oct 2009 Posts: 16

I am having the same problem, any solution yet?

Gusar · Posted: Mon Feb 13, 2012 7:36 pm Post subject:

Which problem exactly?

seenxu · n00b Joined: 19 Oct 2009 Posts: 16

Gusar · Posted: Mon Feb 13, 2012 9:48 pm Post subject:

That's not a problem. While it says "error" at the beginning, it's actually just an informational message, telling you that udev will be using a fallback instead of what it wants to use (and does use on distros that have implemented /run).