[yocto] [meta-selinux][PATCH] e2fsprogs: remove bbappend

2021-02-06 Thread Yi Zhao
Remove bbappend since the misc_create_inode.c-label_rootfs.patch has
been merged upstream[1].

[1] 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=7616fd6a599e44c5700c2c3a2e08979c6c5c747e

Signed-off-by: Yi Zhao 
---
 .../e2fsprogs/e2fsprogs_%.bbappend|  1 -
 .../e2fsprogs/e2fsprogs_selinux.inc   |  3 --
 ...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 -
 .../misc_create_inode.c-label_rootfs.patch| 45 ---
 4 files changed, 69 deletions(-)
 delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
 delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
 delete mode 100644 
recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
 delete mode 100644 
recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch

diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend 
b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 
'${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc 
b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git 
a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
 
b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..000
--- 
a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca 
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===
 e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX1024
- 
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY   6
-+
- struct ext2_ext_attr_header {
-   __u32   h_magic;/* magic number for identification */
-   __u32   h_refcount; /* reference count */
diff --git 
a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch 
b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca 
-To: ty...@mit.edu
-Cc: liezhi.y...@windriver.com
-Date: Sat, 20 Feb 2016 18:58:58 +
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when 
populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca 
-Signed-off-by: Jeremy Puhlman 
-

- misc/create_inode.c | 8 
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
 a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t 
parent_ino,
-   return retval;
-   }
- 
-+  retval = set_inode_xattr(fs, root, source_dir);
-+  if (retval) {
-+  com_err(__func__, retval,
-+  _("while setting xattrs for \"%s\""), source_dir);
-+  goto out;
-+  }
-+
-   file_info.path_len = 0;
-   file_info.path_max_len = 255;
-   file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t 
parent_ino,
-  _info, fs_callbacks);
- 
-   free(file_info.path);
-+out:
-   free(hdlinks.hdl);
-   return retval;
- }
--- 
-2.11.1
-
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52254): https://lists.yoctoproject.org/g/yocto/message/52254
Mute This Topic: https://lists.yoctoproject.org/mt/80446405/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] devtool question/issue

2021-02-06 Thread David Gartner
After some experimentation it appears that devtool does not like running from a 
filesystem volume that does not contain my home directory.

My current setup on a virtualized host has the following volumes:

Filesystem Size Used Avail Use% Mounted on

udev 32G 0 32G 0% /dev

tmpfs 6.3G 5.7M 6.3G 1% /run

/dev/sda 25G 11G 13G 46% /

tmpfs 32G 0 32G 0% /dev/shm

tmpfs 5.0M 0 5.0M 0% /run/lock

tmpfs 32G 0 32G 0% /sys/fs/cgroup

/dev/sdc 148G 39G 102G 28% /mnt/YB

tmpfs 6.3G 0 6.3G 0% /run/user/1000

My home directory is located on /dev/sda - devtool works for yocto projects on 
this volume

/dev/sdc - I added this volume so that I'd have more space while using yocto, 
but devtool complains and doesn't run here. I deleted the contents of /dev/sdc 
and re-tried following the tutorial given in my initial post. I can reproduce 
(e.g. create and run qemuarm images) everything upto the step where devtool 
needs to be used.

The short term solution would be to increase the size of /dev/sdc but this 
requires moving up to a more expensive plan from my cloud provider.

Any insight as to why this occurs

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52253): https://lists.yoctoproject.org/g/yocto/message/52253
Mute This Topic: https://lists.yoctoproject.org/mt/80422014/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [meta-virtualization]: dunfell docker run issues

2021-02-06 Thread Leon Woestenberg
Marek,

This might indeed indicate a configuration mismatch. Lots of stuff
comes up on Google that you might want to check.

One is a change in systemd that affects this. Sorry I don't have a
link ready anymore.

Regards,

Leon.




--
Leon Woestenberg
l...@sidebranch.com
T: +31 40 711 42 76
M: +31 6 472 30 372

Sidebranch Embedded Systems
Eindhoven, The Netherlands
http://www.sidebranch.com



