**** BEGIN LOGGING AT Mon Sep 04 02:59:57 2006 Sep 04 03:16:43 placid_: i just copied a 2.5GB file over, and it has the same md5 Sep 04 03:16:54 can you make sure it is not other factor? Sep 04 03:17:31 yep. may be an issue on my main box although I've only just started having the problem Sep 04 03:17:47 can someone do a samba LFS test? (optware) Sep 04 03:18:05 I'm getting the same error with rsync which makes me suspicious of samba on my dev machine Sep 04 03:18:47 because I'm rsyncing to a samba mount on my machine Sep 04 05:21:05 hmm I fixed the samba problem by including lfs in fstab. so now I have establish why rsync bombs in a similar manner Sep 04 07:21:02 NAiL, just resent my defconfig file for busybox ... i diffed my personal one against the oe-version and somehow they weren't even NEAR the same file Sep 04 07:21:23 NAiL, so something must have gone wrong the first time i sent you one Sep 04 15:10:35 03nail 07slugos-3.10-beta * r358 10slugos/openembedded/packages/wakelan/wakelan_1.1.bb: wakelan: Update to match OE Style guidelines Sep 04 15:10:57 03nail 07slugos-3.10-beta * r359 10slugos/openembedded/packages/bwmon/bwmon_1.3.bb: bwmon: Update to match OE Style guidelines Sep 04 15:11:40 03nail 07slugos-3.10-beta * r360 10slugos/openembedded/packages/nonworking/icecast/: icecast: move to nonworking Sep 04 15:13:28 03nail 07slugos-3.10-beta * r361 10slugos/openembedded/packages/libdvb/libdvb_0.5.5.1.bb: libdvb: Update to match OE Style guidelines Sep 04 15:18:58 03nail 07slugos-3.10-beta * r362 10slugos/openembedded/packages/libol/libol_0.3.16.bb: libol: Update to match OE style guidelines Sep 04 15:20:04 03nail 07slugos-3.10-beta * r363 10slugos/openembedded/packages/litestream/litestream_1.3RC3.bb: litestream: Update to match OE Style guidelines Sep 04 15:36:03 03nail 07slugos-3.10-beta * r364 10slugos/openembedded/packages/watchdog/watchdog_5.2.bb: watchdog: Update to meet OE Style guidelines Sep 04 15:36:35 03nail 07slugos-3.10-beta * r365 10slugos/openembedded/packages/zd1211/ (zd1211_r77.bb zd1211_r83.bb): zd1211: Update to meet OE Style guidelines Sep 04 15:37:16 03nail 07slugos-3.10-beta * r366 10slugos/openembedded/packages/syslog-ng/syslog-ng_1.6.8.bb: syslog-ng: Update to meet blah-blah, fix initscript bug Sep 04 15:37:50 03nail 07slugos-3.10-beta * r367 10slugos/openembedded/packages/ssmtp/ssmtp_2.61.bb: ssmtp: OE style guidelines Sep 04 15:40:59 03nail 07slugos-3.10-beta * r368 10slugos/openembedded/packages/vsftpd/vsftpd_2.0.3.bb: vsftpd: Update to meet OE style guidelines Sep 04 15:51:53 03nail 07slugos-3.10-beta * r369 10slugos/openembedded/packages/qc-usb/ (3 files in 2 dirs): qc-usb-messenger: Drop old version & OE Style Sep 04 15:52:25 03nail 07slugos-3.10-beta * r370 10slugos/openembedded/packages/icecast/: icecast: Delete leftover Sep 04 15:52:58 03nail 07slugos-3.10-beta * r371 10slugos/openembedded/packages/openntpd/openntpd_3.7p1.bb: openntpd: OE Style Sep 04 15:53:35 03nail 07slugos-3.10-beta * r372 10slugos/openembedded/packages/sane-backends/sane-backends_1.0.15.bb: sane-backends: OE Style Sep 04 16:52:06 03nail 07slugos-3.10-beta * r373 10slugos/README: Add note about IPL -> BSD rename Sep 04 17:32:08 bogofilter builds cross just fine with sqlite3 as database engine Sep 04 17:43:04 only rpath is a problem, but I don't need bogofilter, maybe somebody else would like to try Sep 04 18:49:13 hi Sep 04 18:50:08 morning Sep 04 18:50:19 evening here ;] Sep 04 18:50:57 i have a problem... i'm using debian installed using debian-etch-beta2-20060311 and have a fatslug with 64mb... and dont have any idea how to make the system see the extra ram Sep 04 18:51:22 ~ugt Sep 04 18:51:24 [ugt] Universial Greeting Time. Created in #mipslinux, it is a rule that states that whenever somebody enters an IRC channel it is always morning, and it is always late when the person leaves. The local time of any other people in the channel, including the greeter, is irrelevant. http://www.total-knowledge.com/~ilya/mips/ugt.html Sep 04 18:51:55 thx 4 the info ;] Sep 04 18:52:01 morning Sep 04 18:52:12 how about my problem ?? Sep 04 18:52:46 i know that it can be done by using apex... but i dont have jtag and probablly wont have it so i dont wanna risk Sep 04 18:52:49 which bootloader do you use? Sep 04 18:52:56 redboot Sep 04 18:53:24 well, assuming, that you read this http://www.nslu2-linux.org/wiki/HowTo/FattenYourSlug , it wont work with redboot Sep 04 18:53:42 yes i've read it Sep 04 18:54:10 but, also saomeone wrote that a change to the kernel can make it work Sep 04 18:54:52 ah ja, that's true, but have you tried that modification? Sep 04 18:55:09 nope... thats why i'm here ;] Sep 04 18:55:21 totally dont know how to do it :/ Sep 04 18:57:25 afair, build your own image (using the mastermakefile) and do some changes in somewhere in the configs... maybe, that #openslug is a better channel to place your questions Sep 04 18:58:46 ping Sinclair73de ? Sep 04 18:59:33 is there maybe a channel for debianslug users ?? Sep 04 19:00:00 Szafran, or you may ask Sinclair73de (if he's available), as far as i known, he runs a fat slug, he should know, how to build a kernel/image, which fits Sep 04 19:01:01 Szafran, #debonaras maybe Sep 04 19:01:57 does flashing apex make any sense without jtag ?? Sep 04 19:01:58 but the problem is os independend, it depends on how you configure the kernel/image build Sep 04 19:02:16 does somebody has fatten his ds101g? It has already the places for the ram chips on the pcb, so it might be doable. Sep 04 19:04:39 btw, gda_ , haven't had any time to review the "problems" with clamav, so if there are doubles in the setup/postinst, just remove it Sep 04 19:05:13 it's not that easy Sep 04 19:06:09 Szafran: I've flashed APEX on two of my slugs. However, you need serial to do it. Sep 04 19:06:10 rc.clamav looks like it was one day part of a postinst script Sep 04 19:06:47 nothing gets started in rc.clamav Sep 04 19:07:37 NAiL: it can't be done from redboot ?? (serial -> you mean jtag ?) Sep 04 19:08:03 it can be done from redboot, but you will need serial (not JTAG) to do it Sep 04 19:08:15 currently too tired to start a new rc.clamav from scratch, the only reference I have is too complicated for optware Sep 04 19:08:24 because once you start apex (in order to flash it), you loose the network connection Sep 04 19:08:54 gda_, back soon, will restart in linux Sep 04 19:09:05 and whats the difference between jtag and serial in this matter ?? Sep 04 19:09:43 caplink811_log: hä, and what are you runnning now? Sep 04 19:17:20 * caplink811_log wonders why the fs is marked dirty all the time... Sep 04 19:22:36 gda_, you're right, that make no sense to me, seems, that i should fix that thing.... xp, haven't found time, to port the dev env in a virtual machine Sep 04 19:24:04 Szafran: read the wiki Sep 04 19:27:54 caplink811_log, what fs? vfat? Sep 04 19:43:57 NAiL: is the serial neccessary ?? or can i just use a usb2serial in one of the slugs usb ports ?? Sep 04 19:46:07 Szafran, you need the serial mod Sep 04 19:46:38 :/ Sep 04 19:46:43 the usb-2-serial converters are initialised by the linux kernel, which is loaded after redboot Sep 04 20:13:58 Szafran: First, you need to follow this howto: http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort Sep 04 20:14:40 Szafran: then, follow this: http://wiki.buici.com/wiki/Apex_Bootloader#IXP42x_and_the_Linksys_NSLU2_.28aka_SLUG.29 Sep 04 20:15:08 Then the kernel should detect (and be able to use) all your ram. Sep 04 20:16:32 be aware, after installing APEX, you will not be able to reflash from the bootloader over the network Sep 04 20:16:47 (APEX doesn't have network support, that's why you need the serial mod) Sep 04 20:18:33 and what about the flashing state (the one where you need to hold reset button untill status led turns red and then let go of the button)?? is this also a part of the redboot ?? Sep 04 20:18:46 that is redboot, yes Sep 04 20:19:21 apex doesnt have sthing like this ?? and only way is to flash through serial, right ? Sep 04 20:19:58 once you've flashed apex, the only ways to flash are either through serial, or from a fully booted system. Sep 04 20:21:10 oh, so when debian is alive then i'll be able to flash redboot back, or even the entire FW ? Sep 04 20:22:21 yes Sep 04 20:22:34 but reflashing redboot will limit your ram to 32mb again Sep 04 20:30:23 yes i know, but it's nice to know that there is a way back, just in case Sep 04 20:31:47 anyways i have 64mb now but in 2 days i'll have 128mb installed Sep 04 20:33:10 is there a possibility to limit the ram to 64mb under apex (in case if under debian will be some errors that come out in openslug - if my memory is correct) Sep 04 20:33:28 I think so Sep 04 20:43:04 and, as i see, apex is available to download from debian archive allready compilled for the slug =o] Sep 04 20:43:10 03nail * r360 10kernel/trunk/patches/2.6.17/ (40-scsi-idle.patch series): 2.6.17: Add scsi-idle patch Sep 04 20:43:49 This package is a version of APEX configured for the Linksys NSLU2 network appliance. In this case, APEX is used as a second stage loader so that Redboot, as installed by the manufacturer, may remain. Sep 04 20:44:03 is this the way to go ?? Sep 04 20:44:44 caplink811_log: if you are fixing rc.clamav, then do me please the favour and make it easy not to start clamd, at default only freshclam should be started Sep 04 20:45:21 gda_, sure, i'll do it at this way Sep 04 20:45:50 AFAIK only amavisd is currently using clamav and it can use clamscan, so no need for another daemon that needs memory Sep 04 20:45:59 amavisd already takes too much Sep 04 20:47:03 amavisd can use clamd and it is faster then, but better wait some seconds and have more memory free Sep 04 20:47:52 butI think I don't tell you newa Sep 04 20:48:01 s/newa/news/ Sep 04 20:48:02 gda_ meant: butI think I don't tell you news Sep 04 20:49:17 Szafran: go ask in #openjtag. I don't know which of the APEX binaries to use Sep 04 20:49:40 caplink811_log: too sad that clamav is the only antivirus solution that runs on the ds101g Sep 04 20:50:22 the description is copied from aptitude. so i think this should work. Sep 04 20:50:40 but first i think i'll try to recompile the kernel somehow Sep 04 20:54:15 from time to time the system clock of my ds101g has jumped 8 hours into the future after a boot, but not always, ideas? Sep 04 21:01:22 not me, but, the clock of the nslu isn't the best, i run ntpdate (small) at the startup. and every 20 mins, so the time is always adjust to the right Sep 04 21:02:17 ds101g firmware allows to use ntp, but didn't help, it looks like the timezone jumps completly Sep 04 21:04:15 /etc/synoinfo.conf:timezone="Amsterdam" Sep 04 21:04:46 \/etc.defaults/synoinfo.conf:timezone="Pacific" Sep 04 21:04:58 are this 8 hours? Sep 04 21:05:23 assuming, yes Sep 04 21:05:57 now I have only to find out what is using this info when and why ;) Sep 04 21:07:10 or I set etc.defaults/synoinfo.conf:timezone generally to Amsterdam and don't care Sep 04 21:09:38 * caplink811_log have to leave now (same tz it is) bye and gnite :) Sep 04 21:10:16 n8 Sep 04 21:35:26 more /etc/TZ Sep 04 21:35:26 CET-1CEST-2 Sep 04 21:35:37 does this only look strange for me? Sep 04 21:35:48 "-"? Sep 04 21:36:18 I don't know the format Sep 04 21:36:35 It's documented on the openwrt wiki IIRC Sep 04 21:37:25 will look there, but this is part of the original synology firmware Sep 04 21:37:34 yeah Sep 04 21:39:07 at least the beginning is the same Sep 04 21:39:08 http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html Sep 04 21:39:54 Here, it's CET+1CEST+2 IIRC Sep 04 21:40:51 or, CET+1CEST... that should give the same result. Sep 04 21:40:59 http://wiki.openwrt.org/OpenWrtDocs/Configuration#head-a7708420e79025405daa939605108397c2bd7343 Sep 04 21:41:24 hmm Sep 04 21:41:28 odd Sep 04 21:41:49 morning, blaster8 ;) Sep 04 21:42:10 but it is not set as env, it is only in /etc/TZ Sep 04 21:42:29 shouldn't matter. The TZ env and /etc/TZ should work the same way Sep 04 21:44:22 but more /etc.defaults/TZ Sep 04 21:44:22 PST8PDT7 Sep 04 21:44:38 so from time to time it uses this Sep 04 21:44:51 and my clock jumps 8 hours Sep 04 21:45:49 if it will happen next time I will overwrite it Sep 04 21:53:58 n8 Sep 04 22:14:49 * NAiL commits 2.6.18-rc6 to the kernel repo and tries to start applying the patches Sep 04 22:14:54 03nail * r361 10kernel/trunk/patches/2.6.18/ (35 files): 2.6.18: Initial commit of 2.6.18 (Untested) Sep 04 22:41:56 03nail * r362 10kernel/trunk/patches/2.6.18/ (01-nas100d-leds.patch series): 2.6.18: Remove nas100d-leds.patch. Accepted upstream Sep 04 22:47:04 03nail * r363 10kernel/trunk/patches/2.6.18/ (03-nslu2-leds.patch series): 2.6.18: Remove 03-nslu2-leds.patch, accepted upstream Sep 04 23:05:09 03nail * r364 10kernel/trunk/patches/2.6.18/ (15-jffs2-endian-config.patch 40-scsi-idle.patch series): 2.6.18: Four patches that don't apply. dsm600g, arm-leds and ixp timer Sep 04 23:40:51 03bzhou * r4017 10optware/trunk/make/ (py-paste.mk py-pastescript.mk): py-paste{,script}: upstream upgrade to 0.9.8 Sep 04 23:59:54 03nail * r365 10kernel/trunk/patches/2.6.18/ (50-leds-arm-cpu-activity.patch 75-dsmg600.patch series): 2.6.18-rc6: Fixup dsm600g patches and leds patches Sep 05 00:07:35 03nail * r366 10kernel/trunk/patches/2.6.18/patch-2.6.17-ide1: Re-add ide-patch to repo Sep 05 00:09:29 03nail * r367 10kernel/trunk/patches/2.6.18/ (77-velocity-module.patch 78-velocity-BE.patch series): 2.6.18-rc6: refresh velocity patches Sep 05 01:12:43 03nail * r368 10kernel/trunk/patches/2.6.18/series: 2.6.18-rc6: Remove the two non-applying nslu2 patches Sep 05 01:14:09 03nail * r369 10kernel/trunk/patches/2.6.18/defconfig: 2.6.18-rc6: defconfig update **** ENDING LOGGING AT Tue Sep 05 02:59:56 2006