This allows qemu to build for the target in the world build.
Not sure this would make sense to run on the target.
(From OE-Core rev: 09a55b1d4354531afe692f2618bd4fa5bf2dec74)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When a package is built, some installation scripts must be
performed on the target. In the case of a complete image,
these scripts are run by a separate step at init time, but
only during the first boot (other package install scripts
can just be run when the package is installed on the target).
This patch lets the distribution (or user) decide when these
postponed install scripts should run. The default is normally
near the end of init, but there may be times when it's beneficial
to run them earlier so the "when" can be overridden.
(From OE-Core rev: a46466893407d44dd16ab37ae70e1bee14bdde0a)
Signed-off-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the current state, udev init script is loaded as 3rd and modutils.sh as
20th, so udevadm called in udev init script loads all kernel modules in some
unpredictable order, not honoring in any way specified order of modules in
/etc/modules. This causes some troubles mainly in the first boot. So to fix
this we now move loading of the kernel modules just before we exec udev init
script. Example of the current state:
Starting udev
rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc0
rtc-m48t86 rtc-m48t86: battery ok
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc1
root@ts72xx:~# cat /etc/modules
rtc-ep93xx
ohci-hcd
ts72xx_sbcinfo
rtc-m48t86
As you can guess, this is really wrong behaviour, because I've rtc1 as the
main time source for my system.
root@ts72xx:~# cat /etc/default/hwclock
HWCLOCKACCESS=yes
HWCLOCKDEVICE=/dev/rtc1
Expected behaviour with this patch applied:
Please wait: booting...
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0
usbcore: registered new device driver usb
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
...
rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1
rtc-m48t86 rtc-m48t86: battery ok
Starting udev
(From OE-Core rev: a0629aa0dc55829565b7ab1725875eac065ab2f1)
Signed-off-by: Petr Štetiar <ynezz@true.cz>
(based on http://patches.openembedded.org/patch/1917/)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This upgrade fix the one security issue:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-1002
[YOCTO #975] fixed.
This should be included in the Bernard point-release.
(From OE-Core rev: b52e9922e8d9acaa9b94b0f19c54bdee18ae49f1)
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means it can easily be overridden by other points in the code,
such as a ?= assignment in recipes.
(From OE-Core rev: f370961b61be2e2be4e7b33c446d71c0693ca16b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Syslog is full with entries like:
/usr/sbin/crond[773]: (CRON) STAT FAILED (/etc/cron.d): No such file or directory
Checking the package yields
Package cronie (1.4.6-r0) is installed on root and has the following files:
/usr/sbin/crond
/etc/init.d/crond
/usr/bin/crontab
/etc/sysconfig/crond
Which is missing most of what do_install_append installs, this commit fixes that
(From OE-Core rev: 4ba1d06b51d77f4bb1f542ba26328f718161a92a)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Saul Wold
Gary Thomas
Petr Štetiar
Zhai Edwin
Richard Purdie
Koen Kooi