From: Saul Wold <sgw@linux.intel.com>
To: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>,
"Chen, Qi" <Qi.Chen@windriver.com>
Subject: Re: [RFC][PATCH] udev: add udev-utils to RDEPENDS
Date: Thu, 05 Jun 2014 16:47:34 -0700 [thread overview]
Message-ID: <53910196.8080401@linux.intel.com> (raw)
In-Reply-To: <538D7214.6060805@windriver.com>
On 06/02/2014 11:58 PM, ChenQi wrote:
> On 02/03/2014 10:01 PM, David Nyström wrote:
>> On mån 3 feb 2014 14:43:53, Phil Blundell wrote:
>>> On Mon, 2014-02-03 at 13:58 +0100, David Nyström wrote:
>>>> An intended fix for below error message with core-image-lsb,
>>>> Sending this as an RFC since I dont really know what constitutes
>>>> a RRECOMMENDS vs. RDEPENDS.
>>>> Is this clearly defined somewhere ?
>>>> Below should be an RDEPENDS, no ?
>>>>
>>>> INIT: version 2.88 booting
>>>> Starting udev
>>>> udevd[59]: starting version 182
>>>> /etc/rcS.d/S04udev: line 108: udevadm: command not found
>>>> /etc/rcS.d/S04udev: line 113: udevadm: command not found
>>>> /etc/rcS.d/S04udev: line 114: udevadm: command not found
>>>
>>> That depends (ha ha) on what the udevadm call in question is actually
>>> doing. If udev is so badly broken without it as to be unusable then
>>> yes, it should be an RDEPENDS. If udev will still work without then
>>> RRECOMMENDS is appropriate and the initscript should be tweaked to deal
>>> with it.
>>>
>>> p.
>>>
>>>
>>
>>
>> SNIP
>> --
>> udevadm control --env=STARTUP=1
>> if [ "$not_first_boot" != "" ];then
>> udevadm trigger --action=add --subsystem-nomatch=tty
>> --subsystem-nomatch=mem --subsystem-nomatch=vc
>> --subsystem-nomatch=vtconsole --subsystem-nomatch=misc
>> --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus
>> --subsystem-nomatch=graphics --subsystem-nomatch=backlight
>> --subsystem-nomatch=video4linux --subsystem-nomatch=platform
>> (udevadm settle --timeout=10; udevadm control --env=STARTUP=)&
>> else
>> udevadm trigger --action=add
>> udevadm settle
>> fi
>> --
>> SNIP
>>
>> Does this classify as essential ?
>>
>> If essential, we either need to move udev-utils to RDEPENDS.
>> If not essential, fix the script to detect if udevadm is available.
>>
>> Br,
>> David
>
> Hi All,
>
> I think it's essential.
> Without 'udevadm trigger --action=add', the system start-up process may
> have some problem. I can recall that once I removed this line from the
> init scripts in my live image, the image could not boot up correctly.
>
> I think this patch is reasonable and I'd like to acknowledge it.
>
If it's that essential, then we should incude udevadm in the udev
package directly and not have a 1 file package for udev-utils at all.
v2 patch welcome
Sau!
> Best Regards,
> Chen Qi
>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2014-06-05 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 12:58 [RFC][PATCH] udev: add udev-utils to RDEPENDS David Nyström
2014-02-03 13:03 ` Paul Eggleton
2014-02-03 13:21 ` David Nyström
2014-02-03 14:19 ` Martin Jansa
2014-02-03 13:43 ` Phil Blundell
2014-02-03 14:01 ` David Nyström
2014-06-03 6:58 ` ChenQi
2014-06-05 23:47 ` Saul Wold [this message]
2014-06-06 9:34 ` Koen Kooi
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=53910196.8080401@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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