**** BEGIN LOGGING AT Tue Jun 02 02:59:58 2015 Jun 02 14:32:18 hi all, is there a good way to add user account policy in oe ? Jun 02 14:35:24 kimo_: what do you mean by policy? Jun 02 14:49:09 bluelightning; I mean user access/attributes like passwd/groups Jun 02 14:50:07 bluelightning: I didn't see any example of "recipe" that show how to manage that Jun 02 14:50:10 kimo_: it depends on what you want to add the users for; if you mean system users for a service, use useradd.bbclass in the recipe which installs the service; if you mean normal users, use extrausers.bbclass Jun 02 14:50:55 http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-useradd and http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-extrausers should be helpful Jun 02 14:54:13 ok that's seems a good starting point :) thank you Jun 02 16:23:14 I've been reading the Yocto manual and trying to understand the inner workings of shared state cache. What does "task acceleration" mean, exactly (in the context of _setscene tasks)? I've been looking in sstate.bbclass and it appears that sstate_installpkg is doing quite a bit of work regardless of whether sstate data already exists for a task. Can anyone help me understand how the sstate files are used and how they speed up execution when rerunning tasks? Jun 02 16:24:25 consmith the unpack already compiled stuff Jun 02 16:24:31 and thats your speedup Jun 02 16:32:05 Okay, so as I understand the process: a checksum is generated using the inputs to a given task. Shared state archives contain stuff that has been compiled already, and each sstate archive has a checksum/signature in its name that corresponds to the set of inputs that were used to generate it. When rerunning a task, if an archive exists with a matching checksum in its name, the files in the archive will be unpacked and used in the output of the task, instead of Jun 02 16:35:34 consmith right Jun 02 16:36:32 and bitbake automagicly sets stuff to be rebuild only when it decides its necessary Jun 02 16:41:19 Thanks. Does bitbake decide what needs to be rebuilt based off the checksum? What exactly counts as an "input" to a task? Are these environment variables of some kind? I see that PACKAGE_ARCHS[vardepsexclude] and PACKAGE_ARCHS[vardeps] can be used to exclude and include dependencies, respectively. Jun 02 16:42:41 yes with that you have some control so the kernel is not rebuild Jun 02 16:42:44 for instance Jun 02 16:44:51 so the inputs to a task are all the environment variables set when that task runs, except those that have been excluded manually? Jun 02 18:43:03 If anyone wants a job in Salt Lake City doing BSP work for L3, let me know Jun 02 18:43:12 I updated the job page at OE.org also Jun 02 20:20:25 nerdboy, send some details to th eoe list would be a start Jun 02 20:46:38 Crofton|work: eoe? Jun 02 20:46:49 http://lists.openembedded.org/mailman/listinfo <= which one? Jun 02 20:48:08 so many lists Jun 02 20:48:15 send to oe-core and oe-devel Jun 02 21:02:38 What's the difference between BB_HASHBASE_WHITELIST and BB_HASHCONFIG_WHITELIST? I see that BB_HASHCONFIG_WHITELIST contains BB_HASHBASE_WHITELIST. As I understand it, BB_HASHBASE_WHITELIST is used to allow variables to change without affecting the checksum of a task, but what is BB_HASHCONFIG_WHITELIST used for? I see reference to "the cache," but I'm not sure what this means Jun 02 21:10:58 hi, all! Jun 02 21:11:19 is it possible to enable rm_work to all except a few recipes? Jun 02 21:21:07 nerdboy: just caught your question in the scrollback. we don't have any real mechanism to ask folks. I'd just send something to the oe-devel list Jun 02 21:21:43 * darknighte notices that Crofton said largely the same thing a short while ago Jun 02 21:26:23 slapin: I believe you can enable rm_work and then set "RM_WORK_EXCLUDE += "busybox glibc" if you wanted to exclude certain recipes. See http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-rm-work Jun 02 21:33:44 * nerdboy thought he was already sunscribed to both Jun 02 22:58:50 nerdboy, I'll forward to other lists Jun 02 23:01:58 did you get it? Jun 02 23:02:31 maybe you could talk scott into a documentation/project-ish talk... Jun 02 23:02:43 belize is pretty close Jun 02 23:03:58 yep Jun 02 23:04:02 sent to toe some other lists Jun 02 23:04:08 yes ETOOMANYLISTS Jun 02 23:05:33 uh-oh, Crofton is coughing errors Jun 02 23:05:43 somebody hit the reset button Jun 02 23:06:11 er, Crofton|work is... Jun 02 23:18:48 Crofton|work: Everything is fine unless you run into ETOOMANYLAYERS ;) Jun 02 23:19:01 * Crofton|work laughs Jun 02 23:19:13 or EONLYONEGIANTLAYER Jun 02 23:19:47 hey, we survived that one ;) Jun 02 23:21:50 wah... 1:21am... -ETOOMUCHWORK Jun 02 23:25:48 GO TO BED Jun 02 23:27:29 okay daddy ;) Jun 02 23:27:36 *scnr* Jun 02 23:27:46 night all... Jun 02 23:28:03 gn Jun 02 23:34:18 EGETSLESSFUNNY after a while... Jun 03 00:33:41 consmith: thanks a lot! Jun 03 00:59:53 * nerdboy early warning system ^^ **** ENDING LOGGING AT Wed Jun 03 02:59:58 2015