linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aras Vaichas <arasv@magtech.com.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-126 puts devices in /usr/local/dev
Date: Thu, 28 Aug 2008 00:55:34 +0000	[thread overview]
Message-ID: <48B5F786.7000003@magtech.com.au> (raw)
In-Reply-To: <48B5F216.1000708@magtech.com.au>

David Zeuthen wrote:
> On Thu, 2008-08-28 at 10:32 +1000, Aras Vaichas wrote:
>   
>> 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
>   
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 
______________________________________________________________________

  parent reply	other threads:[~2008-08-28  0:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  0:32 udev-126 puts devices in /usr/local/dev Aras Vaichas
2008-08-28  0:39 ` David Zeuthen
2008-08-28  0:51 ` Marco d'Itri
2008-08-28  0:55 ` Aras Vaichas [this message]
2008-08-28  4:50 ` Matthias Schwarzott
2008-08-28  6:32 ` Kay Sievers
2008-08-28  9:12 ` Matthias Schwarzott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48B5F786.7000003@magtech.com.au \
    --to=arasv@magtech.com.au \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).