On Sat, Mar 10, 2007 at 05:26:47PM -0500, simo wrote: > On Sat, 2007-03-10 at 12:36 -0800, Jeremy Allison wrote: > > On Sat, Mar 10, 2007 at 08:40:12PM +0100, Stefan (metze) Metzmacher wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Jeremy Allison schrieb: > > > > which is incorrect. Now that's easy to fix, but > > > > the problem is when the client is in unix extensions > > > > posix pathname mode and accesses a DFS share which > > > > needs to reply with a redirect of : > > > > > > > > "\server\share\home/userluser/eLItE\haXor/" > > > > > > why not /sever/share/home/userluser/eLItE\haXor/ ? > > > > I thought of this, hmmmm. I originally thought > > this would be difficult to tell from an ordinary > > pathname, but you always get the DFS flag bit > > set on that name.... > > > > This would work for the incoming pathname, but > > outgoing redirect paths still must be canonicalized > > to \server\share\path as we don't have any info > > about the server we're redirecting to. > > But what would do a server that do not have unix extensions when > presented a path with mixed slashes like: \server\share/user/blah/ ? > > Will a windows server understand it ?
Of course not. That's why we'd never send such a path to a server with which we've not negotiated POSIX pathnames. Jeremy. _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
