Re: [Samba] Mac client

2007-11-16 Thread Adam Hardy

Good tip. I'm posting it to lists.samba.org so it will end up in the archives.

Thanks
Adam

Ryan Bair on 15/11/07 18:32, wrote:

As a side note, there is an option for the Mac clients to disable the
.DS_Store files from being created on network volumes. I always use
this on my clients because the .DS_Store creation will update the
modtime on the directory every single time a user goes to the
directory. It also causes the directory to open in the same view that
the last person was using, which tends to irritate users.

The command is "defaults write com.apple.desktopservices
DSDontWriteNetworkStores true" in the  terminal.

--Ryan

On Nov 15, 2007 3:34 AM, Adam Hardy <[EMAIL PROTECTED]> wrote:

Mikko Suomi on 14/11/07 16:48, wrote:

Adam Hardy wrote:

I'm trying to copy files to a Samba share that I have set up on a
linux debian machine from a Mac running OS X, using samba 3.0.24.

The Mac complains that there is something wrong with the file name,
and then refuses to copy, and the operation leaves a zero-byte file
with the same name on the samba share.

I had similiar problems with Mac's when I had veto files = /.*/ in samba
share to pervent users from deleting their linux profile files from
Windows workstations. (OSx likes to create .DS_Store -files to it's
folders) For some reason files could be written to samba from Macs
terminal window. Chancing veto files to /.bash*/ fixed problem for me.

Thanks for the tip.

I had veto = /*.{*}/.*/mail/bin

  - put in there by default by SWAT!


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Mac client

2007-11-15 Thread Adam Hardy

Mikko Suomi on 14/11/07 16:48, wrote:

Adam Hardy wrote:


I'm trying to copy files to a Samba share that I have set up on a 
linux debian machine from a Mac running OS X, using samba 3.0.24.


The Mac complains that there is something wrong with the file name, 
and then refuses to copy, and the operation leaves a zero-byte file 
with the same name on the samba share.


I had similiar problems with Mac's when I had veto files = /.*/ in samba 
share to pervent users from deleting their linux profile files from 
Windows workstations. (OSx likes to create .DS_Store -files to it's 
folders) For some reason files could be written to samba from Macs 
terminal window. Chancing veto files to /.bash*/ fixed problem for me.


Thanks for the tip.

I had veto = /*.{*}/.*/mail/bin

 - put in there by default by SWAT!

Thanks
Adam

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Mac client

2007-11-13 Thread Adam Hardy

I tried with a blah.txt as a test.

I can't find much on the internet from Apple about this. Nothing in fact. I 
can't be the only one, but it's beginning to look like it.


Thanks
Adam

Mike McGonagle on 13/11/07 00:44, wrote:

Are the Mac files using any ILLEGAL Windows characters? The Mac pretty
much allows any character in a filename, as long as it is escaped
properly, while Windows can't handle things like...

? [ ] / \ = + < > : ; " ,

The Mac will pretty much allow any of them to be used in a filename.

On 11/12/07, Adam Hardy <[EMAIL PROTECTED]> wrote:

I'm trying to copy files to a Samba share that I have set up on a linux debian
machine from a Mac running OS X, using samba 3.0.24.

The Mac complains that there is something wrong with the file name, and then
refuses to copy, and the operation leaves a zero-byte file with the same name on
the samba share.

It lets me log in nicely through the Mac File Finder.

I've just spent a couple of hours searching the net but without any luck at all.
Does anyone know what I should do in this situation?

The samba share works fine from my other linux machine.

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Mac client

2007-11-12 Thread Adam Hardy


I'm trying to copy files to a Samba share that I have set up on a linux debian 
machine from a Mac running OS X, using samba 3.0.24.


The Mac complains that there is something wrong with the file name, and then 
refuses to copy, and the operation leaves a zero-byte file with the same name on 
the samba share.


It lets me log in nicely through the Mac File Finder.

I've just spent a couple of hours searching the net but without any luck at all.
Does anyone know what I should do in this situation?

The samba share works fine from my other linux machine.


Thanks
Adam

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba