**** BEGIN LOGGING AT Thu Dec 28 02:59:57 2006 Dec 28 03:35:47 03rwhitby * r85 10slugimage/trunk/ (10 files in 6 dirs): Added tests Dec 28 03:37:21 03rwhitby * r86 10slugimage/trunk/Makefile: Added clean target Dec 28 04:06:01 03bzhou * r4880 10optware/trunk/ (Makefile make/strace.mk): strace: made to work on slugosbe Dec 28 06:16:46 03rwhitby * r87 10slugimage/trunk/tests/ (10 files in 4 dirs): Added some more common tests Dec 28 06:23:16 03rwhitby * r88 10slugimage/trunk/tests/ (9 files in 3 dirs): Added ethaddr as a separate test Dec 28 06:30:07 03osas * r4881 10optware/trunk/ (4 files in 2 dirs): asterisk14-gui: svn rev 193 -> 195 + System Info html page fixes Dec 28 06:47:20 03rwhitby * r89 10slugimage/trunk/tests/ (12 files in 4 dirs): Added large ramdisk regression test Dec 28 06:47:57 03rwhitby * r90 10slugimage/trunk/slugimage: Check for running out of space in the last variable size partition Dec 28 07:41:47 03rwhitby * r91 10slugimage/trunk/tests/ (19 files in 5 dirs): Added more debian tests (including real sizes of kernel and ramdisk). Also added a slugos large flashdisk test. Dec 28 09:45:14 03rwhitby * r92 10slugimage/trunk/slugimage: Reduced the size of the microcode header, to make it easy to distinguish the partition size from the data size in debug mode. Adjusted the attributes for created data to match. Dec 28 09:47:25 03rwhitby * r93 10slugimage/trunk/tests/apex/ (standard.expected standard.test): Apex standard test Dec 28 11:59:47 03oleo * r4882 10optware/trunk/ (make/mc.mk sources/mc/static-declaration.patch): mc: static declaration patch for gcc4.x Dec 28 12:13:20 03oleo * r4883 10optware/trunk/ (3 files in 2 dirs): minicom: patch window.c for gcc-4.x Dec 28 12:28:43 03oleo * r4884 10optware/trunk/ (make/xvid.mk sources/xvid/ sources/xvid/configure.in.patch): xvid: cvs update - remove deprecated -freduce-all-givs optimization Dec 28 12:43:59 03oleo * r4885 10optware/trunk/ (make/hpijs.mk sources/hpijs/): hpijs: 1.7.1->2.1.4 - cups search patched Dec 28 13:15:59 does anybody know what this is: Dec 28 13:16:02 ERROR: Error in executing: /Users/openslug/local/downloads/openslug/openembedded/packages/quilt/quilt-native_0.45.bb Dec 28 13:16:02 ERROR: Exception:exceptions.UnboundLocalError Message:local variable 'md5data' referenced before assignment Dec 28 13:31:05 03oleo * r4886 10optware/trunk/ (7 files in 2 dirs): modutils: several patches for gcc-4.x Dec 28 13:37:23 03oleo * r4887 10optware/trunk/ (make/indent.mk sources/indent/ sources/indent/output.c.path): indent: static declaration patch Dec 28 14:27:39 03oleo * r4888 10optware/trunk/sources/hpijs/configure.patch: hpijs: CUPS configure.patch for /opt location Dec 28 14:31:31 03oleo * r4889 10optware/trunk/ (3 files in 2 dirs): imagemagick: 6.3.0->6.3.1 - uClibc patches Dec 28 14:36:10 03oleo * r4890 10optware/trunk/make/inetutils.mk: inetutils: 1.4.2->1.5 Dec 28 14:39:46 03oleo * r4891 10optware/trunk/make/mdadm.mk: mdadm: 1.8.0->2.6 Dec 28 15:15:24 03oleo * r4892 10optware/trunk/ (2 files in 2 dirs): cyrus-imapd: patch for gcc-4.x Dec 28 15:31:16 03oleo * r4893 10optware/trunk/make/ircd-hybrid.mk: ircd-hybrid: 7.0.3->7.2.2 Dec 28 15:31:56 That ends 4.1.1 uClibc pathing for buildroot :) Dec 28 17:05:22 03bzhou * r4894 10optware/trunk/Makefile: promoted hpijs indent inetutils mdadm & minicom for slugosbe after oleo's gcc4 fix Dec 28 17:13:58 03bzhou * r4895 10optware/trunk/ (Makefile make/picocom.mk): promoted ircd-hybrid & picocom for slugosbe Dec 28 17:18:39 03bzhou * r4896 10optware/trunk/Makefile: added ipkg-opt to slugosbe for manual bootstrap Dec 28 17:26:07 <[g2]> oleo can you talk about what you mean by that ends patching for buildroot ? Dec 28 17:30:13 03bzhou * r4897 10optware/trunk/make/ipkg-opt.mk: ipkg-opt: added slugosbe Dec 28 17:37:38 03bzhou * r4898 10optware/trunk/ (Makefile make/clearsilver.mk): clearsilver: explicit --with-python to pass gcc4 cross compilation Dec 28 17:42:05 [g2]: That meant that I've patched all the packages that failed to build with buildroot-4.1.1. Dec 28 17:42:32 <[g2]> oleo that's for optware correct ? Dec 28 17:42:39 Now it's time to commit buildroot-4.1.1 itself. Dec 28 17:42:41 <[g2]> THX ! btw :) Dec 28 17:44:14 Currently only mipsel router firmwares are supported in Optware (oleg,ddwrt,xwrt,openwrt,...) Dec 28 17:44:44 biyh buildroot toolchain, of course. Dec 28 17:45:04 s/bihy/With/ Dec 28 17:46:19 it just happens that optware/slugosbe also uses gcc 4.1.1, your changes also benefit slugosbe feed, thx Dec 28 17:52:54 03bzhou * r4899 10optware/trunk/make/inetutils.mk: inetutils: keep wl500g back at 1.4.2 Dec 28 17:58:20 eno which binutils use slugosbe? I am using 2.17.50.0.8 Dec 28 17:58:43 <[g2]> oleo eno I'm actually interested in build openwrt for the ixp42x Dec 28 17:59:00 <[g2]> I think rwhitby commited something, but it may have just been the kernel build Dec 28 17:59:15 <[g2]> rwhitby ping Dec 28 17:59:30 * [g2] guesses he's sleeping Dec 28 18:00:40 [g2] openwrt on nslu2 or some other hardware? Dec 28 18:01:01 <[g2]> oleo for the nslu2 with a wireless adapter Dec 28 18:01:28 * [g2] has minipci cards, but that's just a kernel driver tweak Dec 28 18:06:15 oleo: dunno much about toolchain, optware/slugosbe simply uses optware/../openslug/tmp/cross for now Dec 28 18:06:36 what is the easiest way to check binutils version? Dec 28 18:07:05 <[g2]> ld -v Dec 28 18:09:28 03bzhou * r4900 10optware/trunk/ (Makefile make/tcl.mk): promoted tcl and xvid for optware/slugosbe Dec 28 18:09:58 Hi eno! Dec 28 18:13:49 eno, oleo: I have prepared a new disk with slugos/be ready to start installing optware with the new pkg feed :) When the expected earliest time the feed will be available ? Dec 28 18:14:16 it is available already, just the bootstrap is not ready Dec 28 18:15:00 eno: when do you think the bootstrap will be ready? Dec 28 18:15:41 wait another hour or so, ipkg-opt.ipk will be in the feed http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/unstable/ Dec 28 18:16:56 then you can manually bootstrap, pretty much follow http://bzimage.blogspot.com/2006/11/optware-on-slugosbe.html Dec 28 18:16:59 eno: thanks! Dec 28 18:18:12 use ipkg-opt.ipk from slugosbe feed instead of fsg3/cross/unstable/ipkg Dec 28 18:19:18 and replace nslu2 with slugosbe in .conf Dec 28 18:19:56 what is the command to get a pkg from a specific feed? I have done only: ipkg update; ipkg install this_pkg; so far... Dec 28 18:21:02 right now, just use wget and tar for the first ipkg-opt.ipk. This is what i meant by "manual bootstrapping" Dec 28 18:21:52 once you have ipkg-opt files in the right place, all .conf setup correctly, do "ipkg update; ipkg install ..." as usual Dec 28 18:22:33 please understand that the bootstrapping method is not final, and will likely change to a script in the future Dec 28 18:23:38 $ ls -l nslu2/builds/*.ipk | wc -l Dec 28 18:23:38 696 Dec 28 18:23:47 $ ls -l slugosbe/builds/*.ipk | wc -l Dec 28 18:23:47 587 Dec 28 18:24:15 eno: It will be nice to have ipkg install ... for getting from the existing stream, and another command or link, such as optpkg install ... for the new one. That way one can select from either one. What do you think? Dec 28 18:24:58 <[g2]> eno are you around for 15-30 minutes ? Dec 28 18:25:08 i'm no expert on bootstrapping, it would be nice i agree Dec 28 18:25:16 [g2]: yes Dec 28 18:25:41 <[g2]> eno you do a ton of work on optware right ? Dec 28 18:25:47 [g2]: the only problem is my openslug at home is unreachable Dec 28 18:25:59 yes Dec 28 18:26:04 I think I will wait for the 'normal' install procedure; my *nix experience is limited :( Dec 28 18:26:25 <[g2]> eno I'd like to just talk overall strategy, you don't need access to any devices for me Dec 28 18:26:37 sure Dec 28 18:26:54 <[g2]> I haven't really used optware for like 2 years Dec 28 18:27:16 <[g2]> however, I'm thinking about doing an optware build for the ixp4xx platform Dec 28 18:27:38 for kernel and driver, slugos is definitely better Dec 28 18:28:17 <[g2]> eno I'm guessing that's for chacko Dec 28 18:29:22 [g2], how do you define the ixp4xx platform? Dec 28 18:29:34 eno: When I was experimenting with eno's procedure before, what I did was: the ipkg itself was installed in the /opt/ path, and I put a symbolic link optpkg to this /opt/ipkg. After that I could do either ipkg.. as normal, and optpkg... for the new stuff. Appears to have worked fine! Dec 28 18:29:55 <[g2]> eno IXP42x arches ( I haven't run 46x yet) Dec 28 18:30:43 [g2]: what about toolchain? BE vs LE, glibc vs uclibc? Dec 28 18:30:45 <[g2]> I think that includes the nslu2, dsm-g600, loft, nas100d, .... Dec 28 18:31:12 <[g2]> eno I'm thinking of starting with BE uclibc Dec 28 18:31:54 <[g2]> eno I don't know if you are aware of the Data Coherency versus Address Coherency issue regarding IXP4xx arches Dec 28 18:32:24 <[g2]> basically, I think we are running DC and if we switch to AC for the GPL ethernet driver we may be able to avoid the byte-swap tax Dec 28 18:32:25 existing optware platforms mostly are BE glibc, some mips uclibc Dec 28 18:32:30 <[g2]> but that's down the road Dec 28 18:32:56 * [g2] could start with BE glibc Dec 28 18:32:59 [g2]: i'm not aware of that Dec 28 18:33:15 During the unstable/testing phase, I prefer to try an optware pkg only when it is not in the unSlung stream, that way I can limit my risk... I have a somewhat production machine I wnat to bring the new one up... Dec 28 18:33:21 optware/slugosbe is BE glibc gcc4 Dec 28 18:33:56 <[g2]> eno nod. which glibc 2.3.5cvs ? Dec 28 18:34:24 sorry, I meant: 'only when the pkg is not in the current slugos/be stream' Dec 28 18:36:11 [g2]: since we borrow toolchain from openslug build, we use whatever openslug is using Dec 28 18:36:38 <[g2]> eno Ok Dec 28 18:37:33 on my build machine I have libc-2.3.90.so Dec 28 18:37:56 under openslug/tmp/cross/armeb-linux/lib/ Dec 28 18:39:48 see optware/Makefile UCLIBC_BROKEN_PACKAGES for the diff between glibc and uclibc Dec 28 20:31:29 hi (again) Dec 28 20:35:07 Hi mcsalty Dec 28 20:46:15 i was trying to config putty for x11:) but now i'm searching for an irc server, maybe someone has an idea what to do an how to use it? Dec 28 20:46:51 irc server for unSlung? Dec 28 20:48:43 yes, i know it's difficult and paranoid, but i've 3 projects working on, one of them is x11, and the other 2 are skypelike program and irc server Dec 28 20:51:58 you think it's possible to do that, the processor isn't "that" fast...? Dec 28 20:52:21 maybe the easiest way is to use ipkg list | grep irc Dec 28 20:52:56 or apt-cache search irc|more Dec 28 20:57:34 ok thank you, i'll try it Dec 28 21:04:46 [g2]: openwrt builds for nslu2 - but you need apex to load it. Dec 28 21:15:53 <[g2]> rwhitby I dl'ed the the master Makefile and was looking for openwrt in there, but didn't see anything Dec 28 21:16:31 <[g2]> I'm sure I can setup my partitioning and have RedBoot boot the image properly Dec 28 21:16:49 <[g2]> along with the loft specific kernel built Dec 28 21:17:05 rwhitby, [g2], howdy! Dec 28 21:17:06 [g2]: "make update" to get the latest Makefile Dec 28 21:17:23 rwhitby, you should be able to build openprotium from the current head. Dec 28 21:17:27 hey HopsNBarley Dec 28 21:17:34 HopsNBarley: should we put it in the Master Makefile? Dec 28 21:17:54 i haven't tried it on any other HW yet, so lets hold off on that (-; Dec 28 21:18:09 nah - that's the best way to test it. Dec 28 21:18:31 gimme a few days. Dec 28 21:18:37 ok Dec 28 21:18:44 we got a QNAP TS-201 yesterday, started working on that. Dec 28 21:19:03 <[g2]> HopsNBarley hey! Dec 28 21:19:12 hi [g2] Dec 28 21:19:38 HopsNBarley: How far have you gotten? Dec 28 21:20:01 [g2]: I've updated the autobuild script to automatically update the downloadable Makefile now Dec 28 21:20:28 we got the console up, took pictures, and measured the power usage. Dec 28 21:21:07 so, not too far yet. (-; Dec 28 21:21:14 hehe Dec 28 21:21:26 As I mentioned, I'm waiting for a serial port Dec 28 21:21:36 nice product. Dec 28 21:21:40 lets keep in touch. Dec 28 21:21:51 the 101 is. I haven't seen the 201 up close Dec 28 21:21:54 someone got some internal photos? Dec 28 21:22:06 HopsNBarley: can you update the nslu2-linux gallery? Dec 28 21:22:14 we'll have them on the openprotium wiki today/tomorrow. Dec 28 21:23:50 hmm Dec 28 21:23:52 <[g2]> rwhitby do you have stats on how many downloads of the OE meta-data there are ? Dec 28 21:23:58 I had some pics of the ts101 somewhere Dec 28 21:25:58 NAiL, my HW eng. in convinced all the 824x designs we see have a common ancestor. have an opinion? Dec 28 21:26:01 [g2]: nope Dec 28 21:26:15 HopsNBarley: probably a Freescale reference design Dec 28 21:26:21 sandpoint? Dec 28 21:26:46 yeah, that's it. Dec 28 21:26:47 the ts101 appears to use a sandpoint Dec 28 21:26:48 reference Dec 28 21:29:16 are there similarities between the ts101 and the ds101g? had read something about it but forgotten where Dec 28 21:29:45 Both are PPC Dec 28 21:29:54 IIRC, 16mb flash on both Dec 28 21:30:03 S-ATA Dec 28 21:30:06 GBLan Dec 28 21:30:15 ts101 is fanless though ;) Dec 28 21:30:38 how do they do it? how do they get the hd cool? Dec 28 21:30:56 the casing is solid metal Dec 28 21:31:11 and there's quite a bit of it Dec 28 21:31:19 mine never gets hot to the touch Dec 28 21:31:28 uncomfortably hot, that is Dec 28 21:31:43 Interesting how they attach the hd to the casing Dec 28 21:32:05 * NAiL goes to check Dec 28 21:34:22 the hdd is attached to an aluminum bracket-thingy that transfers the heat to the boty Dec 28 21:34:29 s/boty/body/ Dec 28 21:34:30 NAiL meant: the hdd is attached to an aluminum bracket-thingy that transfers the heat to the body Dec 28 21:34:39 Have thought about to replace one side of the case of my ds101g with thishttp://cgi.ebay.de/ALUMINIUM-KUHLKORPER-GOLD-40-x-x-116-x-143-mm_W0QQitemZ300058655665QQihZ020QQcategoryZ28908QQrdZ1QQcmdZViewItem Dec 28 21:35:06 s/thishttp/this http/ Dec 28 21:35:07 gda_ meant: Have thought about to replace one side of the case of my ds101g with this http://cgi.ebay.de/ALUMINIUM-KUHLKORPER-GOLD-40-x-x-116-x-143-mm_W0QQitemZ300058655665QQihZ020QQcategoryZ28908QQrdZ1QQcmdZViewItem Dec 28 21:35:19 wow Dec 28 21:35:23 that looks big Dec 28 21:35:39 the cpu has a heatsink that is connected to the casing via a thermal pad Dec 28 21:35:44 should be enough to get it cool Dec 28 21:36:59 IIRC the fan in the ds101g doesn't get air from the fan, so this shouldn't be a problem Dec 28 21:37:08 cpu? Dec 28 21:37:20 of course Dec 28 21:37:26 sorry Dec 28 21:37:44 np ;) Dec 28 21:38:17 or a 12cm fan in the side? Dec 28 21:38:27 bbl Dec 28 21:38:40 I'd think a large heatsink would do more than good enough Dec 28 21:42:24 The only noise my ts101 makes is when I put it directly on the floor. The vibrations from the hdd spinning are annoying. Putting some foam on the feet removes that noise and makes it virtually silent Dec 28 21:42:43 * NAiL uses a samsung spinpoint 250gb disk in it, so the noise is minimal Dec 28 21:55:26 NAiL: I use a 320gb WD, because it is silent and 5 °C cooler than the other, I can't hear it Dec 28 21:56:07 normally I prefer seagate Dec 28 21:59:25 <[g2]> gda_ what box do you have the 320gb WD in ? Dec 28 21:59:32 ds101g Dec 28 22:00:15 [g2] why? Dec 28 22:00:38 * [g2] has been running my gigabit server for a while now Dec 28 22:01:01 <[g2]> I'm nfs sharing/streaming audio/video Dec 28 22:01:29 <[g2]> I'm getting my audio/video setup ironed out Dec 28 22:02:07 <[g2]> I can SCP between boxes at 25-30MBs yes that's bytes Dec 28 22:04:32 that's much Dec 28 22:04:46 g2: Assume that is thru the ethernet connection? Dec 28 22:08:38 <[g2]> chacko yeah gige Dec 28 22:24:05 have asked synology whether they sell me a new side of the case for the ds101g to make experiments with passive cooling Dec 28 22:24:39 but I believe I am too naive Dec 28 22:25:44 NAiL: please publish a picture of this aluminium bracket-thingy Dec 28 22:30:08 <[g2]> gda_ aluminium bracket disk cooler ? Dec 28 22:30:14 yes Dec 28 22:47:57 An ipkg use question: how do I tell ipkg to use a specific feed? slugos/be: when i try 'ipkg -f list' it does not seem to work... Dec 28 22:50:04 Sorry, I meant: I made a source line like 'src/gz special http:/....' and put it in a file_c and did 'ipkg -f file_c list', and no joy :( Dec 28 23:01:11 hey guys... seems that latest d-i etch (LE) build uses APEX bootloader, right? Dec 28 23:02:56 So, it seems, for a FatSLUG, it should be relatively easy then, to modify APEX to recognize more than 32MB SDRAM Dec 28 23:04:25 it's easy, i did it before Dec 28 23:04:52 d-i etch running on a 128MB FatSlug now Dec 28 23:05:33 Sinclair73de: cool.... I'm looking for 256MB FatSlug (4 x 512Mb chips) Dec 28 23:06:02 but you sill MUST replace the redboot Dec 28 23:06:06 still Dec 28 23:06:39 Sinclair73de ah gotcha... makes sense b/c params are read at boottime. Better first confirm JTAG acccess Dec 28 23:07:36 Will that be easy to get this Apex working on slugbos/be too? Dec 28 23:07:36 i fatend 2 devices and flashed apex as primary bootloader with no problem Dec 28 23:08:32 in apex src there's a config-file for BE too Dec 28 23:08:32 Sinclair73de: that's what I'd like to eventually do - now that I have confirmed serial and unconfirmed JTAG interface Dec 28 23:08:48 D-I is LE but it prolly doesn't matter right? Dec 28 23:09:33 RobNC, here too: serial confirmed, jtag not confirmed, but having an jtag-adapter Dec 28 23:11:10 Sinclair73de: thks good to know it works... I've already backed up the entire flash, and if necessary, I could remove the flash and reprogram it at work (chip programmer) Dec 28 23:11:45 the good thing is now, by changing the second stage apex bootloader you can give the kernel the correct mem=128MB commandline Dec 28 23:12:45 at the bootstrap method i always changed the kernel default cmdline to get 128MB memory Dec 28 23:12:53 Since APEX loads after redboot for D-I install, it should be a matter of re-compiling APEX, trying to load that with redboot (to make sure it works), then finally write that to flash Dec 28 23:13:39 Sinclair73de is that all that is required, just command-line change? no compile-time? If so that would be much better... Dec 28 23:14:42 BRB wife calling :-) Dec 28 23:15:04 no, two things must be done für more than 64MB RAM: the first bootloader must set the sdram size/banks and the kernel must use the correct cmdline Dec 28 23:16:00 so i think you must still replace redboot for FatSlug Dec 28 23:29:54 Sinclair73de After doing a lot of research on this and conferring with rwhitby indeed I think you are right. I could recompile redboot but what's the point if I already have a serial console... might has well use APEX since it supports command-line args. Surely, the memory config must be part of some settings in the bootloader (bit width, bank size, CAS/RAS, LE/BE mode, etc.) Dec 28 23:31:29 no good info: dma error when copy large data Dec 28 23:32:04 http://pastebin.com/846778 Dec 28 23:32:09 that is irritating... so it seems there is no boot loader that does extensive memory "bit banging" eh? Dec 28 23:38:42 oh... possible my usb-stick is dead Dec 28 23:39:26 THat's always better than bad soldering or NSLU2 board problem :-) Dec 28 23:40:13 yes... but doing d-i again.... :-( Dec 28 23:42:52 D-I yes it takes forever for some reason... think it's the mirror site speed Dec 28 23:43:35 hmmm Dec 28 23:44:07 yeah the D-I instructions aren't clear or up-to-date for the latest etch install Dec 28 23:44:52 possible too hot for my usb-stick inside the slug see: http://stposch2.dyndns.info/temp/IMG_1108.JPG Dec 28 23:45:04 outside its running again Dec 28 23:45:08 but the good thing is it's a lot smoother than my previous install circa March whereby most of the kernel modules weren't set up right, and apt wasn't set up correctly either. It's come a long way and works great. Just wish I could manually select which packages I want and don't want. Dec 28 23:45:16 but soldering is good Dec 28 23:46:04 what is that board above the memory? Dec 28 23:46:33 serial Dec 28 23:46:43 with max3232 Dec 28 23:47:24 Ah I did mine with superglue above the memory (double-stacked) with flipping the chip over and using 30ga wire or thicker for Vcc/Vss Dec 28 23:48:07 don't have pics b/c using it right now but should take some pics next time Dec 28 23:48:49 green/white/blk/red = JTAG? Dec 28 23:49:10 scsi 0:0:0:0: rejecting I/O to dead device Dec 28 23:49:15 my stick ... :-( Dec 28 23:49:48 I glued a 4x2 header onto back of my SLUG for JTAG - used same pinout as WRT54G JTAG (only uses 4 signals and ground) Dec 28 23:50:06 no... wires for the usb-stick when placed inside the SLUG Dec 28 23:50:31 Oh that stinks... time to unwrap tape. So you're using one of the three unused USB ports on the backside? Dec 28 23:50:41 now the stick is connected normaly, and still dead Dec 28 23:50:43 yes Dec 28 23:51:10 ah gotcha... those flash devices won't last forever (read/write cycles) Dec 28 23:51:35 not so old, but cheap Dec 28 23:52:54 yeah true... I'd be afraid of a permanent mod like that. Just using seagate HDDs with USB2 cases now. Would be nice to use extra USB ports for diskless operation, but not using it for that now Dec 28 23:54:11 It's too bad there isn't software to determine if all "free" sectors (swapped out when bad sectors are found by microcontroller) are used. Thus, the useful life would be over at that point. Dec 28 23:55:23 this is the serial board from top http://stposch2.dyndns.info/temp/IMG_0911.JPG Dec 28 23:56:12 I was too poor to pay for that, and had some scrap boards at work that I used. Max3202 is what I used Dec 28 23:56:40 my idea was to use the slug with system on internal stick an an usb-hdd for large data-space Dec 28 23:57:27 the chip was a sample from maxim and the board is selfmade you see Dec 28 23:57:52 is there an advantage of that over USB-HDD for large user-data? Other than power and noise savings... Dec 28 23:58:48 more portable... sometimes i what use these Slug for internet radio in outher rooms here Dec 29 00:00:08 oh I gotcha... Dec 29 00:00:41 but... no way... must install to hdd again Dec 29 00:00:58 this is true. How about 2.5" laptop HDD Dec 29 00:01:20 most can be USB powered Dec 29 00:16:19 i have too slugs and 2 old laptop HDD's (3GB and 5GB) Dec 29 00:16:27 too = 2 Dec 29 00:20:11 robnc: I use 2.5" HDD exclusively here with a couple of slugs, one unslung, the other slugos/be. I have a couple of spare ones which I do a full backup to. They work fine, some people say the life will be limited. Dec 29 00:21:20 You can use those old HDD as well, most of the older ones will easily be usb powered, many new ones need additional power, especially during the startup Dec 29 00:25:37 hmmm... i found, some hdd's are too slow with init , when using apex the slug boots faster than the hdd inits, and then boot fails Dec 29 00:26:48 One way to get around that is to get the hdd powered up first, and then start the slug. Dec 29 00:28:00 I have those usb cables, which have two usb connectors at one end, so the second one is used for addtiional power. Dec 29 00:29:23 On my slugos/be, I can plug in the disk (already powered up) into DISK1 slot, soon afer I have started the powerup of the slug. Dec 29 00:32:04 no good news... system hangs when copy large data Dec 29 00:35:47 ok, must retry it without the stick... tomorrow Dec 29 00:36:27 now sleeping... ;-) ist 2:00AM local time Dec 29 00:36:34 bye bye Dec 29 00:49:22 oops I was away... ttyl Dec 29 01:09:41 03rwhitby * r94 10slugimage/trunk/ (4 files in 3 dirs): Added apex small-kernel test (which currently fails), and the man page written by Joey Hess. Dec 29 01:12:32 * Chacko-away is now away - Reason : for a while Dec 29 01:15:58 Chacko-away: away status is better shown by the built-in support (i.e. see they people who are greyed out in the user list?) then it doesn't cause message traffic in the channel (which makes people look in the channel to see what is being discussed, and then they are irritated cause it's just a useless away message) Dec 29 02:04:36 <[g2]> rwhitby optware looks like it's building crosstool and the old 2.4.22 kernel Dec 29 02:07:48 [g2]: that's correct, for the nslu2 target (which is compatible with stock firmware) Dec 29 02:08:12 for slugosbe target, it uses the latest slugos cross compiler built by OE Dec 29 02:36:43 03rwhitby * r95 10slugimage/trunk/ (slugimage tests/apex/small-kernel.expected): Fixed the apex small kernel bug, and cleaned up the partition allocation code a bit (now that I have a regression test suite in place). Dec 29 02:44:50 03rwhitby * r96 10slugimage/trunk/tests/runtests: Clean up the text executor. Dec 29 02:47:17 03rwhitby * r97 10slugimage/trunk/tests/ (10 files in 4 dirs): Test files actually require bash. Dec 29 02:54:14 03rwhitby * r98 10slugimage/trunk/tests/ (11 files in 4 dirs): Actually, the tests just needed a portable way of creating a temporary file, instead of calling the Debian tempfile utility. Dec 29 02:55:33 03rwhitby * r99 10slugimage/trunk/tests/do-test: do-test also needed a portable way of creating a temporary file, instead of calling the Debian tempfile utility. **** ENDING LOGGING AT Fri Dec 29 02:59:59 2006