Daniel Klaffenbach dixit: >I've been using FreeWRT on my Asus WL-500gP for quite a while now and I was >wondering if someone is trying to get Linux 2.6 to work?
We had initial tries, but (aside from the Broadcom problem) there are (were?) stability issues. >The wl-500gP has a bcm4318 wireless NIC which should be supported by >the native kernel driver in 2.6.24 or later. Interesting. Do you by chance know how well OpenWrt fares with it? In theory, it would be nice to have Linux kernel 2.6 support… but then, FreeWRT’s focus used to be stability over features. Stability includes supporting the WL-500gPv2 with higher priority than a different kernel. If there were commercial interest in Linux kernel 2.6 support, people might add it (at least that is what I heard last time). >But a far more important question is if there are any patches for Samba 3 to >work with FreeWRT. Samba 2 is very outdated, buggy, has quite a few security >issues If you ask me… wait for Samba 4. The attitude of the Samba developers regarding bug reports for Samba 3 (at least towards BSD developers) was not something I’d like to see again. Then, there’s the Linux 2.4 on MIPS cache coherency problem (which, for example, prevents FUSE from ever working correctly – if it seems to work for you, that’s by chance). I don’t know if that influences it. Finally, there’s probably the cause that no developer uses Samba 3, and nobody has enough pressure to add it ☺ If you get someone to port it, fine… (but I suggest to retain the Samba 2 port). Regarding Windows® version compatibility: the only version I know that has issues with Samba 2 (running on MirBSD) is Windows® XP Home, but that one’s SMB/CIFS implementation is inherently buggy, and the fix is to use NFS or upgrade to the Professional version. According to MS. >Btw: selecting UTF-8 as default charset in FreeWRT's "make menuconfig" breaks >the samba compilation :( Interesting. That is something I might look into once our other project server (flyingfish) is back up. Thanks for the verbose bug report ;-) bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
