Hello
So this is what I have tried out:
I have downloaded master from openembedded-core
(f04e6bd144deb0c8fe2742f66b18904b6619a502)
then:
bitbake core-image-minimal core-image-base syslinux
Create a file test.wks
part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
part /mnt/data1/
Hi Ricardo,
On 07.05.2018 15:22, Ricardo Ribalda Delgado wrote:
In my case this patch does the trick
Unfortunately your patch results in having the recovery image's UID and
GID settings to be set to my current user instead of root. So no, your
patch does not seem to work for me.
I didn't have
Hi Volker
I have tried your patch and does not work for me :(. My configuration
is a little bit more complex, I have two different machines.
The images are generated with:
host-kiosk.wks:
part /boot/bootloader --source qbootimg-efi --ondisk sda --active
--align 1024 --use-uuid --fsoptions defau
cc: ed
Is it a very bad idea to revert your patch?
Thanks!
On Wed, May 2, 2018 at 8:17 PM, Ricardo Ribalda Delgado
wrote:
> Hi
>
> I do not know how many people is actively using wic. We have started
> using it from last week, it is hard to replace old scripts that work
> :)
>
> Try sending it
Hi
I do not know how many people is actively using wic. We have started
using it from last week, it is hard to replace old scripts that work
:)
Try sending it as a proper patch, I can help you if you need it.
Regards
On Wed, May 2, 2018 at 6:31 PM, Volker Vogelhuber
wrote:
> Hi,
>
> I never go
Thanks Ricardo... that helps me.
Scott
On Wed, May 2, 2018 at 11:18 AM, Ricardo Ribalda Delgado <
ricardo.riba...@gmail.com> wrote:
> Hi Scott
>
> In this case I believe that it is a bug in wic, for no reason the user
> id of bitbake should be leaked into the rootfs.
>
> Regards
>
> On Wed, May
Hi Scott
In this case I believe that it is a bug in wic, for no reason the user
id of bitbake should be leaked into the rootfs.
Regards
On Wed, May 2, 2018 at 6:44 PM, Scott Rifenbark wrote:
> Hi,
>
> I have a couple Wic-related areas in the Yocto documentation. Wondering if
> this affects doc
Hi,
I have a couple Wic-related areas in the Yocto documentation. Wondering if
this affects documentation. I don't particularly have sections dedicated
to using specific canned wic files such as the "directdisk-multi-rootfs"
file. However, if there is some mentioning or changing of the docs to
Hi,
I never got any response to my message (until now). So AFAIK I solved
the problem with the following patch:
diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
index 84fe85d62b..66ab757aec 100644
--- a/scripts/lib/wic/partition.py
+++ b/scripts/lib/wic/partition.py
@@
Hi
I just got hit by this one. It is specially nasty because nfsroot
fails to boot if the uids are wrong.
What is the status on this?
On Mon, Jan 22, 2018 at 11:39 AM, Volker Vogelhuber
wrote:
> I finally found out, what's the reason why the included recovery rootfs has
> the wrong UIDs, while
I finally found out, what's the reason why the included recovery rootfs
has the wrong UIDs, while the main image has the correct one. The reason
seems to be the PSEUDO_LOCALSTATEDIR variable that is set to the state
dir of the main image in both cases.
I debugged all the calls up to the environm
I'm currently trying to create a multi RootFS WIC image as mentioned in
directdisk-multi-rootfs.wks. For that I have two image recipes. One that
is creating only an ext4 image (image-recovery), and the second that is
also creating a WIC image (image-main). I used the IMAGE_FSTYPES
variable for
12 matches
Mail list logo
