Hi Francois,
I think the best way to handle UNC pathes is to do it properly; Wine should talk SMB/NBT directly to other machines on the network, not through Linux's VFS layer.
This approach would give high level of flexability to Wine. We could:
* support NetDDE and DCOM with a common code base * use Windows file permissions and security properly * support unicode share names properly * support named pipes, etc across the network * eliminate SMB<->VFS<->SMB problems eg. parsing /etc/fstab
There's three options: 1) write our own SMB code (wineserver talks NetBIOS/SMB) i have a short snippet of code to resolve NetBIOS names in CreateFile, but that is only the beginning of the effort.
2) link with a LGPL'ed CIFS implementation. http://www.ubiqx.org/libcifs/ (very incomplete, but maybe possible later, may still have threading issues)
3) get Samba to provide us with a Unix domain socket to talk with. (SambaTNG looks like the best bet there.)
i have experimented with linking Wine to samba's libsmbclient and use it to open files. That works (i have a test patch), has threading and licensing issues (it's GPL).
This would be alot of work, but i think it's the only way to do it properly.
Mike
does
config
way w
running.
------------------------------------------ mailto:Mike_McCormack@start.com.au ph +82 16 430 0425
__________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au
On Wed, Dec 26, 2001 at 12:08:46PM +1000, Mike McCormack wrote:
Yep. Actually I've never understood why one would go through mount points for *dynamic* host paths ! In short: do it once, do it *right*. Don't go for a weak compromise. That's why I'm strongly in favour of high Samba integration. Wine really needs this functionality, AFAICS.