June 17, 2010 4:41 PM

Hi goodwill,

a few quick answers.

1. This is the default behavior, which probably most users want. But can be cvhanged through "Use Custom Configuration", for example:

[global]
server string = Kong
workgroup = Secure
interfaces = br*
bind interfaces only = Yes
map to guest = Bad User
smb passwd file = /var/samba/smbpasswd
private dir = /var/samba
passdb backend = smbpasswd
log file = /var/smbd.log
max log size = 1000
printing = none
load printers = No
usershare allow guests = Yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = yes
write raw = yes
oplocks = yes
max xmit = 65535
dead time = 15
getwd cache = yes
lpq cache = 30


[Admin]
comment = Restricted Area
path = /jffs/
read only = No
guest ok = No
valid users = joe steve

[Public]
comment = Public Share
path = /jffs/pathxyz
read only = No
guest ok = Yes
guest only = Yes

2. Printer sharing needs a printer deamon, which is not directly included in firmware yet. They have included it upstream this week, so it does not have to be installed through optware anymore. Once I update my build I'll include it.

3. This looks like going to be a pain. I have searched through the Tuxera (developer of ntfs-3g) forums. It is a known problem, ntfs-3g is being posix compatible and behaving like ext3, ntfs however does some converting between localtime and utc since it has to be down/up compatible. Now to fix this, samba would have to be patched in order to respect that if it reads/writes from ntfs volumes. Therefore I doubt this will be fixed soon. By the way ntfs-3g opensource app has horrible performance so it is rather a emergency solution. It is rather recommended to use ext3 or fat since they provide 3x faster read/writes to the share.

4. I did not include an option for it, since there is no ntfs module to load, like for the other fs modules, since it is a userspace app.