Re: [OE-core] [yocto] Subjects for YP Developer Day at ELCE
On 09/09/2016 11:51 AM, Jeff Osier-Mixon wrote: Hi all - we are in the planning stages for DevDay at ELCE right now, particularly the advanced track. This track changes every session, usually to cover the things we are working on hardest - for example, in San Diego we covered CROPS, devtool, the latest Toaster features, and much more. Whether you are able to attend DevDay or not, we would be grateful to hear your suggestions for subjects to cover in the advanced track. We are currently planning talks about CROPS, devtool and the ESDK, Toaster, wic, smack, security, and a few other things. If you have a burning desire to hear about something specific, please let us know. *** Status and state of the art for read-only root filesystems. 1) r/o root + tmpfs only for ephemeral systems 2) r/o root + select r/w points (bind-volatile?) 3) r/o root + unionfs r/w My interest would be in #1 & #2 as it is security related. r/w mount would be nosuid, nodev, etc and perhaps noexec A survey of the space should include #3 however. I know there is a section in the developer manual for the basic mechanisms of r/o root but it appears a lot is left as an excrice for the user. Are the full demo images etc? *** What is the OE/YP response to Ubuntu-core? 4) Can Yocto build transactionally updated-able bundles for kernel and core-os/root-fs? 5) Can Yocto [cross-]build snaps or flatpaks? 6) Will snapd (or whatever flatpak needs) become 1st class ecosystem components? Ex: meta-snappy has a lot of good work but is early days Currently meta-snappy disables AppArmor & seccomp snapd does only light ns & cgroup control and relies on AppArmor to do most of the containment so snapd w/o AppArmor is a demo [Arch is no better BTW] Bill -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [poky] Commit and Patch message guidelines - fifth draft
On 05/12/2011 05:11 PM, Darren Hart wrote: One more thing. There is a great deal of cross-posting to the various lists. We should discourage this. At least mentioning somewhere in here that patches should be sent to the appropriate list with maintainers and involved developers on CC and not cross posted would be a help. Ok, so I am going to go ahead and ask the dumb question. Where is the write up that say what list is for what? It seems to me there is a whole bunch of discussion happening on the poky list about making changes that that would effect everyone using openembedded-core. Do we have two lists for discussion of stuff that effect the oe-core? -- Bill ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [poky] Commit and Patch message guidelines - fifth draft
On 05/12/2011 07:49 PM, Darren Hart wrote: There is: http://www.yoctoproject.org/community/mailing-lists Which needs to be updated to better reflect the oe-core aspect I think. This might be at least one source of the cross posting as people are not sure poky vs oe-core. It seems to me there is a whole bunch of discussion happening on the poky list about making changes that that would effect everyone using openembedded-core. Do we have two lists for discussion of stuff that effect the oe-core? No. As I understand it, things that go into poky.git/meta and things that go into oe-core should be sent to the openembedded-core list. Patch series for poky.git should be isolated in such a way so that they do not include changes to meta (oe-core) and other areas at the same time. Does anyone have a different view? This seems logical to me. Thanks. I also think discussion of a potential patch should be done on the list that the patch would go to yes? Maybe we could drive that definition to ground and get the mailing list page updated. --- So above, perhaps my whole bunch was overstated. Let me retract that and say at least some. I don't mean to pick on you Darren; I really am just trying to understand and an example is often helpful. Earlier you and Richard were discussing directdisc images [1] with a suggestion that it might be ripe for removal. Should that have been on oe-core? [1] https://lists.yoctoproject.org/pipermail/poky/2011-May/006106.htm Thanks, Bill ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
