On 8/22/19 11:23 AM, Behnke, Jochen wrote:
Hello Randy,
thanks for your reponse and sorry for my late reaction.
In order to test, if the problem can be reproduced reliably, I
performed a clean rebuild as follows
$ source oe-init-build-env build-tca5-32
$ rm -rf tmp
$ rm -rf sstate-cache
$ bitbake core-image-minimal
$ wic create mkefidisk -e core-image-minmal
I then mounted the resulting image file
"mkefidisk-201908221701-sda.direct" using a loopback device (losetup)
Inside the Image all directories have UID/GID 1000/1000, which
corresponds to my host user.
Files however have UID/GID 0/0.
Hi Jochen,
I'm not able to reproduce the error, see below (1).
What version of oe-core/bitbake are you using?
I'm using the latest master branches:
oe-core: 64f9fd2a1e quilt: added less to RDEPENDS list
bitbake: 28b3f0d8 runqueue: Optimise build_taskdepdata slightly
So the answer to your question is "yes I can reproduce the behavior".
One sidenote
- I am using an appended core-image-minimal not the default
What is the bbappend? Is it publicly clonable? What happens if you drop
that addition?
../Randy
(1)
I followed your steps above and mounted my image as follows:
$ fdisk -l mkefidisk-201908230902-sda.direct
Disk mkefidisk-201908230902-sda.direct: 94.4 MiB, 98956288 bytes, 193274
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1E5F9B4E-ED8A-4677-82CD-7B146807C145
Device Start End Sectors Size Type
mkefidisk-201908230902-sda.direct1 2048 51433 49386 24.1M Microsoft
basic data
mkefidisk-201908230902-sda.direct2 53248 103127 49880 24.4M Linux
filesystem
mkefidisk-201908230902-sda.direct3 103128 193239 90112 44M Linux swap
# 53248*512 = 27262976
$ sudo mount -o loop,offset=27262976 ./mkefidisk-201908230902-sda.direct
/mnt/loop
$ ls -l /mnt/loop/bin/busybox.nosuid
-rwxr-xr-x 1 root root 625296 Aug 23 11:45 /mnt/loop/bin/busybox.nosuid
$ ls -l /mnt/loop/usr | head -3
total 10
drwxr-xr-x 2 root root 3072 Aug 23 11:52 bin
drwxr-xr-x 2 root root 1024 Aug 23 11:29 games
../Randy
- In my other image I am using qt5 (v5.12)
Regards
Jochen
On 8/12/19 5:11 AM, Behnke, Jochen wrote:
> Hello,
>
> I am using poky 2.6.1 (thud) and create images using the wic utility.
>
> Recently I noticed that all directories contained in the created image
> are owned by UID 1000 and not by root. The files inside the image
> however are owned by root.
>
> The UID 1000 refers to my unprivileged user on the host system.
>
> Here is the command I use to create the image
>
> “wic create mkefidisk –e core-image-minimal”
>
> The images created by bitbake directly (.tar.bz2, .hddimg) are correct
> so this seems to be a wic related problem.
>
> Does anybody have a solution for this?
Hi Jochen,
No and I've never seen this particular extreme symptom.
There is a known, generally rare bug:
Bug 12434 - pseudo: Incorrect UID/GID in packaged files
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12434
but that usually shows up when building.
You could check you build logs for the generic stings from:
glibc-locale-2.26: glibc-locale:
/glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT
is owned by uid 3004, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
Is your issue 100% reproducible?
../Randy
>
> Many thanks in advance, any hint is appreciated.
>
> Regards
>
> Jochen
>
> <gfidisc.SID=010500000000000515000000993c4a7a4675257c8b2de024250d0000>
>
>
> __________________________________
> *SCHMIDT Technology GmbH*
> Feldbergstrasse 1
> 78112 St. Georgen/Germany
> Telefon +49 (0) 77 24 / 89 90
> Fax +49 (0) 77 24 / 89 91 01
> i...@schmidttechnology.de <mailto:i...@schmidttechnology.de>
> http://www.schmidttechnology.de
>
> USt-Id Nr. DE 811725105 · Registergericht Freiburg HRB 600 755
> Geschaeftsfuehrung: Oliver Schmidt, Stephan Schmidt
>
> <gfidisc.SID=010500000000000515000000993c4a7a4675257c8b2de024250d0000>
>
>
>
--
# Randy MacLeod
# Wind River Linux
--
# Randy MacLeod
# Wind River Linux
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
