Changes between Version 4 and Version 5 of Ticket #7
- Timestamp:
- 12/23/09 10:00:34 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7 – Description
v4 v5 1 Windows clients can't mount theserver since we can't tell them what port to use (sigh). So maybe we should always do a reverse mount? (server mounts shares from the client)[[BR]]1 Windows clients can't mount a remote tunneled server since we can't tell them what port to use (sigh). So maybe we should always do a reverse mount? (server mounts shares from the client)[[BR]] 2 2 We need to find out the list of shares (pysamba?) and allow the user to configure what is mounted (read-only, password,...)[[BR]] 3 3 [[BR]] … … 11 11 12 12 We should also deal with non-tunneled setups nicely: simply connect to SMB on client or server directly. This weighs in favour of supporting client-mounts-server option. 13 14 [[BR]] 15 16 We can figure out what shares are available with (needs a bit of magic parsing... sigh): 17 {{{ 18 smbclient -U guest -N -L localhost 19 }}} 20 or 21 {{{ 22 smbclient -A /path/to/auth-file -L localhost 23 }}} 24 25 26 Maybe we should make the mounting more filesytem agnostic (using modules) to handle sshfs,nfs,glusterfs,..