You may have noticed Gentoo developers are working on eudev (http://thread.gmane.org/gmane.linux.gentoo.devel/81901). I previously switched some of my machines to udev-19x with initramfs (thanks NeddySeagoon for the guide at https://forums.gentoo.org/viewtopic-t-920644.html), but I wasn't really happy about my fstab and the need of maintaining the scripts and initramfs. Right now, I'm testing eudev and I succesfully deployed it on 3 machines, if you have any other working machines, feel free to post here so that we can test it properly and provide a choice between udev / eudev. No flaming please, let this thread be about testing eudev and your experience with it.

Apart from this bug and me not grasping why the f* I now need docbook-stuff for this kind of programm, it works smoothly - though I'm not using any possible features except for x.org device detection/enumeration. I'm having this problem, which did also show up lately while I've still been on normal udev and thought eudev might help, but something other seems broken here.

Merged with default USE on ~amd64._________________++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.

As I've mentioned in another thread, I've been using eudev for some time now (since before it was in portage), without any problems whatsoever. I have separate /usr (and a number of other paritions) without an initramfs, and it works properly without any issues. eudev has proven to be an excellent replacement for udev so far, and it does not impose extra dependencies like kmod and such._________________"To design the perfect anti-Unix, make all file formats binary and opaque, and require heavyweight tools to read and edit them." - The Art of Unix Programming

Not really much to say about it other then repeat hcaulfield57 .
I've not been using it since before it got in the tree but when I saw it I switched - I have no special/technical need for it really but I see no difference in functionality so I shall use it as long as it is supported

Works fine, though - with this machine >udev-180 also wouldn't be a problem (yet). _________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic