**** BEGIN LOGGING AT Sat Aug 10 02:59:58 2013 Aug 10 05:50:48 hi Aug 10 05:54:26 looks like util-linux package provides /usr/bin/getopt but it is a symlink to itself, does it happen to anybody here? Aug 10 05:57:23 never mind i probably spotted the issue Aug 10 09:48:35 2 newbies questions: is there a way to list available targets for bitbake? and how can i go about building an initramfs rather than a typical disk image? Aug 10 10:04:25 BCMM: bitbake -s Aug 10 10:05:17 BCMM: we provide an example initramfs that is used for live images - core-image-minimal-initramfs meta/recipes-core/images/core-image-minimal-initramfs.bb Aug 10 10:06:10 bluelightning: when you say "live images", do you mean the situation where the initramfs never pivots a "real" rootfs in? Aug 10 10:06:38 my image is small and i don't want to be able to save changes to the FS, so i was going for that sort of configuration Aug 10 10:06:40 actually that's what our live images do, they contain the real root filesystem as a compressed image Aug 10 10:07:03 but clearly you could modify the scripts to do whatever you want within the initramfs Aug 10 10:07:54 bluelightning: slightly confused here - by "as a compressed image", do you mean the initramfs itself (cpio.gz format), or that the initramfs is used to initialise a cloop (or whatever people use instead of cloop these days)? Aug 10 10:08:35 BCMM: I think the latter, but you might have to look at the scripts for details on how it's implemented Aug 10 10:08:51 i see i have targets initramfs-boot initramfs-framework and initramfs-live-boot on the list from bitbake -s Aug 10 10:09:02 is there a page somewhere documenting targets? Aug 10 10:09:39 not all of them in a list, no; however each recipe should have a description of what it is used for Aug 10 10:10:06 BCMM: you may find this useful for looking up recipe info: http://layers.openembedded.org/layerindex/recipes/ Aug 10 10:10:27 of course that covers all recipes in the OE ecosystem, not just the ones that come in a poky release Aug 10 10:11:30 bluelightning: i'm also slightly confused by seeing things like core-image-base alongside individual packages like mplayer-common - i guess the targets that generate actual finished images are just recipes like any other bit of software? Aug 10 10:11:59 indeed, images are just recipes that inherit the image or core-image class Aug 10 10:12:07 ah, i think i see Aug 10 10:12:34 bluelightning: you said "each recipe should have a description of what it is used for" - where to i find such descriptions? Aug 10 10:13:16 BCMM: you can see them in the individual recipe files (as SUMMARY or DESCRIPTION) or you can use the link above to search Aug 10 10:13:36 BCMM: actually this page may serve as an overview: http://layers.openembedded.org/layerindex/layer/openembedded-core/ Aug 10 10:14:01 (just for the core recipes) Aug 10 10:15:46 bluelightning: thanks a lot Aug 10 10:16:21 bluelightning: more generally, assuming i can find a clean way to make bitbake do it, can you see anything wrong with my idea of just doing everything in an initramfs? Aug 10 10:16:31 (given that my image is small compared to the amount of ram i have) Aug 10 10:16:41 note that what you're looking at there is master though, it may differ slightly in terms of versions or some recipe availability to one of our releases Aug 10 10:17:11 I can't see any immediate problem with that approach Aug 10 10:23:26 hmm not all of these descriptions are terribly verbose... there are two different recipes with DESCRIPTION = "A live image init script" Aug 10 10:23:28 bluelightning: thanks Aug 10 10:25:30 hmm, also really are both just /init scripts, not a way to actually make the cpio.gz archive... Aug 10 10:33:21 BCMM: that's the job of the image recipe Aug 10 10:33:54 BCMM: you'll see that core-image-minimal-initramfs sets IMAGE_FSTYPES to ${INITRAMFS_FSTYPES} which by default includes cpio.gz Aug 10 10:34:38 bluelightning: uh, i actually failed to see core-image-minimal-initramfs on the list of targets, sorry... Aug 10 10:35:12 like, even though it's the first line out of bitbake -s | grep initramfs Aug 10 21:32:17 bluelightning: yesterday I've asked about checksums in do_fetch, it seems to work correctly, you don't need to check it now Aug 10 21:32:20 $ bitbake-diffsigs tmp-eglibc/sstate-diff/1376169599/qemux86-64/x86_64-oe-linux/zlib/1.2.8-r0.do_fetch.sigdata.dc44ce8d9b3863b5b8e1a64d569128d3 tmp-eglibc/sstate-diff/1376170188/qemux86-64/x86_64-oe-linux/zlib/1.2.8-r0.do_fetch.sigdata.6e5f8247d475a0aa8448063851c950a9 Aug 10 21:32:24 basehash changed from 88cd42901220fcef84bddcbca946a0b5 to 223e2b5c4dc2d09aa22cc206f1aecade Aug 10 21:32:28 Variable SRC_URI[md5sum] value changed from '28f1205d8dd2001f26fec1e8c2cebe37' to '28f1205d8dd2001f26fec1e8c2cebe39' **** ENDING LOGGING AT Sun Aug 11 02:59:58 2013