summaryrefslogtreecommitdiff
path: root/examples/libsmbclient/smbwrapper/README
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2012-02-03 15:06:48 +1100
committerAndrew Bartlett <abartlet@samba.org>2012-02-09 01:58:24 +0100
commit4328f3ccf37d9a1baadbc55f658902e3b16ff125 (patch)
tree203f4238cd13e283b423ee97df6ce2714298fd7f /examples/libsmbclient/smbwrapper/README
parentb93326b9689d0ad935eed35f7cf5201ad04ac1ff (diff)
downloadsamba-4328f3ccf37d9a1baadbc55f658902e3b16ff125.tar.gz
samba-4328f3ccf37d9a1baadbc55f658902e3b16ff125.tar.bz2
samba-4328f3ccf37d9a1baadbc55f658902e3b16ff125.zip
smbwrapper: Remove smbwrapper
There are now many better ways to access a remote SMB filesystem, which do not rely on LD_PRELOAD and the associated dangers. FUSE, gvfs and the CIFS VFS are all much better options which do not require knowing every possible libc entry point that can deal with a file descriptor. As an example of the maintainence that would be required to keep this going, recent changes to deal with thread races and close-on-exec have resulted in dup3(), but this isn't currently mapped. While this would not be hard to add, it illistrates why it is better to move to an interface designed for this task. Andrew Bartlett Autobuild-User: Andrew Bartlett <abartlet@samba.org> Autobuild-Date: Thu Feb 9 01:58:24 CET 2012 on sn-devel-104
Diffstat (limited to 'examples/libsmbclient/smbwrapper/README')
-rw-r--r--examples/libsmbclient/smbwrapper/README40
1 files changed, 0 insertions, 40 deletions
diff --git a/examples/libsmbclient/smbwrapper/README b/examples/libsmbclient/smbwrapper/README
deleted file mode 100644
index 7b71ec06ba..0000000000
--- a/examples/libsmbclient/smbwrapper/README
+++ /dev/null
@@ -1,40 +0,0 @@
-To create "smbsh" on Linux, just type "make".
-
-If you execute "smbsh" in *this* directory (so that it can find the required
-shared library), you'll find yourself in a new shell. You can then issue
-commands referencing the "/smb" pseudo-filesystem:
-
- ls /smb
- ls /smb/WORKGROUP_OR_DOMAIN
- ls /smb/SERVER
- ls /smb/SERVER/SHARE
- ls /smb/SERVER/SHARE/PATH
-
-Note that WORKGROUP_OR_DOMAIN is *not* used other than at that level. This is
-consistent with the smb:// URI definition.
-
-Usage:
- smbsh [-L <path to find smbwrapper.so>]
- [-p <library to load before smbwrapper.so>]
- [-a <library to load after smbwrapper.so>]
- [-d <debug value for libsmbclient>]
- [-n] (do not ask for username/password)
- [-W <workgroup>]
- [-U <username%password]
- [command]
-
-So to list the contents of \\MYDESK\C$ where a username (adventure) and password
-(xyzzy) are required, and with smbwrapper.so installed in /usr/share/samba, you
-could try:
-
- smbsh -L /usr/share/samba -U adventure%xyzzy ls '/smb/MYDESK/C$'
-
-(It's a good idea to get in the habit of surrounding windows paths in single
-quotes, since they often contain spaces and other characters that'll give you
-headaches when not escaped.)
-
-This smbsh seems to work quite well on Linux 2.4 and 2.6. The biggest problem it
-has is in tracking your current working directory. I haven't had the time to
-track that down and fix it.
-
-Derrell Lipman