**** BEGIN LOGGING AT Thu Jul 11 02:59:58 2013
Jul 11 08:03:08 <radekp_> hi, i have ported devtmpfs to our old openmoko 2.6.29 kernel. It works but all the devices are created stright in /dev
Jul 11 08:03:35 <radekp_> e.g. input events are now /dev/event0 but they are /dev/input/event0 in later kernels
Jul 11 08:04:03 <radekp_> same for sound nodes - they are /dev/pcmC0D0c instead of /dev/snd/pcmC0D0c
Jul 11 08:04:16 <radekp_> any ideas?
Jul 11 08:13:19 <lindi-> radekp: why 2.6.29 and not 2.6.34 btw?
Jul 11 08:13:49 <radekp> lindi-: i have seen resume problems with 2.6.34
Jul 11 08:14:08 <lindi-> radekp: have you reported them somewhere?
Jul 11 08:14:33 <radekp> lindi-: there was complain on ML like week ago and i have experienced it myself too twice
Jul 11 08:14:34 <lindi-> radekp: I have seen them in 2.6.29, 2.6.34 and 2.6.39 but 2.6.34 was still much better than 2.6.39
Jul 11 08:14:49 <lindi-> I still run 2.6.34 for several years now
Jul 11 08:15:32 <radekp> i was running 2.6.34 for long time too - but i want to try 2.6.29 now
Jul 11 08:15:38 <lindi-> ok
Jul 11 08:16:32 <radekp> i wonder if it's worth reporting...
Jul 11 15:03:11 <DocScrutinizer05> OS-Command Injection via UPnP Interface in multiple D-Link devices   http://www.s3cur1ty.de/m1adv2013-020
Jul 11 15:11:21 <pabs3> is that those semi-recent miniupnp vulnerabilities?
Jul 11 15:11:43 <pabs3> (the page is 404)
Jul 11 15:12:16 <pabs3> oh, it is only 404 if you don't send a User-Agent, weird
**** ENDING LOGGING AT Fri Jul 12 02:59:58 2013