**** BEGIN LOGGING AT Sat Apr 22 09:59:56 2006 Apr 22 11:35:00 03repvik * r302 10/releases/slugos-3.6-beta/openembedded/packages/e2fsprogs/e2fsprogs_1.38.bb: e2fsprogs: Split off badblocks and add RDEPENDS Apr 22 11:35:35 03repvik * r303 10/releases/slugos-3.6-beta/openembedded/conf/distro/ (debianslug.conf openslug.conf): debianslug/openslug: Add badblocks to rootfs Apr 22 11:39:13 03repvik * r304 10/releases/slugos-3.6-beta/openembedded/packages/linux/ (ixp4xx-kernel/2.6.16/defconfig ixp4xx-kernel_2.6.16.bb): ixp4xx-kernel: Demodularize the kernel Apr 22 11:40:45 03repvik * r305 10/releases/slugos-3.6-beta/openembedded/conf/distro/ (debianslug.conf openslug.conf ucslugc.conf): debianslug/ucslugc/openslug: Remove modules that are now built-in Apr 22 11:57:04 reading the unslung readme, it sounds like it is a good idea to unsling to a dedicated usb flash drive, does this sound sensible? Apr 22 11:58:36 problem is, i wont then be able to add any other peripheral (e.g. webcam, other cool usb device) because port 2 will be taken Apr 22 11:59:16 how do most people have their slug set up? one big hd with your data, and unsling to that same hd? Apr 22 12:00:38 seems like if I have a dedicated usb stick to unsling to (and install packages to etc) then I can have an NTFS or FAT32 hd (which can be removed and used with a pc) Apr 22 12:19:13 iwo: that's the idea, yes. Apr 22 12:19:32 you can use a usb hub to add whatever else you want. Apr 22 12:44:54 the slug is a damn cool device :) ... Apr 22 12:45:22 when it arrived at my office, three more people saw it and are now going to buy one! Apr 22 12:46:36 presumably, i'm unlikely to need more than a 512mb memory stick to unsling to (+some extra packages), correct? Apr 22 12:47:15 since the slug can only run basic apps, is 256 enough even? Apr 22 12:48:03 basic? Apr 22 12:48:15 have you seen the package feed list lately ;-) Apr 22 12:48:20 okay, small in terms of package size :) Apr 22 12:48:34 i mean, i won't be installing photoshop :) Apr 22 12:48:58 or ms office Apr 22 12:51:01 256 should be enough, if you don't install development stuff and such Apr 22 12:51:15 ymmv though Apr 22 12:56:10 I'd put in 512, just to be safe. Apr 22 17:08:44 the nslu2 driver disc has a load of linux apps on it, anyone know why? Apr 22 17:18:29 linux *apps*? Apr 22 17:18:40 or just the sources for them? Apr 22 17:19:13 (ie, they've put the GPL sources on the CD finally?) Apr 22 17:25:30 iwo, do you mean in the "Modified Source" folder on the CD ? Apr 22 17:28:24 yeah. Apr 22 17:28:54 does this mean the software on the nslu2 is open source? Apr 22 17:29:42 parts of it, yes Apr 22 17:29:57 the NTFS module and the network modules are closed-source Apr 22 17:30:11 and everything pertaining to the webinterface, IIRC Apr 22 17:41:12 are kernel patches required for the nslu2, or can I just use the stock source? Apr 22 17:46:44 kernel patches are required Apr 22 17:47:35 we are getting as much as possible moved into mainstream, but it's not all there yet Apr 22 17:48:45 are there patches beyond what linksys has done, and if so, where can I find them? sorry, I'm having trouble finding this info on the wiki Apr 22 17:50:41 they are in cvs on sourceforge and in the openembedded tree Apr 22 17:51:06 okay, great. thanks Apr 22 17:52:10 np Apr 23 01:13:44 hello, anyone here? Apr 23 01:14:43 nslu2-nubee: given debian-sda1.bin how do I extract files from it and rebuild it with new ones? Apr 23 01:15:28 (A pointer do a web page with the right info would be perfect!) Apr 23 01:15:50 what exactly is /lib/libntpass.so.0 Apr 23 01:15:58 And more specifically, can it be deleted? Apr 23 01:26:00 bofh: I believe it is to generate lanmanager passwords for samba Apr 23 01:26:26 breed: #debonaras would be a better place to ask Apr 23 01:27:29 actually, I'm debian-sda1.bin is just an example. I'm wondering how the firmware files are generated in general. Apr 23 01:28:09 slugtool Apr 23 01:28:38 excellent! thanx Apr 23 01:28:57 oh, sorry - I meant to say slugimage Apr 23 01:29:12 http://cvs.sourceforge.net/viewcvs.py/nslu/slugimage/ Apr 23 01:29:44 what is the difference between the two? Apr 23 01:30:18 slugtool was the very old original tool. Fully replaced by slugimage over a year ago Apr 23 01:30:46 excellent. thanx for the help. exactly what I was looking for. Apr 23 01:34:41 What is the filesystem usually used for the initrd. It doesn't look like a gzipped image. Apr 23 01:40:45 rwhitby: I figured it had something to do with LM/NTLM, only thing is, I removed samba via ipkg awhile ago, so why is it still there? Apr 23 01:42:56 dunno - what firmware are you running for a start? Apr 23 01:44:57 openslug, and it wasn't there to begin with, I just checked the /initrd Apr 23 01:47:44 probably a package that samba depends on and got loaded Apr 23 01:51:31 * bofh queries Apr 23 01:52:34 Nope, not in the list Apr 23 01:52:40 I'll just delete it Apr 23 01:53:06 Thing is, I'm really paranoid as my slug has over 200 days uptime and is a stratum-2 ntp serv Apr 23 03:10:44 Hmm - I need zmodem on the wl500g optware so I can load a new image onto my nas100d ... Apr 23 03:15:50 Time to port lrzsz to optware Apr 23 03:18:36 03bzhou * 10unslung/make/cherokee.mk: upstream upgrade to 0.5.3 Apr 23 03:26:32 03rwhitby * 10unslung/Makefile: Added lrzsz. Apr 23 03:26:42 03rwhitby * 10unslung/make/lrzsz.mk: Initial version. Apr 23 03:26:53 let's see what it builds on ... Apr 23 05:23:23 sweet - it seems to work Apr 23 05:23:43 (can use minicom and lrzsz to upload via ymodem to nas100d redboot Apr 23 05:27:03 hmm - spoke too soon Apr 23 05:54:45 RedBoot> load -m ymodem Apr 23 05:54:45 Unrecognized image type: 0x85190520 Apr 23 05:54:52 wonder if it's an endian thing. Apr 23 05:55:23 load -r ? Apr 23 05:57:40 yeah, that was it Apr 23 05:57:56 had to change the paths in minicom to /opt/bin too Apr 23 06:12:33 nice to be able to reflash the lude wirelessly from the wl500gx Apr 23 06:12:50 NAiL: testing the lastest SlugOS on the nas100d Apr 23 06:17:29 03rwhitby * 10unslung/make/lrzsz.mk: Cleaned up superfluous text. Apr 23 06:20:20 is there a howto or something for compiling a kernel for the NSLU2? Apr 23 06:51:11 tsowell: kernel module, cvs repo, sf.net/projects/nslu Apr 23 06:52:34 rwhitby: should the patches for 2.6.15 work fine? Apr 23 06:52:49 dunno, we're at 2.6.16 Apr 23 06:53:19 all right. that might explain my troubles Apr 23 07:13:21 03rwhitby * 10kernel/2.6.16/defconfig: Put the required modules back in the kernel. Apr 23 08:45:02 03rwhitby * 10kernel/2.6.16/96-nas100d-leds.patch: Fixed the name of the disk led on the nas100d. **** ENDING LOGGING AT Sun Apr 23 09:59:56 2006