**** BEGIN LOGGING AT Sun Dec 10 02:59:58 2006 Dec 10 03:25:32 Hey All Dec 10 03:26:39 03bzhou * r4650 10optware/trunk/make/tar.mk: tar: 1.16 -> 1.16.1 Dec 10 03:39:58 03bzhou * r4651 10optware/trunk/make/sane-backends.mk: sane-backends: make sure _SITE is working Dec 10 07:08:33 03bzhou * r4652 10optware/trunk/make/whois.mk: whois: 4.7.19 -> 4.7.20 Dec 10 11:17:40 03vidar * r4653 10optware/trunk/ (9 files in 2 dirs): kissdx: Adding kissdx package to repository. - See kissdx site for info: http://kissdx.vidartysse.net/ Dec 10 11:24:09 Hi all. I have just added a new package "kissdx" to svn. I have not yet added it to the Makefile as ready for testing. According to eno it builds on all platforms but wl500g, and I have now made it build on wl500g too. Should I proceed and add it to CROSS_PACKAGES_READY_FOR_TESTING ? Dec 10 11:24:55 FYI: The nick vidar" was already taken so I am now "vtysse". Dec 10 11:27:30 vtysse: høres fornuftig ut ;) Dec 10 11:29:13 NAiL: OK, Øyvind. I will take that as an authoritative yes :-) Dec 10 11:32:33 03vidar * r4654 10optware/trunk/Makefile: kissdx: Made package ready for testing. Dec 10 11:37:29 nice :) Dec 10 12:00:41 NAiL: I see that you changed http://www.nslu2-linux.org/wiki/Optware/PackagingBestPractices to remove the Package Registration section. However there is still a reference to that section on http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware Dec 10 12:01:21 NAiL: So which is correct? Is it no longer a requirement for a package maintainer to be registered in the bug tracking system? Dec 10 12:40:34 we've changed bug tracking system Dec 10 12:40:45 we're now using trac Dec 10 12:41:30 trac.nslu2-linux.org, it uses the cert you have for svn access Dec 10 12:41:36 * NAiL rephrases Dec 10 12:41:50 https://trac.nslu2-linux.org/, use the cert you got for svn access ;) Dec 10 13:04:59 hmm, I don't think you need to be manually added to trac Dec 10 13:05:07 Just read the last page you linked Dec 10 13:08:44 I'd imagine rwhitby would do it in any case. Dec 10 13:25:43 OK, I've subscribed to RSS feed for tickets. That way I'll get notified if something is reported. Not many tickets in there so I can cope with the traffic :-) Dec 10 13:26:45 Still the sentence "See PackagingBestPractices, section on "Package registration" for how to do this." should be removed or replaced with a link to trac. Dec 10 13:28:25 feel free to correct it Dec 10 13:28:40 OK Dec 10 13:35:00 Hmm, https://trac.nslu2-linux.org/ is not working for me: Secure connection: fatal error (40) from server. Dec 10 13:35:20 Works fine with http though. Dec 10 14:38:38 Hmm... Has anyone managed to connect to an fsg-3 with wireless from a mac? Dec 10 14:41:21 I can connect to it from windows and linux, but my gf's powerbook can't connect at all Dec 10 15:31:28 or... to put it another way Dec 10 15:31:58 has anyone connected a mac to any linux-based wireless access point with WEP encryption? Dec 10 17:26:29 03bzhou * r4655 10optware/trunk/Makefile: promoted kissdx Dec 10 21:28:46 if i upgrade from a debootstrapped slugos to Debian/NSLU2, what happens to the kenel modules installed via ipkg's? do i need to remove them or should i just ignore them? Dec 10 22:20:46 03vidar * r4656 10optware/trunk/make/kissdx.mk: kissdx: Config step failed (unexpected end of file) Dec 10 23:01:55 anyone know what kind of disk is in the FSG-3? (PATA or SATA?) Dec 10 23:02:40 * NAiL suddenly remembers that question doesn't make sense... it's shipped with both... Dec 10 23:05:47 rwhitby: does your fsg-3 have a pata or sata disk? Dec 10 23:05:59 * NAiL presumes his has the same config Dec 10 23:06:03 internal is PATA I believe Dec 10 23:06:13 ok Dec 10 23:06:16 did you check the internal pictures? Dec 10 23:06:39 won't really help, since (according to freecom) it's shipped with both Dec 10 23:07:18 mine has internal PATA and external eSATA - is that what they mean? Dec 10 23:07:47 no, the internal disk can apparently be either Dec 10 23:08:13 depending on prices, apparently Dec 10 23:09:12 interesting. which do you have? Dec 10 23:09:30 I haven't cracked it open Dec 10 23:09:40 I decided to wait with that until I got the serial cable Dec 10 23:23:32 03rwhitby * r76 10debian/trunk/patches/kernel/2.6.19/ (3 files): 2.6.19 cleanup patch now in Debian kernel repo Dec 11 00:05:00 03bzhou * r4657 10optware/trunk/make/py-sqlalchemy.mk: py-sqlalchemy: 0.3.1 -> 0.3.2; added py25 subpackage Dec 11 00:11:46 03bzhou * r4658 10optware/trunk/make/privoxy.mk: privoxy: 3.0.5b -> 3.0.6 Dec 11 01:19:54 * rwhitby installs linux-2.6.19-1 .deb on the nas100d Dec 11 01:20:10 (including IDE modules) Dec 11 01:20:26 dumfrac: ping Dec 11 01:28:57 rwhitby: hi, can't chat now - I'm needed in the kitchen to help my wife make dinner Dec 11 01:30:41 dumfrac: np Dec 11 01:31:10 dumfrac: I wanted to pick your brains about how to add IDE modules to the initramfs for the nas100d debian port Dec 11 01:37:36 03rwhitby * r77 10debian/trunk/ (Makefile patches/kernel/2.6.19/config.ixp4xx.patch): 2.6.19 now builds Dec 11 02:54:56 rwhitby: what would you like to know (I hope that I can help) Dec 11 02:55:52 dumfrac: dunno yet :-) Dec 11 02:56:00 :-) Dec 11 02:56:23 I've got new pata_artop and libata modules, and I need to get them loaded in a new initramfs so that the nas100d can boot from the internal IDE hard disk Dec 11 02:56:32 Any pointers? Dec 11 02:56:52 (and I want to do it in the way that it will eventually be merged into debian mainline) Dec 11 02:57:15 I would start by adding the modules to the initramfs using in the procedure oultined in the wiki Dec 11 02:57:33 Doh! I forgot about that bit on the page. Dec 11 02:57:34 then, I'm not sure if they would be loaded automagically by udev Dec 11 02:57:51 but at least you would have then available Dec 11 02:58:05 :-) Dec 11 02:59:25 oh, I see - that's the manual method. Yeah, I could do that, but I want to know how to get mkinitramfs-kpkg to do it Dec 11 02:59:37 or update-initramfs **** ENDING LOGGING AT Mon Dec 11 02:59:57 2006