From: ChenQi <Qi.Chen@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] udev 182: Create a symlink of /lib/udev/udevd in /sbin
Date: Wed, 28 Nov 2012 10:26:03 +0800 [thread overview]
Message-ID: <50B5763B.1040107@windriver.com> (raw)
In-Reply-To: <CAP9ODKqLkqZ=AtU9SNVfXRFxs04LnsQEe-9iE0nsU34Yru2pnw@mail.gmail.com>
On 11/27/2012 10:15 PM, Otavio Salvador wrote:
> On Tue, Nov 27, 2012 at 10:57 AM, Shakeel, Muhammad
> <muhammad_shakeel@mentor.com> wrote:
>> From: Muhammad Shakeel<muhammad_shakeel@mentor.com>
>>
>> From udev 174 changelog:
>> "The udev daemon moved to /lib/udev/udevd. Non-systemd init systems
>> and non-dracut initramfs image generators need to change the init
>> scripts. Alternatively the udev build needs to move udevd back to
>> /sbin or create a symlink in /sbin, which is not done by default."
>>
>> Also for 64 bit architectures there exists /lib64/udev instead of
>> /lib/udev and current init script fails to start udev.
>>
>> Signed-off-by: Muhammad Shakeel<muhammad_shakeel@mentor.com>
> As far as I know, all code in master now handles it properly (the
> missing bits I sent a patch today) so why to include this symlink?
>
I'm not sure about this.
Two things:
1) Have we ever tested udev on a target where its ${base_libdir} is
'/lib64'?
Apparently, if udevd is intalled under '/lib64', its init script cannot
start udev correctly.
2) Bug#2804 is related to to udev and ${base_libdir}.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2804
(Some packages hardcode their udev rules directory to be
'/lib/udev/rules.d/'. So can udev find them if the ${base_libdir} is
'/lib64'? )
next prev parent reply other threads:[~2012-11-28 2:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:57 [PATCH] udev 182: Create a symlink of /lib/udev/udevd in /sbin Shakeel, Muhammad
2012-11-27 14:15 ` Otavio Salvador
2012-11-28 2:26 ` ChenQi [this message]
2012-11-28 10:51 ` Otavio Salvador
2012-11-28 11:09 ` Shakeel, Muhammad
2012-11-29 9:26 ` ChenQi
2012-11-29 10:49 ` Otavio Salvador
2012-11-30 6:00 ` ChenQi
2012-12-05 13:31 ` Shakeel, Muhammad
2012-12-05 14:00 ` Mark Hatle
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=50B5763B.1040107@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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