**** BEGIN LOGGING AT Mon Mar 17 02:59:56 2008 Mar 17 03:39:08 03rwhitby * r7989 10optware/trunk/make/perltgd.mk: perltgd: Updated to betaM Mar 17 03:41:38 03bzhou * r7990 10optware/trunk/make/sane-backends.mk: sane-backends: libsane.so already named 1.1.0 Mar 17 04:01:27 03osas * r7991 10optware/trunk/make/openser.mk: openser: 1.3.0 -> 1.3.1 Mar 17 14:21:31 ran into an odd error in building what should be a truly basic recipe utilizing the CPAN class Mar 17 14:21:37 make: *** No rule to make target `/usr/lib/perl/5.8/Config.pm', needed by `Makefile'. Stop. Mar 17 14:21:44 not sure what to make of that Mar 17 14:21:55 does it mean the CPAN module is missing? Mar 17 15:45:49 03bzhou * r7992 10optware/trunk/make/py-simpy.mk: py-simpy: 1.9 -> 1.9.1 Mar 17 16:02:18 03bzhou * r7993 10optware/trunk/make/py-simplejson.mk: py-simplejson: 1.7.3 -> 1.7.5 Mar 17 17:22:48 03bzhou * r7994 10optware/trunk/make/py-4suite.mk: py-4suite: py-4suite -> py24-4suite Mar 17 17:23:06 03bzhou * r7995 10optware/trunk/make/py-amara.mk: py-amara: py-amara -> py24-amara Mar 17 17:33:48 03bzhou * r7996 10optware/trunk/make/py-trac.mk: py-trac: py-trac -> py24-trac Mar 17 17:41:12 03bzhou * r7997 10optware/trunk/make/py-mercurial.mk: py-mercurial: py-mercurial -> py24-mercurial Mar 17 17:56:11 03bzhou * r7998 10optware/trunk/make/py-webpy.mk: py-webpy: py-webpy -> py24-webpy Mar 17 18:16:31 Help. I just unplugged my USB flashdrive from my Linksys NSLU2 (it was ext3 formatted and running Debian). Mar 17 18:16:35 I inserted a Knoppix Live CD and removed the journal, using tune2fs and 2fsck Mar 17 18:16:42 Then I edited /etc/fstab, putting "ext2" instead of "ext3". But now it doesn't boot anymore o.o Mar 17 18:16:47 Can someone help me? What's going wrong and am I still able to boot my Debian? ^^ Mar 17 18:51:18 l0c4lh0st: You probably needed to edit the /etc/fstab on the flash filesystem; that's what would mount the USB flashdrive with the Debian rootfs. Mar 17 18:51:37 Yes I did. I changed it to ext2. Mar 17 18:51:37 I have no idea how you can do that, or how you would recover from your current situation. Mar 17 18:51:53 You changed it on the flash filesystem on the NSLU2 itself? Mar 17 18:52:12 Or did you edit the fstab that was on the USB drive? Mar 17 18:52:37 Yes. I edited the fstab on the USB drive. Mar 17 18:52:46 So how would I get into the NSLU2 flash? Mar 17 18:53:21 I have no idea how you can do that, or how you would recover from your current situation. Mar 17 18:53:46 You would need a debian arm expert... Mar 17 18:53:46 So when I convert my USB drive back to ext3, I can access it again? Mar 17 18:53:52 I'm gonna try that ^^ Mar 17 18:53:55 Dunno. I would think so. Mar 17 18:54:08 Then I have at least a working NSLU2. Mar 17 18:54:48 Or do you know a way to install Debian on ext2, instead of ext3/ Mar 17 18:54:55 I can only choose ext3 on install. I want ext2. Mar 17 18:56:41 l0c4lh0st: You should probably ask Debian questions on the Debian ARM IRC channel; you are more likely to find someone who knows the answer. The channel is listed on the wiki, IIRC. Mar 17 18:57:11 #debian-arm is gone Mar 17 18:58:38 on irc.oftc.net ? Mar 17 19:49:48 03bzhou * r7999 10optware/trunk/make/py-serial.mk: py-serial: py-serial -> py24-serial Mar 17 19:50:25 03bzhou * r8000 10optware/trunk/make/py-genshi.mk: py-genshi: py-genshi -> py24-genshi Mar 17 20:02:18 03bzhou * r8001 10optware/trunk/make/py-scgi.mk: py-scgi: rename 2.4 ipk as py24-scgi Mar 17 20:02:39 03bzhou * r8002 10optware/trunk/make/py-quixote.mk: py-quixote: rename 2.4 ipk as py24-quixote Mar 17 22:14:21 03bzhou * r8003 10optware/trunk/make/py-openssl.mk: py-openssl: renamed python2.4 ipk to py24-openssl Mar 18 00:51:44 hi! Mar 18 00:53:58 Could you perhaps add the ./configure parameter "--enable-inotify" to the mediatomb package? Mar 18 00:55:00 if you don't use it, mediatomb will try to look at the build system if it has inotify support in the kernel, but if you add it, mediatomb will compile it in anyway, and look at runtime if it could be used. Mar 18 00:55:43 http://mediatomb.cc/pages/documentation#id2486887 Mar 18 00:57:11 especially for the ds101 builds. the latest firmware supports inotify, but it's not compiled in, while it seems to be compiled in for syno-x07. Mar 18 00:57:30 If I should ask for that somewhere else, please let me know! Mar 18 00:59:00 andreask2: the current mediatomb configuration logic in optware is: Mar 18 00:59:17 if toolchain kernel header is 2.4, --disable-inotify Mar 18 00:59:25 otherwise, --enable-inotify Mar 18 00:59:53 so it could be that ds101 toolchain lags behind firmware Mar 18 01:00:20 while latest firmware is 2.6 and supports inotify Mar 18 01:00:32 the toolchain does not (probably is still 2.4) Mar 18 01:02:09 2.6 is not only in the latest firmware only, it's there for quite some time... Mar 18 01:02:32 the problem is not the firmware, but optware ds101 toolchain Mar 18 01:02:37 but you don't have to care for problems with the kernel, mediatomb will do it at runtime Mar 18 01:03:10 it's described here: http://mediatomb.cc/pages/documentation#id2486887 Mar 18 01:03:15 without proper kernel headers, it won't even compile Mar 18 01:03:22 hm Mar 18 01:05:59 i'm trying a compile with --enable-inotify with ds101 and see how it goes Mar 18 01:06:32 oh great! Mar 18 01:06:39 the docs say: Mar 18 01:06:42 "If you specify this option, the functionality will be compiled in even if the build system does not support inotify - the availability of inotify will then be checked at server runtime" Mar 18 01:07:35 are there any plans to upgrade the toolchain to the current synology build system with 2.6 kernel? Mar 18 01:07:58 the upcoming DS508 will be PPC again... Mar 18 01:08:14 someone with synology should take the initiative Mar 18 01:09:13 is there any documentation on how to create such a toolchain? Mar 18 01:09:23 or, donate to nslu2-linux to make it happen Mar 18 01:10:44 I'll do so, I really love it! Mar 18 01:11:40 either you have the toolchain binary, use crosstool to create one for glibc, or buildroot to create one for uclibc Mar 18 01:12:29 i must say creating a proper toolchain is half the work of getting optware onto a new platform Mar 18 01:19:47 ok, it builds fine with --enable-inotify Mar 18 01:19:58 let me enable it Mar 18 01:20:36 (but i definitely have seen --enable-inotify having compilation problem somewhere) Mar 18 01:22:19 with mediatomb? Mar 18 01:22:24 yes Mar 18 01:22:32 perhaps an old version Mar 18 01:22:50 no, just this version, on a different platform Mar 18 01:42:40 where do you enable it? can I get such a binary somehow/soon? Mar 18 01:43:05 i'll enable it in the official feed Mar 18 01:43:24 the problem platform is openwrt-brcm24 Mar 18 01:43:34 i'm trying to solve that right now Mar 18 01:44:06 ah, thank you very much, what I saw was: http://trac.nslu2-linux.org/optware/changeset/7945 Mar 18 01:44:37 if you have optware/ds101 build environment, pretty easy to change the configuration yourself Mar 18 01:45:13 is it, what is described here: http://www.nslu2-linux.org/wiki/Development/MasterMakefile ? Mar 18 01:45:31 you can start from MasterMakefile, but you don't have to Mar 18 01:46:09 http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware Mar 18 01:54:59 03bzhou * r8004 10optware/trunk/make/mediatomb.mk: mediatomb: disable inotify only on openwrt-brcm24 Mar 18 01:57:10 that's great, thank you so much for looking into it! Mar 18 01:58:19 I'll try to create another package on my own, if it works you can add it if you want. Mar 18 01:58:46 bye! Mar 18 02:20:36 03bzhou * r8005 10optware/trunk/make/py-trac.mk: py-trac: removing old IPK_DIR **** ENDING LOGGING AT Tue Mar 18 02:59:57 2008