**** BEGIN LOGGING AT Tue Dec 11 02:59:57 2007
Dec 11 04:54:19 <CIA-8> 03osas 07slugos-3.10-beta * r430 10slugos/openembedded/packages/meta/slugos-packages.bb: slugos-packages.bb: enable asterisk 1.4 sound packages
Dec 11 05:02:09 <CIA-8> 03bzhou * r7443 10optware/trunk/ (3 files in 2 dirs): plan9port: builds for nslu2 unslung now
Dec 11 05:39:47 <CIA-8> 03osas 07slugos-3.10-beta * r431 10slugos/openembedded/packages/meta/slugos-packages.bb: slugos-packages.bb: enable monit
Dec 11 06:01:42 <CIA-8> 03bzhou * r7444 10optware/trunk/sources/plan9port/postinst: plan9port: export PLAN9 PATH
Dec 11 14:13:35 <VoodooZ> If I add a new package to the packages folder do I still have to add it to a file somewhere? (I remember something about freezing packages...)
Dec 11 14:26:30 <rwhitby> we don't do freezing any more
Dec 11 14:26:49 <rwhitby> you may want to add it to an image or feed.
Dec 11 15:05:12 <VoodooZ> rwhitby: yep. that I already did but I meant for OE to consider in existance? Just putting it in packages/ is enough basically?
Dec 11 15:26:55 <CIA-8> 03osas 07slugos-3.10-beta * r432 10slugos/openembedded/packages/nano/ (nano-2.0.6/ nano-2.0.6/glib.m4 nano_2.0.6.bb): nano: 1.3.9 -> 2.0.6
Dec 11 15:29:01 <CIA-8> 03osas 07slugos-3.10-beta * r433 10slugos/openembedded/packages/dnsmasq/ (dnsmasq.inc dnsmasq_2.38.bb): dnsmasq: 2.22 -> 2.38
Dec 11 20:46:11 <rwhitby> VoodooZ: yes, just putting it in packages is enough
Dec 11 22:11:27 <VoodooZ> rwhitby: btw, Is it true that slugosbe doesn't make use of a ramdisk in any way (even the fis entry)? 
Dec 11 22:12:30 <VoodooZ> I reinstalled apex with the correct kernel cmdline string but now it won't boot at all.. I noticed that this apex build disables ramdisk so I'm wondering
Dec 11 22:18:21 <VoodooZ> or in short: what are people using in terms of apex's startup string? (printenv will show it)
Dec 11 22:18:30 <VoodooZ> mine is: startup *= copy $kernelsrc $bootaddr; wait 10 Type ^C key to cancel autoboot.; boot
Dec 11 22:19:23 <VoodooZ> the only diff is that before it copied the ramdisk from flash to ram between the kernel load and wait instruction...
Dec 11 23:10:30 <rwhitby> VoodooZ: we don't use the ramdisk - we boot straight to jffs2
Dec 11 23:11:01 <rwhitby> and apex is able to skip over the mandatory 16 byte length header at the start of the ramdisk partition, so the kernel can extend into that area.
Dec 11 23:11:12 <rwhitby> (to make up for the space that apex takes)
Dec 11 23:32:00 <VoodooZ> ok. just looking for what could have changed.
Dec 11 23:33:01 <VoodooZ> Is the trailer before the kernel (and the ramdisk one) still in use aside Redboot, which I don't use?
Dec 11 23:54:37 <VoodooZ> I'm starting to think my latest kernel is busted then... passing execution to 0x00008000 just stops there...
Dec 12 00:07:38 <rwhitby> VoodooZ: ramdisk header and trailer and only used by redboot
Dec 12 00:38:24 <VoodooZ> ok. I got it to boot to an old kernel... and from there was able to cat a newer kernel to /dev/mtdblock2.. appears good. thanks.
Dec 12 00:39:41 <VoodooZ> Now I need to get my private package built as OE skips it..
Dec 12 01:30:08 <joshin> Bah, I (almost) give up on the oom-killer problem.  Its beyond my kernel hacking skills.   I''m tempted to kludge in a 2.4 kernel.
Dec 12 02:23:32 <CIA-8> 03bzhou * r7445 10optware/trunk/make/squid.mk: squid: 2.6.16 -> 2.6.17
Dec 12 02:47:55 <CIA-8> 03bzhou * r7446 10optware/trunk/make/samba.mk: samba: 3.0.27a -> 3.0.28
**** ENDING LOGGING AT Wed Dec 12 02:59:57 2007