**** BEGIN LOGGING AT Fri Dec 29 02:59:59 2006 Dec 29 03:04:11 03rwhitby * r100 10slugimage/trunk/tests/ (8 files in 4 dirs): Seems that hexdump output is based on LANG settings, so canonicalise that. Dec 29 03:06:46 03rwhitby * r101 10slugimage/trunk/tests/ (8 files in 4 dirs): Update the expected outputs to be LANG=C Dec 29 03:08:13 slugimage now has a fairly good regression test suite. Dec 29 03:26:47 anyone know of a cleaner way to stop/start services than update-rc.d ? Dec 29 03:41:42 03bzhou * r4901 10optware/trunk/ (Makefile make/mutt.mk): mutt: fixed -I/opt/include for gcc4 cross compilation; promoted for slugosbe Dec 29 05:38:12 03bzhou * r4902 10optware/trunk/make/libogg.mk: libogg: fixed gcc4 cross compilation Dec 29 05:38:15 03bzhou * r4903 10optware/trunk/make/audiofile.mk: audiofile: fixed gcc4 cross compilation Dec 29 05:38:18 03bzhou * r4904 10optware/trunk/make/esound.mk: esound: fixed gcc4 cross compilation Dec 29 05:38:21 03bzhou * r4905 10optware/trunk/make/libvorbis.mk: libvorbis: fixed gcc4 cross compilation Dec 29 05:38:27 03bzhou * r4906 10optware/trunk/make/ivorbis-tools.mk: ivorbis-tools: fixed gcc4 cross compilation Dec 29 05:38:36 03bzhou * r4907 10optware/trunk/make/gift.mk: gift: fixed gcc4 cross compilation Dec 29 05:41:52 03bzhou * r4908 10optware/trunk/Makefile: promoted esound, gift*, ivorbis-tools, libvorbis, streamripper, & vorbis-tools for slugosbe Dec 29 06:43:37 03bzhou * r4909 10optware/trunk/Makefile: promoted esniper for slugosbe Dec 29 07:46:17 morning all Dec 29 07:46:35 NAiL: ping Dec 29 08:55:49 likewise: morning Dec 29 09:01:03 I've replaced all the caps. But I'm still getting the (apparently) PCI-related crash. It crashed before replacing the caps too, so I suspect a b0rked kernel. Dec 29 09:01:51 If not, I think the board is more or less dead. Dec 29 09:06:09 NAiL: OK, I just wanted to ask if I should send you the caps. Dec 29 09:06:19 or maybe a flash chip Dec 29 09:06:52 I've got two flash chips, need to check if they will work. Dec 29 09:09:45 What chips will work? Dec 29 09:10:04 I've got two flash chips that used to be bioses on something else Dec 29 09:13:03 I got the caps here at work, but the flash chip at home. But I think I mentioned in the wiki page. Dec 29 09:21:54 but what I'm looking for is primarily a 256kb (2mbit) part, right? Dec 29 09:22:07 Or 512kb if I flash both halves? Dec 29 09:22:54 There isn't any harm in trying to flash the chips and seeing if it works, is there? ;) Dec 29 09:51:16 hello :) Dec 29 09:51:28 has anyone ever set up a hidden service on an unslung slug using tor? Dec 29 10:31:55 03marceln * r4910 10optware/trunk/ (Makefile make/gnokii.mk): OPTWARE: Added gnokii Dec 29 11:26:53 likewise: It would appear that it might just be the hdd that is causing my problems Dec 29 11:35:06 NAiL: good to hear Dec 29 11:35:34 Not *entirely* sure yet, still gotta check a bit. But I have problems using the disk in an usb enclosure right now. Dec 29 11:35:52 which is a pain, because I don't have any replacement ATA-disks :-P Dec 29 11:36:03 S-ATA disks aplenty ;) Dec 29 11:50:00 likewise: Any pointers to how to boot from network? Dec 29 11:50:14 (Is it possible to boot from cdrom? usb?) Dec 29 11:50:35 NAiL: I think you would need to build Linuxbios with a different bootloader payload Dec 29 11:50:43 etherboot or such Dec 29 11:50:45 mmhmm Dec 29 11:50:57 I haven't gotten that far yet Dec 29 11:51:07 the image you gave me only supports ide? Dec 29 11:51:41 NAiL: I have enabled everything in FILO (see the defconfig file in filo-0.4.2/), I am not sure it does anything beyond IDE. Dec 29 11:51:50 ah Dec 29 11:51:51 ok Dec 29 11:52:01 NAiL: http://te.to/~ts1/filo/ Dec 29 11:52:29 thx Dec 29 11:53:03 I still can't boot, and I suspect it's the harddrive acting weird with the "host protected area" Dec 29 11:57:32 aha. Wrong jumper setting. Wonder if that makes a difference Dec 29 11:57:38 has anyone ever set up a hidden service on an unslung slug using tor? :) Dec 29 12:06:18 likewise: Filo 0.5 appears to have USB support Dec 29 12:07:09 Jollino: Quite possibly. Why are you asking? Dec 29 12:09:10 NAiL: because if i don't set up the hidden service, it works perfectly; if i do (it's a simple service on port 80 to 127.0.0.1:80) i keep getting a lot of "Invalid service descriptor rejected" messages, and the hidden service doesn't work Dec 29 12:09:43 privoxy immediately returns a domain not found page, rather than waiting a little Dec 29 12:09:47 ah... well.. um. No idea. Dec 29 12:10:58 i even tried removing the package and reinstalling it, just to make sure everything was clean Dec 29 12:25:34 i would compile the unstable version of tor but i have no way to crosscompile Dec 29 12:28:09 Jollino: you don't have a PC you can run Knoppix or VMWare on? Dec 29 12:29:50 well i can run a virtual machine with linux. i actually already have slackware installed on a VM (through parallels), but i don't think it can crosscompile out of the box. how do i try it? (i never crosscompiled anything) Dec 29 12:30:08 look at the Development section of the wiki Dec 29 12:30:43 Debian Sarge is our default host system (that's what the autobuilders run), but Ubuntu and CentOS (RedHat) should work too Dec 29 12:31:46 i'll investigate it Dec 29 12:36:27 hmm i guess i could install optware-devel Dec 29 12:37:40 better to cross-compile Dec 29 12:38:59 hm ok Dec 29 12:39:20 can i use ubuntu as a live cd? Dec 29 12:46:49 03oleo * r4911 10optware/trunk/ (7 files in 4 dirs): buildroot: switch to gcc-4.1.1 and binutils-2.17.50.0.8 - backported lrint and lrintf C99 math to uClibc 0.9.28 Dec 29 13:32:30 hi Dec 29 14:20:00 likewise: Finally got the debug info from my epia. It appears to crash when selecting scheduler (cfq or whatever it's called). Any idea why? Dec 29 14:21:17 no, which kernel are you using? CFQ emits block i/o transactions to the block device driver. Dec 29 14:21:52 NAiL: if you have multiple i/o schedulers built-in, you could try overriding the scheduler at the kernel parameter line. Dec 29 14:23:16 aha Dec 29 14:23:24 thx Dec 29 14:25:38 03oleo * r4912 10optware/trunk/ (3 files in 3 dirs): sendmail: uClibc dn_skipname solved with -DNAMED_BIND=0 Dec 29 14:30:06 likewise: no joy. BTW, would you mind sending me the caps anyway? I see one of the "new" caps I put in has started bulging Dec 29 14:30:43 NAiL: sure, send me your snailmail address to leonw _ mailcan.com Dec 29 14:31:05 NAiL: I'll put in an extra (double sized) FlashROM. Dec 29 14:33:40 cool, thanks :) Dec 29 14:37:07 likewise: Any idea if the Epia M10000G also works with linuxbios? Dec 29 14:37:57 I dunno that device, probably should ask for on the linuxbios list. Dec 29 14:38:10 It looks more or less exactly the same Dec 29 14:38:17 I know the guy that did work on the test framework, works with epia boards (coresystems.de or such) Dec 29 14:39:25 hmm.. I can't see any differences between the M10kG and the M10k Dec 29 14:40:29 I'm considering buying a new board, but I want one that can use linuxbios ;) Dec 29 14:41:06 I think that my current board is more or less junk, unless the caps fix it. Dec 29 15:53:07 NAiL: synology will send me a replacement side of my ds101g case :), I have only to pay for shipping Dec 29 16:45:56 03blaster8 * r645 10kernel/trunk/ (5 files in 3 dirs): Add Linus' fix for ext3 corruption issues spotted by Gordon, should be removed as soon as proper fix is implemented in stable/upstream Dec 29 16:53:07 gda_: replacement side? Dec 29 17:23:26 NAiL: a new right side of the case so that I can cut a hole for a big heatsink Dec 29 17:31:46 is your old case broken? Dec 29 17:43:03 NAiL: yesterday we talked about to mount a big heat sink to the harddisk of my ds101g Dec 29 17:44:00 for this I would have to break the case, but I don't do it without the possibility to reverse it Dec 29 17:44:11 aha Dec 29 17:58:48 But without the possibility to reverse it, success is guaranteed -- as one is commited to obtaining success! :D Dec 29 18:01:01 ~rules Dec 29 18:01:03 * jbot makes the rules. now stfu and code mode addons. Dec 29 18:01:21 * NAiL goes "huh?" Dec 29 18:01:23 ~rules Dec 29 18:01:24 * jbot makes the rules. now stfu and code mode addons. Dec 29 18:03:03 ~nslu2-rules Dec 29 18:03:05 hmm... nslu2-rules is 1) You must search the wiki before asking questions on IRC or mailing list. 2) You must follow the README steps precisely when flashing firmware. 3) Those who ask the questions, update the wiki with the answers. 4) Those who complain about doco, update the wiki to improve it. 5) Friends don't let friends flash custom firmware without ... Dec 29 18:05:35 jbot: nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool - it will brick your slug permanently. 2) You will search the wiki first and read the FAQ before asking questions. 3) You must read and follow the steps in the README file precisely when flashing firmware. 4) Those who ask the questions, update the wiki when they get the answers. 5) Those who complain about the documentation, update the wiki to make it better. 6) Friends don Dec 29 18:05:37 ...but nslu2-rules is already something else... Dec 29 18:05:51 hmm... how did that work again Dec 29 18:06:30 jbot: forget nslu2-rules Dec 29 18:06:31 i forgot nslu2-rules, NAiL Dec 29 18:06:36 jbot: nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool - it will brick your slug permanently. 2) You will search the wiki first and read the FAQ before asking questions. 3) You must read and follow the steps in the README file precisely when flashing firmware. 4) Those who ask the questions, update the wiki when they get the answers. 5) Those who complain about the documentation, update the wiki to make it better. 6) Friends don Dec 29 18:06:38 NAiL: okay Dec 29 18:06:45 ~nslu2-rules Dec 29 18:06:47 well, nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool - it will brick your slug permanently. 2) You will search the wiki first and read the FAQ before asking questions. 3) You must read and follow the steps in the README file precisely when flashing firmware. 4) Those who ask the questions, update the wiki when they get the answers. 5) Those who ... Dec 29 18:09:42 03oleo * r4913 10optware/trunk/Makefile: optware: promote bsdmainutils elinks erl-escript ficy procps sdl ser snownews xcursor xfixes xft xrender for uClibc Dec 29 18:09:56 jbot: nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool. 2) You will search the wiki first and read the FAQ before asking. 3) You must read and follow the steps in the README file precisely when flashing. 4) Those who ask the questions, update the wiki when they are answered. 5) Those who complain about the docu, update the wiki to improve it. 6) Friends don't let friends flash custom firmware without confirmed RedBoot Upgrade Mo Dec 29 18:09:56 ...but nslu2-rules is already something else... Dec 29 18:09:59 jbot: forget nslu2-rules Dec 29 18:09:59 i forgot nslu2-rules, NAiL Dec 29 18:10:01 jbot: nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool. 2) You will search the wiki first and read the FAQ before asking. 3) You must read and follow the steps in the README file precisely when flashing. 4) Those who ask the questions, update the wiki when they are answered. 5) Those who complain about the docu, update the wiki to improve it. 6) Friends don't let friends flash custom firmware without confirmed RedBoot Upgrade Mo Dec 29 18:10:11 jbot: nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool. 2) You will search the wiki first and read the FAQ before asking. 3) You must read and follow the steps in the README file precisely when flashing. 4) Those who ask the questions, update the wiki when they are answered. 5) Those who complain about the docu, update the wiki to improve it. 6) Friends don't let friends flash custom firmware without confirmed RedBoot Upgrade Mo Dec 29 18:10:13 okay, NAiL Dec 29 18:10:19 ~nslu2-rules Dec 29 18:10:20 i heard nslu2-rules is 1) Never *ever* use the Linksys EraseAll tool. 2) You will search the wiki first and read the FAQ before asking. 3) You must read and follow the steps in the README file precisely when flashing. 4) Those who ask the questions, update the wiki when they are answered. 5) Those who complain about the docu, update the wiki to improve it. 6) ... Dec 29 18:13:10 hmm Dec 29 18:13:12 ~nail Dec 29 18:13:14 * jbot nails $1 to #nslu2-linux Dec 29 18:13:19 bleh Dec 29 18:15:06 03oleo * r4914 10optware/trunk/make/gnuplot.mk: gnuplot: add libstdc++ depend Dec 29 18:16:08 ~nslu2-rules Dec 29 18:16:09 nslu2-rules is probably Short Ed: 1.) Use EraseAll, you're screwed. 2.) Search the wiki 1ST! 3.) Follow the README or else. 4.) If you ask, you'd better update wiki. 5.) Complain? Update the wiki 6.) Don't flash custom f/w w/o Redboot access. 7) Don't flash bootloaders w/o JTAG. Dec 29 18:16:44 ~botsnack Dec 29 18:16:44 thanks, ByronT Dec 29 18:20:23 03bzhou * r4915 10optware/trunk/ (Makefile make/gnokii.mk): promoted gnokii, explicit --without-x Dec 29 19:15:20 03bzhou * r4916 10optware/trunk/make/perl-dbd-sqlite.mk: perl-dbd-sqlite: 1.12 -> 1.13 Dec 29 20:12:38 03blaster8 * r646 10kernel/trunk/patches/2.6.20/ (12-fix-ext3-corruption.patch KERNEL series): Update to 2.6.20-rc1-git1, contains ext3 corruption fix Dec 29 20:48:52 03rwhitby * r4917 10optware/trunk/ (. make/mc.mk sources/mc/terminfo.patch): mc: Set default value for terminfo location. Closes: #5. Dec 29 20:51:27 marceln: can you test if that solves the problem? Dec 29 21:45:08 03bzhou * r4918 10optware/trunk/ (Makefile make/erl-yaws.mk make/erlang.mk): promoted $(ERLANG_PACKAGES) for slugosbe Dec 29 22:11:14 NAiL: I posted the stuff today, forgot to stick a priority label on it, but I guess everything is air-shipped these days, at least I hope so. Dec 29 22:17:33 rwhitby: What problem Dec 29 22:17:47 Sorry. I see it. Dec 29 22:19:43 rwhitby: Hi! Yesterdat you had a suggestion for idle... So when I go away, I do not need to do anything? Somewhere in ircclient there is a setting for idle time? Dec 29 22:23:39 rwhitby: It looks fine again. Dec 29 22:25:27 03osas * r4919 10optware/trunk/ (make/asterisk14.mk sources/asterisk14/configs.patch): asterisk14: fix configs Dec 29 22:42:05 03bzhou * r4920 10optware/trunk/ (10 files in 6 dirs): use /opt/bin/update-alternatives fullpath in postinst Dec 29 23:12:02 03bzhou * r4921 10optware/trunk/make/classpath.mk: classpath: 0.91 -> 0.93 Dec 29 23:12:18 03bzhou * r4922 10optware/trunk/make/jamvm.mk: jamvm: 1.4.3 -> 1.4.4 Dec 29 23:25:46 Hi eno: I tried the manual boot strap and intial test, getting an error Dec 30 00:06:38 Hi, how does ipkg decide which feeds to check when an ipkg update is done? I am trying to test, eno's new feed .../feeds/optware/slugosbe/cross/unstable. Even though the config has only that one feed, update tries ..../cross/stable first and then unstable. Of course the former does not exist, and errors out. Any ideas? Dec 30 02:44:16 03bzhou * r4923 10optware/trunk/ (Makefile make/ntop.mk): ntop: stripped plugins/*.so, gcc4 cross compilation working on slugosbe **** ENDING LOGGING AT Sat Dec 30 02:59:58 2006