Skip to contentSkip to conversation

udev-126 puts devices in /usr/local/dev

DISCUSSION Aras Vaichas 5 participants 7 messages Aug 28, 2008

lore
Share & tools
lore
#0 lore raw

Hi there,

I just updated from 124 to 126 and now all my /dev entries are being created in /usr/local/dev ...

I ./configure'd with the default settings and I am cross-compiling udev in a Scratchbox environment.

Is there a configuration option that I should be setting?

Aras

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

#1 lore raw
Quoted 9 lines · Aras Vaichas

Hi there,

I just updated from 124 to 126 and now all my /dev entries are being created in /usr/local/dev ...

I ./configure'd with the default settings and I am cross-compiling udev in a Scratchbox environment.

Is there a configuration option that I should be setting?

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

FYI you can override this by editing the udev configuration file (e.g. the one in /usr/local/etc/udev/udev.conf if you don't pass stuff to ./configure), e.g. just put

udev_root="/dev"

in the file and you should be all set.

David

#2 lore raw
In reply to Aras Vaichas
Quoted 3 lines · David Zeuthen

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

This really looks like an excuse for an autoconfiscation bug. I have been maintaining an udev package for over four years and I never dreamt of rebuilding it with a different value of udev_root just for testing.
It's much easier to set $UDEV_ROOT when debugging instead of forcing every package maintainer to set $prefix.

Signature · 2 lines
ciao,
Marco
#3 lore raw
In reply to Aras Vaichas
Quoted 21 lines · David Zeuthen
Quoted 10 lines · Aras Vaichas

Hi there,

I just updated from 124 to 126 and now all my /dev entries are being created in /usr/local/dev ...

I ./configure'd with the default settings and I am cross-compiling udev in a Scratchbox environment.

Is there a configuration option that I should be setting?

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

FYI you can override this by editing the udev configuration file (e.g. the one in /usr/local/etc/udev/udev.conf if you don't pass stuff to ./configure), e.g. just put

Quoted 6 lines

udev_root="/dev"

in the file and you should be all set.

David

Hah, thanks. Silly me, I should have read the man page for that setting.

I also wanted to check that this was the expected behaviour.

I personally would design it so that the default configuration would install into the default location.I think that would adhere better to the "Rule of Least Surprise".

I'm currently assembling a whole custom Linux distribution for our embedded product, and 9-times-out-of-10 I can just call ./configure for each package and everything works as expected. Anyway, just my 2 cents.

Aras

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

#4 lore raw
In reply to Aras Vaichas
Quoted 11 lines · Marco d'Itri
Quoted 3 lines · David Zeuthen

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

This really looks like an excuse for an autoconfiscation bug. I have been maintaining an udev package for over four years and I never dreamt of rebuilding it with a different value of udev_root just for testing.
It's much easier to set $UDEV_ROOT when debugging instead of forcing every package maintainer to set $prefix.

The gentoo package now calls configure with these params:
--prefix=/ --includedir=/usr/include

The only thing I explicitly patched is the path to the pkgconfig file. I think it should be in /usr/lib/pkgconfig and not in /lib/pkgconfig.

Regards
Matthias

#5 lore raw
In reply to Aras Vaichas
Quoted 13 lines · Matthias Schwarzott
Quoted 11 lines · Marco d'Itri
Quoted 3 lines · David Zeuthen

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

This really looks like an excuse for an autoconfiscation bug. I have been maintaining an udev package for over four years and I never dreamt of rebuilding it with a different value of udev_root just for testing.
It's much easier to set $UDEV_ROOT when debugging instead of forcing every package maintainer to set $prefix.

Quoted 2 lines

The gentoo package now calls configure with these params:
--prefix=/ --includedir=/usr/include

Huh? Why? Let prefix stay as usr, as usual, and set exec-prefix, as suggested in INSTALL. Just take a look at autogen.sh.

Kay

#6 lore raw
In reply to Aras Vaichas
Quoted 14 lines · Kay Sievers
Quoted 13 lines · Matthias Schwarzott
Quoted 11 lines · Marco d'Itri
Quoted 3 lines · David Zeuthen

If you don't pass any special options (such as prefix=/), the behavior of putting device nodes in /usr/local/dev is indeed correct (it's useful for e.g. debugging udev without screwing up the real /dev).

This really looks like an excuse for an autoconfiscation bug. I have been maintaining an udev package for over four years and I never dreamt of rebuilding it with a different value of udev_root just for testing.
It's much easier to set $UDEV_ROOT when debugging instead of forcing every package maintainer to set $prefix.

Quoted 6 lines
Quoted 2 lines

The gentoo package now calls configure with these params:
--prefix=/ --includedir=/usr/include

Huh? Why? Let prefix stay as usr, as usual, and set exec-prefix, as suggested in INSTALL. Just take a look at autogen.sh.

Ah, that simplifies it.
Thanks

Matthias