On Thu, Feb 4, 2021 at 4:04 PM Marek Belisko  wrote:
>
> Hi,
>
> I'm trying to run docker containers on orangepi and use
> meta-virtualization layer to add docker. I've installed the docker-ce
> package and everything seems to be fine.
>
> But docker service seems fails to start with:
> Feb 04 15:00:01 orange-pi-zero dockerd[495]: failed to start daemon:
> Devices cgroup isn't mounted
>
> I was trying to add various options to kernel command line like
> described here: https://github.com/docker/cli/issues/2104
>
> but it doesn't work. My command-line looks like:
> ...systemd.unified_cgroup_hierarchy=0 cgroup_enable=memory
> cgroup_memory=1 swapaccount=1 cgroup_no_v1=all
>
> Any other ideas what to check? Thanks a lot.
>
> BR,
>
> marek
>
> --
> as simple and primitive as possible
> -
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52252): https://lists.yoctoproject.org/g/yocto/message/52252
Mute This Topic: https://lists.yoctoproject.org/mt/80381272/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] devtool question/issue

2021-02-06 Thread David Gartner
Thanks for the suggestion. I gave it a try but I still get the same 
result/error :(

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52251): https://lists.yoctoproject.org/g/yocto/message/52251
Mute This Topic: https://lists.yoctoproject.org/mt/80422014/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] devtool question/issue

2021-02-06 Thread Gary Huband via lists.yoctoproject.org
I always start with

devtool modify 

This sets-up the workspace,  puts the package source code in workspace/sources, 
inits git, etc.

Gary


From: yocto@lists.yoctoproject.org  on behalf of 
David Gartner via lists.yoctoproject.org 

Sent: Friday, February 5, 2021 8:06 PM
To: yocto@lists.yoctoproject.org 
Subject: [yocto] devtool question/issue

Hi,

I've been following along on this youtube video created by a Yocto developer:

https://youtu.be/nqHylLP2NmA?t=1592

I can reproduce everything presented until it comes to using devtool (as shown 
at the time index in the link given above). When attempting to run:

devtool add git://blah-blah-gitrepo

I get the error:


ERROR: workspace layer not set up

My understanding from the documentation is that the "workspace" layer gets 
created (if it doesn't exist) when running devtool with a command such as add.

Since I'm new at using Yocto, it's likely that I"m missing something 
fundamental here.

Any help/suggestions would be appreciated

Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
g...@missionsecure.com

Follow Us!
LinkedIn  |  
Blog
  |  
Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

[MSi]

This email and any files transmitted with it are confidential and proprietary 
and intended solely for the use of the individual or entity to whom they are 
addressed. Any dissemination, distribution or copying of this communication is 
strictly prohibited without our prior permission. If you received this in 
error, please contact the sender and delete the material from any computer.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52250): https://lists.yoctoproject.org/g/yocto/message/52250
Mute This Topic: https://lists.yoctoproject.org/mt/80422014/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [meta-virtualization]: dunfell docker run issues

2021-02-06 Thread Robert Berger

Hi,

On 04/02/2021 17:03, Marek Belisko wrote:

Hi,

I'm trying to run docker containers on orangepi and use
meta-virtualization layer to add docker. I've installed the docker-ce
package and everything seems to be fine.

But docker service seems fails to start with:
Feb 04 15:00:01 orange-pi-zero dockerd[495]: failed to start daemon:
Devices cgroup isn't mounted



Can you please tell us which version of yocto this is?

Also which kernel and especially which kernel config.

I use something pretty recent (master kind of) and I am able to start 
docker and podman with a custom kernel, but networking is very wrong.


e.g.
1) if I run a web service in a container and open port 8080 to the 
outside world it is not accessible.


2) it's also not possible with docker-compose/podman-compose to 
communicate between containers


... unless I put everything on the host network.

Once you reconfigure your kernel and get it up and running could you 
please also test the issues I mention here?


BTW will dunfell it seems to work, I need to retest, but I have some 
boards running with it, I believe.


If you manage to get an upstream kernel to run on your orangepi zero I 
guess I could even give you my layers to give it a try. You will need 
another device tree and boot loader, but the rest should work.


Regards,

Robert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52249): https://lists.yoctoproject.org/g/yocto/message/52249
Mute This Topic: https://lists.yoctoproject.org/mt/80381272/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-