Hi , I have an application running on windows,which uses batch files.Now planned to move it onto unix/linux platform and so had be converting the batch scripts onto shell scripts for the same. Now the windows scripts have few commands where in it connects to another machine and i have commands to access it like 'net use' from windows.
In the case of Unix machines using Windows Networking, the product to use is Samba. There's not a 1-for-1 command translation, however, since Windows and Unix have different ways of looking at the universe.
For a permanent connection, you can use the smbmount facility to map a location globally. For example, I could set up an automatic mount to \\mywinfs\share1 to be mounted at /winshare. Note, BTW, that in Samba, that would be "//mywinfs/share1" so that the backslashes wouldn't be confused with escape characters.
For a less permanent connection (such as user-specific shares), you can do an automount. I've no experience with that one, though.
For one-shot file transfers, use the smbclient utility like it was ftp. Or, for copying whole directories into/from tar files (e.g. for backups) there's a handy little utility called smbtar.
For sharing out a part of your Unix machine to Windows users, you have to install the samba server and define the shares in the samba.conf file.
Sometimes the only way things ever got fixed is because people became uncomfortable.
The overall mission is to change the world. When you've done that, then you can read this tiny ad: