**** BEGIN LOGGING AT Sat Jun 16 02:59:56 2007 Jun 16 19:05:57 hi NAiL - long time (-; Jun 16 19:06:08 morning ;) Jun 16 19:06:11 sorry - my contract is killing me. must.... finish.... Jun 16 19:06:29 this working for a living isn't everything it's cracked up to be (-; Jun 16 19:06:36 how's the car? Jun 16 19:10:42 hey, what was that LED/fan daemon named? pvr-something? Jun 16 19:10:43 having minor engine troubles Jun 16 19:11:43 I'm hoping to buy a new engine and transmission in two weeks time. Upgrade the car from 2.0L to 2.3L Jun 16 19:12:31 can't remember the name of the daemon Jun 16 19:16:36 that'll be nice. diesel? most of the EU is, right? Jun 16 19:17:59 nothing from jdl in two weeks now. of course, he is doing this for free, but i'll ask him to send me the unit back in another few weeks if there is no progress and perhaps send it to dwery, if you think he's open to helping. Jun 16 19:18:33 not diesel, no Jun 16 19:18:49 we can ask him :) Jun 16 19:24:48 thanks. Jun 16 19:41:35 hmmm, no luck googling. NAiL, do you remember what devices it runs on? The nas100d perhaps? Jun 16 19:56:23 NAiL??? Jun 16 21:23:52 NAiL, at long last, you disk is in the mail. Jun 16 21:38:44 ah, cool Jun 16 21:38:57 btw, the daemon runs on the linkstations and the kuros Jun 16 21:42:42 ah, so now you are all helpful! (-; Jun 16 21:43:22 heh Jun 16 21:43:26 i packed it well - and put a note inside that said it didn't work for me, good luck, and a $25 value. Jun 16 21:43:34 Trying to figure it out ;) Jun 16 21:43:37 ah, good Jun 16 21:43:58 just $16 to ship it. not bad. Jun 16 22:31:12 avr_evtd Jun 16 22:37:44 THANKS! Jun 16 22:38:13 np :) Jun 16 22:38:16 we are having a wierd problem with ours... it seems to just miss the first few commands. not sure what is going on. just reviewed our code and it looks solid. Jun 16 22:38:35 maybe the pic comes up in a wierd state, and needs more resets or more time? dunno. Jun 16 22:51:02 hi rwhitby Jun 16 23:12:48 hey HopsNBarley Jun 17 00:08:31 rwhitby, a design question, if you have a minute. we have a client that is doing a media player type device. they want to do an initramfs rootfs, but we are trying to bend them to a JFFS2 root with some links to a volatile /var/log, /tmp, etc. they are very very concerned about HW failure ,and are raising the issue of exceeeding flash write cycles. Jun 17 00:09:19 if we link out the most volatile things, i just can't imagine 1M writes over the device life. what's your opinion? Jun 17 00:16:41 HopsNBarley: in slugos, with turnup memstick, we make sure that the only time that jffs2 is written is either on boot or on a user command. Jun 17 00:17:04 and there's not going to be 1M of those events in a product's lifetime. Jun 17 00:47:50 rwhitby, thanks for the reality check! Jun 17 00:48:36 HopsNBarley: but you really do need to make sure that nothing else it writing to jffs2 (e.g. ext3 atime for instance) Jun 17 00:48:45 (or ext3 journal for that matter) Jun 17 00:50:03 okay. Jun 17 00:50:10 i'll take a look at turnup memstick. Jun 17 00:50:53 on the initramfs - they are already at 12M, and have more to add, and the device has just 64, so that would reach a dead-end soon of its own accord, i think. Jun 17 00:50:53 I think we used /proc/interrupts, or find -mtime or something to really check no writes were happening over an extended period Jun 17 00:51:04 good idea. Jun 17 00:51:25 thanks rod! i gotta run to take somebody to SFO airport. back in a bit... Jun 17 00:51:32 what about squashfs + mini_fo ? Jun 17 00:51:41 (that's what openwrt uses on the nslu2) Jun 17 00:51:55 squashfs rootfs, + jffs2 overlay. Jun 17 00:52:46 i;ll take a look at that! thanks. Jun 17 00:56:58 Kaloz is the expert on that **** ENDING LOGGING AT Sun Jun 17 02:59:56 2007