)
are available in the git repository at:
git://github.com/pohly/openembedded-core image-conversion
https://github.com/pohly/openembedded-core/tree/image-conversion
Patrick Ohly (2):
image creation: allow overriding .rootfs suffix
image.bbclass: support chaining compression (aka
images. Then
it becomes possible to set
IMAGE_FSTYPES = " dsk.xz dsk.vdi.xz"
and do_image_dsk will automatically produce the intermediate images,
convert to dsk.xz resp. dsk.vdi -> dsk.vdi.xz and delete all
intermediate images. Symlinks are also set correctly.
Signed-off-by: Pa
r avoids the problem and should
also fix the handling of filenames with special characters (in
particular spaces).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/combo-layer | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/combo-layer b/scripts/combo-la
ed on
BBCLASSEXTEND parameters.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on
On Wed, 2016-02-24 at 16:09 +, Lock, Joshua G wrote:
> On Wed, 2016-02-24 at 16:37 +0100, Patrick Ohly wrote:
> > Hello!
> >
> > I haven't had a chance to play with the actual code yet and I don't
> > know
> > yet when I'll be able to. Let me
ious layers and recipes
> make changes to the rootfs contents outside of the package manager,
> particularly
> with IMAGE_POSTPROCESS_COMMAND, etc.
Makes sense to me.
Have you considered generating the file lists more efficiently? I can
think of some alternatives, but all have downsid
ill be
reconstructed during full world rebuilds, a git log will then only
show real updates, additions and removals.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildhistory.bbclass | 60 +--
1 file changed, 51 insertions(+),
itbake).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/base.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 8ce9dd4..1372f38 100644
--- a/meta/classes/base.bbclass
+++ b/meta/clas
When patchelf-uninative fails, reporting only the exit code
as done by subprocess.check_call() is not enough to understand
the problem. We also need to capture and report the output
of the command.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/uninative.bbcla
On Mon, 2016-02-08 at 16:14 +0100, Patrick Ohly wrote:
> initramfs-framework now RDEPENDS on ${VIRTUAL-RUNTIME_base-utils},
> which can be busybox or some alternative like toybox. Making the
> SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS exception flexible, too, ensures that
> distros using toybo
get? Using
relative paths would avoid the problem, and also make it easier to
investigate the content of the rootfs on the build host.
Is that something that would have to be fixed in the different
virtual/update-alternatives providers? I'm using opkg-utils at the
moment.
--
Best Regards, Patrick O
On Tue, 2016-02-09 at 12:03 +0100, Patrick Ohly wrote:
> Hello!
>
> I noticed that toybox's switch_root has problems handling /sbin/init
> -> /lib/systemd/systemd. Apparently it tries to check permissions with
> stat() before switching the root, and at that point resolving t
On Tue, 2016-02-09 at 10:22 +0100, Patrick Ohly wrote:
> On Mon, 2016-02-08 at 16:14 +0100, Patrick Ohly wrote:
> > initramfs-framework now RDEPENDS on ${VIRTUAL-RUNTIME_base-utils},
> > which can be busybox or some alternative like toybox. Making the
> > SIGGEN_EXCLUDE_SAFE_
On Mon, 2016-02-08 at 08:52 +, Richard Purdie wrote:
> On Mon, 2016-02-08 at 07:56 +0100, Patrick Ohly wrote:
> > buildhistory.bbclass by design is incremental: each build adds or
> > updates information. Information is never removed.
> >
> > Sometimes
ear what exactly the problem is, only that reverting
the binutils upgrade avoids it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor a
initramfs-framework now RDEPENDS on ${VIRTUAL-RUNTIME_base-utils},
which can be busybox or some alternative like toybox. Making the
SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS exception flexible, too, ensures that
distros using toybox still pass the selftests.
Signed-off-by: Patrick Ohly <patric
ly show real updates, additions
and removals.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildhistory.bbclass | 43 +++
1 file changed, 34 insertions(+), 9 deletions(-)
diff --git a/meta/classes/buildhistory.bbclass
b/meta/classes/
On Mon, 2016-02-01 at 08:57 -0800, Khem Raj wrote:
> On Mon, Feb 1, 2016 at 12:14 AM, Patrick Ohly <patrick.o...@intel.com> wrote:
> > On Mon, 2016-01-25 at 11:39 -0800, Andre McCurdy wrote:
> >> > +if grep "CONFIG_INIT=y" ${B}/.config; then
>
only causes
tests to fail when SERIAL_CONSOLES is really set differently. I'm
wondering whether there should be variable flag for machine-specific
variables: then using such variables in machine-independent recipes
could trigger a QA warning.
--
Best Regards, Patrick Ohly
The content of this messa
to be used but
are valid when inserted into a shell command; <> for example
did not work because the temporary image command was getting parsed as
shell script) and then turned back into the original variable
references, which is how the code worked before this change.
Signed-off-by: Patric
On Thu, 2016-01-21 at 14:23 +0100, Patrick Ohly wrote:
> Not replacing TMPDIR at all (from in OE-core:a8c377beadb85b0ff50)
> led to an expansion error when INITRD needs to passed to the image command:
>ERROR: ExpansionError during parsing bb: Failure expanding variable
On Mon, 2016-01-18 at 15:58 +0800, Robert Yang wrote:
>
> On 01/18/2016 03:31 PM, Patrick Ohly wrote:
> > I believe the "1.42.9+git${SRCPV}" string goes back to Ross, so I'd
> > assume that it is not too unusual. Can we perhaps use "1.42.9+git
> >
rity for
a while now, and 1.42.9+1.43-git${SRCPV} is considered older than that
because of the embedded 1.43. While I understand that external layers
should not be something that OE-core needs to be concerned about too
much, some consistency still helps.
I believe the "1.42.9+git${SRCPV}"
ystemd"
VIRTUAL-RUNTIME_initscripts = ""
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
PACKAGECONFIG_append_pn-dbus = " user-session"
I also tried without pam and without user-session, again without
problems.
https://github.com/pohly/poky/tree/dbus
--
Best Regard
mit 5b32e63f9e37492cef8de7aabfae562ab072b510
Author: Patrick Ohly <patrick.o...@intel.com>
Date: Fri Jan 8 15:34:50 2016 +0100
dbus_1.10.2.bb: fix path to systemctl
When compiling with systemd, pam and user sessions, the resulting
/usr/lib/systemd/user/dbus.socket ensures that
ndidate for moving into an
utility method, although it may be harder to determine exactly which
variables it depends on and might not even be needed.
So, bottom line, I think it makes sense to move ahead as proposed and
refine later in cooperation with distros trying to implement their own
special
, ${PN} if not set) and CAPABILITIES_
(definition of special files inside the package).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/capabilities.bbclass | 58 +++
1 file changed, 58 insertions(+)
create mode 100644 meta/c
() now always gets called with full path of the
link file in the host file system (because that is what the caller
has) and, while at it, only checks for existance of the target once.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/busybox/busybox.in
e-image: Update to master head revision (2015-12-09 08:49:13
+)
are available in the git repository at:
git://github.com/pohly/openembedded-core capabilities
https://github.com/pohly/openembedded-core/tree/capabilities
Patrick Ohly (3):
capabilities.bbclass: add file capabilities automa
of the busybox binary, so the increase
in disk space is minimal.
However, a local attacker can still run these commands as root by
symlinking to the original busybox.suid. Fixing that would require
building busybox differently, which would cost more disk space.
Signed-off-by: Patrick Ohly <patric
is not changed yet, but it seems that level 1 would
be a better default.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/lib/oe/package_manager.py | 35 ++-
1 file changed, 30 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oe/package_manager.py b/meta/
supports it also without
--enable-systemd.
But I like your patches, so perhaps including D-Bus 1.10.x (1.10.6 is
the latest stable release) can be considered for the next OE-core
release?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an
On Thu, 2015-12-03 at 08:39 +, Burton, Ross wrote:
>
> On 3 December 2015 at 07:46, Patrick Ohly <patrick.o...@intel.com>
> wrote:
> In the layer I am trying to be compatible with OE-core master,
> dizzy,
> fido and jethro. That
enembedded-core/commit/?id=a8aa06b2405dec31a306fdf47bd1fdf740fde7bd
[2]
https://github.com/01org/meta-intel-iot-security/blob/7026d6e8e1084def0ebf203799360b54b5ac2763/meta-security-framework/recipes-core/dbus/dbus-cynara_1.8.18.bb
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
On Wed, 2015-12-02 at 16:47 +, Burton, Ross wrote:
>
> On 2 December 2015 at 16:27, Patrick Ohly <patrick.o...@intel.com>
> wrote:
> I'm not sure about the "more complicated to do changes in
> external
> layers". Why is that?
>
iables" file.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildhistory-extra.bbclass | 49 +
1 file changed, 44 insertions(+), 5 deletions(-)
diff --git a/meta/classes/buildhistory-extra.bbclass
b/meta/classes/buildhistory-
ecksum, originated layer(s), .bbappend and other overrides.
- information about source/patch files used in recipes (URLs, layers
originating from, checksums).
- for images, links to source recipe names/versions that was used in image.
[Code from Paul, commit message from Patrick]
Signed-off-by: Patric
age from Patrick]
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildhistory-extra.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/buildhistory-extra.bbclass
b/meta/classes/buildhistory-extra.bbclass
index e9fea5d..2dd5c5f 100644
--- a/met
m/pohly/openembedded-core/tree/buildhistory-extra
Ismo Puustinen (1):
buildhistory-extra.bbclass: simplify usage
Patrick Ohly (2):
buildhistory.bbclass: support extending the content of the build
history
buildhistory-extra.bbclass: more complete and reliable data gathering
Paul Eggleton (1):
bui
file from
buildhistory-extra.bbclass never showed up in the final build history.
To fix this, the hard-coded list of known files in
buildhistory_emit_pkghistory() must be turned into a variable which
derived classes can extend.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
-
history such that building fails with "version going
backwards".
There are not tune-specific overrides, so a Python snippet is used to
apply the additional parameters on all machines with the same
TUNE_ARCH as intel-core2-32 (like for example edison).
Signed-off-by: Patrick Ohly
egistering
image-vm.bbclass as implementation of it, it becomes possible to
select them with:
IMAGE_FSTYPES = "hdddirect"
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-vm.bbclass| 3 ++-
meta/classes/image.bbclass | 2 +-
meta/classes/image_
This fixes booting with initramfs and root=UUID on machines with IDE
disks, like "runqemu hdddirect", and kernels which still use the
deprecated CONFIG_IDE.
v2: Rebased against current master-next.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../systemd/ru
Due to a missing $ before the variable name, all fatal errors ended up
invoking a shell, instead of only doing that when init_fatal_sh is set
as boot parameter.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 2 +-
ts ignored in the default
mode.
Promoting the "root '$bootparam_root' doesn't exist." message from
"debug" to "msg" gives sufficient context to understand the error. A
more intrusive change would be to change also the control flow.
Signed-off-by: Patrick Ohly <patrick.o...@inte
nce commit 72682d72b52355c3fed947167ca3c6064340ead1:
autotools.bbclass: mkdir ${B} -> mkdir -p ${B} (2015-09-16 22:17:19 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core initramfs-rootfs-failure
https://github.com/pohly/openembedded-core/tree/initramfs-rootfs-failure
Pa
On Wed, 2015-09-16 at 14:11 +0200, Patrick Ohly wrote:
> I just noticed that udev (no longer) creates /dev/disk/by-uuid links for
> my boot partition under qemu when booting a whole-disk image
> (hdddirect). The device is then /dev/hda, with /dev/hda2 being the root
> partition.
>
This fixes booting with initramfs and root=UUID on machines with IDE
disks, like "runqemu hdddirect", and kernels which still use the
deprecated CONFIG_IDE.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../systemd/rules-whitelist-hd-devices.
bit puzzled a) that plain-old IDE block devices have never been
matched by 60-persistent-storage.rules (I checked the history) and b)
that this suddenly broke. I'm fairly sure that I had tested that (but I
cannot 100% guarantee that anymore).
Did indeed something change recently that led to /
for "kernel-devsrc" here:
> http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/68352
Also possibly related:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7959
"archiver.bbclass: fails for linux--yocto when archiving patched source"
--
Best Regards,
. Instead, it will
have to be set in image recipes on a case-by-case basis.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/boot-directdisk.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/boot-directdisk.bbclass
b/meta/classe
8402958cd2cb87b8283c8ee4e2d08e1a6717d67a:
pseudo_1.7.3.bb: New version of pseudo (2015-09-06 15:24:28 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core initramfs-framework
https://github.com/pohly/openembedded-core/tree/initramfs-framework
Patrick Ohly (4
-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/init
b/meta/recipes-core/initrdscripts/initramfs-framework/init
index e
n([' rootfstype=' + i for i in ['ext4', 'ext3',
'ext2'] if i in d.getVar('IMAGE_FSTYPES', True).split()])}"
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/finish | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
It can be useful for debugging to override the default /sbin/init.
This is something typically done via the init boot parameter which
then gets interpreted by the kernel. But when using an initramfs, it
is the initramfs which must react to the option.
Signed-off-by: Patrick Ohly <patric
cause the ordering information is not preserved by the
initramfs-framework's boot param support.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/finish | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/recipes-core/initrdscript
age) after checking the current argument for more
specific cases like bootparams and qemuparams avoids this
misinterpretation of the command line parameters.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/runqemu | 32
1 file changed, 16 i
me know if you have any objections, otherwise the merge is pending.
No objections from me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the
>
> if [ ! -d "$BUILDDIR" ]; then
> echo >&2 "Error: The builddir ($BUILDDIR) does not exist!"
What was the reasoning behind adding these operations on $BUILDDIR/conf
before the check whether BUILDDIR exists and is a directory? Looks a bit
fishy to me.
-
On Fri, 2015-09-04 at 09:17 +0200, Patrick Ohly wrote:
> On Thu, 2015-09-03 at 16:56 -0500, Alex Franco wrote:
> > Removing recursive option from chmod -st on BUILDDIR as it would
> > take very long on existing build directories
>
> Okay, so this *is* a problem o
x 3.16.0-4-amd64, coreutils 8.23-4, ext4 on a SATA
hard disk.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on
On Thu, 2015-09-03 at 14:34 -0700, Khem Raj wrote:
> > On Sep 3, 2015, at 11:42 AM, Patrick Ohly <patrick.o...@intel.com> wrote:
> >
> > install -m 0755 ${WORKDIR}/debug ${D}/init.d/00-debug
> > +
> > +# Create device nodes expected by some kernels
This makes it possible to boot images with multiple partitions (the
ones ending in .hddimg or .hdddirect) in several ways:
runqemu qemux86 core-image-minimal hddimg
runqemu tmp/deploy/images/qemux86/core-image-minimal-qemux86.hddimg
.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
b/meta/recipes-core/initrdscripts/initramf
Some of the SYSLINUX defaults are the same as in the underlying
syslinux.bbclass. Let's not duplicate them, because that makes
changing the default harder.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-vm.bbclass | 2 --
1 file changed, 2 deletions(-)
diff
Set INITRD_IMAGE to automatically add a custom initramfs to the boot
partition.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-vm.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/classes/image-vm.bbclass b/meta/classes/image-vm.bbclass
tion in this example.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/init
b/meta/recipes-core/initrds
e first
place.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/fs-uuid.bbclass | 24
meta/classes/grub-efi.bbclass | 4
meta/classes/gummiboot.bbclass | 4
meta/classes/syslinux.bbclass | 5 -
4 files changed, 36 insertion
This changes the default SYSLINUX_ROOTFS such that the rootfs is no
longer expected under a fixed device path. Instead, the UUID is used
to find it. This makes the resulting .hdddirect (and thus also the
vdi/vdmk/qcow2 images derived from that) more flexible.
Signed-off-by: Patrick Ohly
repository at:
git://github.com/pohly/openembedded-core booting-simplified
https://github.com/pohly/openembedded-core/tree/booting-simplified
Patrick Ohly (8):
runqemu: support full-disk images
initramfs-framework: create /dev/console
initramfs-live-boot: create /dev/console
initramfs
.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework_1.0.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework_1.0.bb
b/meta/recipes-core/initrdscripts/ini
the kernel
(INITRAMFS_IMAGE_BUNDLE).
But I'm fine with dropping these two patches for now and revisit the
topic at a later time. I'll remove them from V2 of the patch series.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employe
On Wed, 2015-09-02 at 13:16 -0300, Otavio Salvador wrote:
> On Wed, Sep 2, 2015 at 12:48 PM, Patrick Ohly <patrick.o...@intel.com> wrote:
> > Using the general purpose "debug" and "verbose" kernel parameters to
> > increase logging in the init script has th
at
step if non-empty.
This allows modules to implement their own rootfs handling.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../initrdscripts/initramfs-framework/finish | 33 +-
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/meta/recipes-co
This makes it possible to boot images with multiple partitions (the
ones ending in .hddimg or .hdddirect) in several ways:
runqemu qemux86 core-image-minimal hddimg
runqemu tmp/deploy/images/qemux86/core-image-minimal-qemux86.hddimg
quot;
SYSLINUX_LABELS_remove = "install"
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../initrdscripts/initramfs-framework/live | 131 +
.../initrdscripts/initramfs-framework_1.0.bb | 9 ++
2 files changed, 140 insertions(+)
crea
Set INITRD_IMAGE to automatically add a custom initramfs to the boot
partition.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-vm.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/classes/image-vm.bbclass b/meta/classes/image-vm.bbclass
This changes the default SYSLINUX_ROOTFS such that the rootfs is no
longer expected under a fixed device path. Instead, the UUID is used
to find it. This makes the resulting .hdddirect (and thus also the
vdi/vdmk/qcow2 images derived from that) more flexible.
Signed-off-by: Patrick Ohly
arameter only affects the init script:
init_verbose, init_verbose=1, init_verbose=true: enable just some info
messages
init_verbose=2: debug messages
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 16 ++--
e first
place.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/fs-uuid.bbclass | 24
meta/classes/grub-efi.bbclass | 4
meta/classes/gummiboot.bbclass | 4
meta/classes/syslinux.bbclass | 5 -
4 files changed, 36 insertion
Some of the SYSLINUX defaults are the same as in the underlying
syslinux.bbclass. Let's not duplicate them, because that makes
changing the default harder.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-vm.bbclass | 2 --
1 file changed, 2 deletions(-)
diff
repository at:
git://github.com/pohly/openembedded-core booting
https://github.com/pohly/openembedded-core/tree/booting
Patrick Ohly (10):
runqemu: support full-disk images
initrdscripts: create /dev/console
initramfs-framework: handle kernel parameters with . inside
initramfs-framework
tion in this example.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/init
b/meta/recipes-core/initrds
.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework_1.0.bb | 7 ++-
meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb | 4 +++-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/initrds
the sysroot (the
ovmf keyword usage), it should make a copy in tmp (on first run) and
then use that copy instead?
[1] http://www.linux-kvm.org/downloads/lersek/ovmf-whitepaper-c770f8c.txt
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764918#47
--
Best Regards, Patrick Ohly
The content
On Thu, 2015-08-27 at 14:50 -0500, Leonardo Sandoval wrote:
On 08/27/2015 08:19 AM, Patrick Ohly wrote:
When I use runqemu, it ends up invoking qemu with -vga vmware. With
that, I don't see any output from TianoCore and booting hangs. It boots
when disabling graphical output (serial
from me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter
hddimg), so runqemu internals are still kinda fresh in my mind. If you
don't have time, then I can rework the patch series. However, it's a
side project for me, too.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel
On Thu, 2015-08-27 at 06:32 -0700, Khem Raj wrote:
On Wed, Aug 26, 2015 at 11:43 PM, Patrick Ohly patrick.o...@intel.com wrote:
The one in bb.utils.contains()? That is there intentionally: it's for
the xattr enabled case, in which case nothing gets added to
EXTRA_OEMAKE.
is it required
://blog.hansenpartnership.com/uefi-secure-boot/
[2] http://www.redhat.com/archives/libvir-list/2014-August/msg00960.html
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue
On Wed, 2015-08-26 at 12:02 -0700, Andre McCurdy wrote:
On Wed, Aug 26, 2015 at 9:10 AM, Patrick Ohly patrick.o...@intel.com wrote:
The unconditional removal of -DWITHOUT_XATTR accidentally introduced a
compile-time dependency on acl, because sys/acl.h gets
included. This caused random
On Wed, 2015-08-26 at 12:16 -0700, Khem Raj wrote:
On Aug 26, 2015 9:11 AM, Patrick Ohly patrick.o...@intel.com
wrote:
+EXTRA_OEMAKE = 'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS}
${@bb.utils.contains('PACKAGECONFIG', 'xattr', '', '-DWITHOUT_XATTR', d)}
-I${S}/include
. This seems more suitable
than not enabling xattr support in mtd-utils when acl support in the
distro is disabled.
Signed-off-by: Patrick Ohly patrick.o...@intel.com
---
meta/recipes-devtools/mtd/mtd-utils_git.bb | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/meta/recipes
with a patch that worked for me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel
On Tue, 2015-08-25 at 08:26 -0500, Mark Hatle wrote:
On 8/25/15 6:46 AM, Patrick Ohly wrote:
On Fri, 2015-08-14 at 11:51 +0100, Burton, Ross wrote:
On 12 August 2015 at 10:33, Patrick Ohly patrick.o...@intel.com
wrote:
There's a xattr DISTRO_FEATURE that should be respected
is not in
DISTRO_FEATURES.
I'm unsure whether checking for acl is the right approach. If xattr
was added to DISTRO_FEATURES, I'd expect the xattr support in mtd-utils
to be enabled, even if that creates some additional dependencies.
--
Best Regards, Patrick Ohly
The content of this message is my personal
On Fri, 2015-08-14 at 11:51 +0100, Burton, Ross wrote:
On 12 August 2015 at 10:33, Patrick Ohly patrick.o...@intel.com
wrote:
There's a xattr DISTRO_FEATURE that should be respected
here for
target builds (and explicitly enabled for native I guess
On Mon, 2015-08-24 at 13:50 +0200, Patrick Ohly wrote:
However, that failed initially with:
[...]
Kernel Offset: 0x0 from 0xc100 (relocation range:
0xc000-0xd07d)
---[ end Kernel panic - not syncing: /dev/console is missing or not a
character device
On Thu, 2015-08-20 at 15:47 +0200, Patrick Ohly wrote:
One more comment: it would be slightly nicer if empty whitelist could be
distinguished from no whitelist, with empty meaning enable no
recipes. In other words, replace if whitelist with if whitelist is
not None.
I want to list all
On Mon, 2015-08-24 at 13:50 +0200, Patrick Ohly wrote:
Hello!
I just tried to boot a custom image under qemu with
core-image-minimal-initramfs included in the kernel. For that, I added
to my local.conf:
INITRAMFS_IMAGE = core-image-minimal-initramfs
601 - 700 of 785 matches
Mail list logo
