**** BEGIN LOGGING AT Tue Nov 08 02:59:57 2011
Nov 08 07:17:59 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * rcf67b16021 10testlab/beaglebone/eglibc/Cloud9-IDE/ (3 files): beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision c87192738b14347a393a6c2fec93390725711af1
Nov 08 09:42:00 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * rc77566c0e0 10testlab/beaglebone/eglibc/Cloud9-IDE/ (4 files): beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision c87192738b14347a393a6c2fec93390725711af1
Nov 08 09:43:32 <CIA-55> angstrom: 03Koen Kooi <koen@dominion.thruhere.net> 07master * rfcc61ee9da 10meta-angstrom/conf/distro/include/angstrom-2010-preferred-versions.inc: 
Nov 08 09:43:32 <CIA-55> angstrom: angstrom: prefer udev 175
Nov 08 09:43:32 <CIA-55> angstrom: Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Nov 08 10:16:17 <KotH> ok boys.. i'm officially lost ^^'
Nov 08 10:16:42 <KotH> is there any documentation that explains me how to build angström for an arbitrary device?
Nov 08 10:17:03 <KotH> or one that at least explains me how to build angström at all?
Nov 08 10:17:10 * KotH couldnt find any after a day of googling
Nov 08 10:33:04 <bluelightning> KotH: http://www.angstrom-distribution.org/building-angstrom  ?
Nov 08 10:43:14 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * r0a71e1dcba 10testlab/beagleboard/eglibc/systemd-image/ (4 files): beagleboard: systemd-image configured for angstrom v2011.11-core using branch angstrom-staging and revision c87192738b14347a393a6c2fec93390725711af1
Nov 08 10:45:12 <KotH> bluelightning: juup, read that 
Nov 08 10:46:04 <KotH> bluelightning: but it doesnt explain how i know what to set MACHINE to (and there is no file that would contain a list in that git repo) and neither does it explain what i would have to do if my device is not supported
Nov 08 10:47:54 <bluelightning> ok, in the first instance, MACHINE points to a file in conf/machine directory within the metadata
Nov 08 10:48:34 <bluelightning> in the second instance if your machine is not supported the best thing is to look at those files and create a new one based upon them for your machine
Nov 08 10:49:30 <KotH> ok... i dont have a conf/machine directory 
Nov 08 10:49:58 <KotH> conf contains only two files, bblayers.conf and  local.conf
Nov 08 10:52:48 <bluelightning> within the metadata, not your build dir
Nov 08 10:53:47 <bluelightning> actually the way those instructions are laid out you don't get a look at the metadata before needing the machine, that's a bit poor
Nov 08 10:54:00 <KotH> how do i get the metadata?
Nov 08 10:56:46 <bluelightning> KotH: what happens if you just do "./oebb.sh update" ?
Nov 08 10:58:41 <KotH> it asks me for the root pw?!?!
Nov 08 11:00:26 <KotH> i think, there sould be a note somewhere that oebb requires bash as /bin/bash
Nov 08 11:00:56 * broonie raised this issue the other day.
Nov 08 11:01:10 <broonie> Reconfiguring the user's system without asking is exceptionally rude.
Nov 08 11:02:05 <bluelightning> OE requires this, yes
Nov 08 11:02:23 <bluelightning> it's on the Yocto Project task list to see if we can remove that restriction, FWIW
Nov 08 11:02:39 <bluelightning> yes, I agree, the script is evil
Nov 08 11:04:06 <broonie> I'm pretty sure Crofton volunteered to write some actual documentation so that you could do things by hand if you want :)
Nov 08 11:04:49 <KotH> ok.. now it downloaded a ton of other git repos into sources...
Nov 08 11:07:26 <KotH> what does BSP stand for?
Nov 08 11:08:03 <broonie> Board Support Package or Bug Squasking Party depending on context.
Nov 08 11:11:42 <bluelightning> KotH: so those git repos are the metadata I was referring to
Nov 08 11:12:43 <KotH> juup
Nov 08 11:12:52 <KotH> i'm already digging trough the structure :)
Nov 08 11:22:13 <KotH> .o0(python is damn memory heavy)
Nov 08 12:51:17 <KotH> bluelightning: it seems to be ding something now.. though i dont quite understand what ...  i'll probably see when it's finished :)
Nov 08 12:51:22 <KotH> s/ding/doing/
Nov 08 13:29:12 <captainigloo> i built a angstrom efl-nodm-image based on oe-core, and my user boot time is 8.7s on the beagleboard :(
Nov 08 13:44:57 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * r9534bd03e6 10testlab/beaglebone/eglibc/Cloud9-IDE/ (3 files): beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision c87192738b14347a393a6c2fec93390725711af1
Nov 08 15:26:05 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * r7b34215137 10testlab/beaglebone/eglibc/Cloud9-IDE/ (4 files): beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision c87192738b14347a393a6c2fec93390725711af1
Nov 08 16:46:55 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * rd8ac6ed8df 10testlab/beaglebone/eglibc/Cloud9-IDE/build-id: beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision 1b892012f269991db14899d15c601bf333535901
Nov 08 20:28:41 <CIA-55> angstrom: 03testlab <testlab@angstrom> 07yocto * r5d9ffcdf31 10testlab/beaglebone/eglibc/Cloud9-IDE/ (5 files): beaglebone: Cloud9-IDE configured for angstrom v2011.11-core using branch angstrom-staging and revision 6d215a0ca021089a8253f3dee2cb9fc5f0fe50a0
**** ENDING LOGGING AT Wed Nov 09 02:59:57 2011