From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib])
Date: Sat, 9 Nov 2013 13:26:33 +0800 [thread overview]
Message-ID: <527DC789.6050307@windriver.com> (raw)
In-Reply-To: <1383565168.6271.107.camel@ted>
On 11/04/2013 07:39 PM, Richard Purdie wrote:
> On Mon, 2013-11-04 at 17:56 +0800, Hongxu Jia wrote:
>> Change in V2: The fourth patch fixed the QA Issue on udev, it was missed on previous version.
>>
>> //Hongxu
>>
>> The following changes since commit f3541226b8b1187e79dec0f6f9f3c58cedf9ac9b:
>>
>> bitbake: hob: do not display the "Package list may be incomplete!" dialog (2013-11-01 17:59:31 +0000)
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib hongxu/fix-qa-issue
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-qa-issue
>>
>> Hongxu Jia (5):
>> insane.bbclass: support to skip unsafe references in binaries qa
>> check.
>> kmod: fix QA issue
>> udev: fix QA issue
>> udev: fix QA issue
>> nfs-utils: fix QA issue
> Last time these warnings came up I asked for a clear plan about what
> needed to live in / and what needed to live in /usr and how we were
> going to fix things once and for all (or forget this idea).
>
> Where is the plan? Why is it ok to just ignore these particular
> warnings?
>
> Cheers,
>
> Richard
Hi Richard,
I want to propose the following solution for this unsafe reference issue.
The solution is based on the following two principles.
1. With /usr on a seperate partition, system should boot up without any error.
2. Without /usr, system should be able to boot into single user mode without any error.
When a QA warning about unsafe references is encountered, the above two principles,
together with FHS, are taken into consideration before making a decision.
For example, libkmod is moved to /lib because /lib/udevd requires it; libgudevd
is moved to /usr/lib because it's a GObject wrapper for libudev and it's obviously
not necessary for booting into single user mode.
The final goals of the solution:
1. Performing a world build doesn't report any warning about unsafe references.
2. System can boot into runlevel 5 without any error if /usr is on another partition.
3. System can boot into single user mode without any error even if /usr is missing.
Patches of this solution have been sent to this mailing list.
Best Regards,
Chen Qi
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
prev parent reply other threads:[~2013-11-09 5:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 9:56 [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib]) Hongxu Jia
2013-11-04 9:56 ` [PATCH 1/5] insane.bbclass: support to skip unsafe references in binaries qa check Hongxu Jia
2013-11-04 9:56 ` [PATCH 2/5] kmod: fix QA issue Hongxu Jia
2013-11-04 9:56 ` [PATCH 3/5] udev: " Hongxu Jia
2013-11-04 9:56 ` [PATCH 4/5] " Hongxu Jia
2013-11-04 9:56 ` [PATCH 5/5] nfs-utils: " Hongxu Jia
2013-11-04 11:39 ` [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib]) Richard Purdie
2013-11-04 11:48 ` Otavio Salvador
2013-11-04 12:10 ` Richard Purdie
2013-11-04 12:08 ` Hongxu Jia
2013-11-09 5:26 ` ChenQi [this message]
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=527DC789.6050307@windriver.com \
--to=qi.chen@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