Subject: Re: [netatalk-admins] Samba/Unix File Management vs. ResourceForks?
From: Matthew Keller (kellermg@potsdam.edu)
Date: Sun Jul 18 1999 - 13:30:23 EDT
a sun wrote:
> a quick question: do those pesky files screw up just win9x or do they
> cause problems with nt as well?
They screw up NT over a network connection, but NT can use the files if
the were created on the server. Hmmm. That's not very clear, perhaps an
example?
Mac 1 connects to NT server 1 and create a file called "This / is / a !
Bad ? File". If an NT box tries to access that file over MS networking
on NT server 1, it cannot. If someone sitting at the console of NT
server 1 tries to access it, it is allowed. Does that make more sense?
Another strange problem: Once Mac 1 creates that file, it cannot delete
it. It can read it, but never delete it. It is necessary to be at NT
server 1's console to delete that file.
IMHO: Netatalk should prevent the creation of the "bad" filenames
altogether, or perhaps allow for a "translation file", so that Netatalk
admins can map the "bad" characters to a "good" character. For example a
lot of our Mac people are accustomed to creating files with dates such
as "7/7/99 This is a file"- I have a Perl Script on the NT server that
then remaps all of the bad characters to a '.' so the file is now called
"7.7.99 This is a file". This does not appear to work on Netatalk
though, as the file is instantly(?) mangled.
--- Matthew Keller - Lead Programmer/Analyst Distributed Computing and Telemedia State University of New York at Potsdam
Web: http://mattwork.potsdam.edu/ PGP: http://mattwork.potsdam.edu/crypto/
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:58 EST