Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Qi.Chen@windriver.com
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] mdadm: make udev rules dir configurable
Date: Tue, 20 Nov 2012 12:07:09 +0000	[thread overview]
Message-ID: <1353413229.23758.5.camel@ted> (raw)
In-Reply-To: <442aa8576f4be75369fe4068794573f257a4d083.1353311649.git.Qi.Chen@windriver.com>

On Tue, 2012-11-20 at 17:34 +0800, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
> 
> mdadm hardcodes the udev rules dir to be '/lib/udev/rules.d'.
> However, udev configs its base library directory to be ${base_libdir}
> instead of '/lib'. Thus if the target has powerpc64 architecture,
> the mdraid.rules file will be missing on the target, as the library
> directory is 'lib64'.
> 
> This patch makes the udev rules dir of mdadm configurable, so that
> the mdraid.rules file will not be missing on any target.
> 
> [YOCTO #2804]

This is a bit of a tricky one. I suspect in this case we need to install
all the udev rules to one place and have an udev look in that place,
regardless of which multilib it was compiled for.

We already have this problem with systemd_unitdir. I think we need to do
something like set:

nonarchlib = "/lib"

and then use this value in places where we want it to be invariant (yet
still allow the layout to be configurable).

So your patch starts to help with this but there is more we need to do.

Cheers,

Richard




  reply	other threads:[~2012-11-20 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  9:34 [PATCH 0/1] mdadm: make udev rules dir configurable Qi.Chen
2012-11-20  9:34 ` [PATCH 1/1] " Qi.Chen
2012-11-20 12:07   ` Richard Purdie [this message]
2012-11-23  3:07     ` ChenQi

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=1353413229.23758.5.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.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