On Fri, Dec 10, 2004 at 10:34:54AM +0800, Not Zed wrote: > > > > You know, I can probably fix this in the smbd server code by detecting > > a UNIX client and relaxing the "invalid character" checks for things > > like : etc. > > Wont that just cause interoperability issues?
No - it'll only allow that for clients identified as UNIX. We already do something similar to give default case sensitive operation for UNIX clients. > Not going to help real windows based backends though. Yes, that needs a client side fix. > While you're here, slightly OT, I noticed when using smbmount that > seek(0, END) failed on that filesystem (it was from some netware box i > think). Is that the server end? Is smbmount the way this is done? > Should all the 'normal' filesystem calls/semantics work on such a > filesystem, e.g. things like files existing after they're unlinked if > they're still open, etc. It depends on the client you're using (smbfs or cifsfs) - each does different things (although cifsfs is more modern these days). Jeremy. _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
