As FDR said when the American nation was in the throws of a previous crisis (surely somehow also Samba related).  "The only thing we have to fear is fear itself."



It is only with a strong will and a cast iron constitution can one leader rise from the ashes of shattered dreams to rescue a community gripped with fears over cross platform file sharing (similiar to the situation of the US in the 1930s).



Such leaders have emerged in CRWeb and Fireether (real names withheld to protect the innocent).  In CRWeb's own humble description:

"Fireether and I have been working with samba.

Details:

2 methods of mounting samba sahres:

1.) smbfs kernel module (800K),smbmount(800k), smbumount(6.8k),smbmnt(9k) total 1614.8K

2.) cifs kernel module (2000K),mount.cifs(20K),umount.cifs(6K) total 2026K

flash space is limited. fireether wants to use cifs, i say use smbfs.This is for mounting ONLY.

the smbclient, and client shared library add another 2M. CIFS does have a lot more features and is totally backwards compat with smb, however, smb has a better footprint size, and all the basic functionality users should "need"

Right now the smb.patch that I have posted enables BOTH kernel modules. and samba packages that I packed have BOTH smb and cifs.

details of install and usage can be found at: http://www.limesg.com/osd/samba/

Kernel Patch: http://www.limesg.com/osd/samba/smb.patch

Mounting: http://www.limesg.com/osd/samba/smb-utils.txt - Document on the samba-*-client package

http://www.limesg.com/osd/samba/samba-3.0-OSD-client.tar.bz2 the samba client package for mounting.

Full Samba:

http://www.limesg.com/osd/samba/samba-3.0.23c-armlinux-OSD.tar.bz2 - the FULL samba suite, server, client, libraries, docs, even webinterface swat for configuration."

Anyway, the point is we're now one step closer to actually being able to save and play files from a *gasp* windows machine!  Bless you crweb for your overwhelming courage in the face of enormous adversity!

Any other hackers of great fortitude and courage, please join this cause on the mailing list discussion

and Bug #723