**** BEGIN LOGGING AT Thu Sep 15 02:59:56 2005 Sep 15 08:36:39 Does anyone know the state of unslung 5.x based on the Linksys V2.3R63 Firmware? Sep 15 08:37:19 the first release of unslung based on R63 firmware will be 6.x Sep 15 08:37:32 I can speak authoritatively on that.... ;) Sep 15 08:41:37 Any Idea about how long one might have to wait to lay hands on that Firmware? Sep 15 08:43:00 20,000 lines to clean ^M's because some moro... err person at linksys or sercomm touched the source with a MSDOS machine Sep 15 08:56:45 thats all it takes to get the Firmware ready for primetime? why not just use a script to clean the source? Sep 15 08:59:07 no, that's one of the problems - we have a R24<->R29 patch that is made by comparing diffs in the source code Sep 15 08:59:33 so we have to create a R29<->R63 patch by comparing diffs in the source code Sep 15 09:00:04 but the diffs show on all 20,0000 source code lines because of the ^M's Sep 15 09:00:59 so *each* source file must be compared - this time, it's not a trivial "run diff" and get changes.... Sep 15 09:03:15 where exactly is the problem to run a script over r63 to clean the source of the ^M's? after that one can proceed like normal Sep 15 09:04:01 ok, let's step back... have you downloaded the source? Sep 15 09:06:12 yes i have the source Sep 15 09:06:38 and the R29 source? Sep 15 09:06:42 no Sep 15 09:07:10 feel free to contribute :) Sep 15 09:08:10 you can check out the R24->R29 patch, and then after doing the diffs of R29->R63, make a R29- that still doesnt answer the question about a script to clean r63, where is the problem? the work it takes to write the script? Sep 15 09:11:02 ok... the R29 source is 70. Sep 15 09:11:28 .. is 70.8mb, how big is the R63 source? Sep 15 09:11:35 170mb+? Sep 15 09:15:23 uncompressed 362mb of Source Sep 15 09:25:50 r29 and the size of the code is irrelevant for a script to clean only r63, so where is the showstopper? Sep 15 09:27:09 so feel free to do it and submit back the patch when you get finished Sep 15 09:32:50 im working on alive projects only, and this one is dead as i understand you Sep 15 09:34:11 thanks for your explanation anyway Sep 15 09:38:39 thanks for your contribution... Sep 15 09:41:25 I just love when ppl who evidently have all the time in the world complain about someone else - who may not have much time at all - not doing something *for* them Sep 15 09:44:55 i did not complain, i just wanted to understand the problem and you did not said that not the skill but the time is the problem until now Sep 15 09:53:11 I'm sorry if I did not get that across - but yes, time is the biggest factor Sep 15 09:56:36 did someone ask linksys for a clean source? (easiest solution first) Sep 15 09:58:47 I don't know, but Linksys doesn't exactly have a stellar reputation re: GPL... everytime that I've asked about the source, I've gotten the "it'll be there when it's there" Sep 15 09:59:32 and since they always seems to be fighting with the EFF - they're not likely to change based on a few requests... Sep 15 10:02:47 thx ... need to go now ... bye Sep 15 10:42:29 hi, trying to get nfs-utils running under openslug, but I cannot get nfsd to run\ Sep 15 10:42:33 anyone an idea? Sep 15 10:44:33 ok got it already, tried to start it wrong... Sep 15 10:55:02 forgot to insmod exportfs and nfsd Sep 15 15:05:50 sorry to bug you people here :), im pretty new to the slug. Im wondering what the tempfs is mounted to /media/ram ? currently using the openslug 2.5 release Sep 15 17:14:23 Any one here? Sep 15 17:15:07 Me Sep 15 17:15:54 :-) I expected more chat in this channel. Sep 15 17:16:40 there is sometimes... Sep 15 17:26:21 do you know how to format bb files for installing packages on openslug. Sep 15 17:28:43 ByronT maybe your man to help Sep 15 17:29:56 What are the busy hours of this channel? Sep 15 17:30:39 Usually, anyways? Sep 15 17:31:26 hard to say; always try #nslu2-linux few more people. Sep 15 17:32:02 last two hours nothings moved. really **** ENDING LOGGING AT Fri Sep 16 02:59:56 2005