Re: freebsd4.7 and Samba and OS X
On Sun, 2003-02-09 at 01:34, Jon Reynolds wrote: On Sat, 2003-02-08 at 18:29, Bill Moran wrote: David Kelly wrote: On Saturday 08 February 2003 09:28 am, Bill Moran wrote: Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). I just thought of this ... Samba has the option to hide dot files which would prevent the Apples from ever seeing the .appledouble (as I remember) files at all. Yeah But... The .AppleDouble directories were created by NetAtalk. They were not the creation of clients which had connected to the share. But you may be on to something as MacOS X does like to create a dot file/directory on shared resources, its just not called .AppleDouble. More like .sD2 IIRC. Well, I could be wrong about, .AppleDouble specifically, but the whole theory that dotfiles could be disappearing into a Samba black hole is what I was trying to put across. I also think you guys might be on to something. The only difference between the 2 shares is that the ServerFiles share has a 'veto' option in it to hide these files. Maybe my understanding of veto is wrong, I always thought that it hid the files not disallowed them to be created. I will try again monday by commenting out the veto directive and see if that is the problem. I will post my results to the list about what I find. Thanks a lot! Jon I am on the OS X and Samba lists and posted this question to both lists. Out of desperation I posted to the FreeBSD list and once again my question was answered. This list ROCKS!!! The problem is now solved and both Macs and Windows boxen can get in and save and edit files on the Samba server. There are two possibilities to what made this work. One is what was told to me about creating '.' files for the Macs. The Macs create a '.' file in the directory to, I'm assuming, hold the resource fork for the file so the Mac can read it. The other solution might have been that when I looked back inot the ServerFiles share on the server I noticed there were already some '.' files created by the Macs. One of these was called '.FBCLockFolder' I deleted all the '.' files that I found to be created by the Macs and everthing is working as expected. Unfortunatley, I tried both solutions at once so can't say for sure which one was the fix. But I have posted both solutions in case anyone else runs into this problem. Thanks Again, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
On Sat, 2003-02-08 at 18:29, Bill Moran wrote: David Kelly wrote: On Saturday 08 February 2003 09:28 am, Bill Moran wrote: Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). I just thought of this ... Samba has the option to hide dot files which would prevent the Apples from ever seeing the .appledouble (as I remember) files at all. Yeah But... The .AppleDouble directories were created by NetAtalk. They were not the creation of clients which had connected to the share. But you may be on to something as MacOS X does like to create a dot file/directory on shared resources, its just not called .AppleDouble. More like .sD2 IIRC. Well, I could be wrong about, .AppleDouble specifically, but the whole theory that dotfiles could be disappearing into a Samba black hole is what I was trying to put across. I also think you guys might be on to something. The only difference between the 2 shares is that the ServerFiles share has a 'veto' option in it to hide these files. Maybe my understanding of veto is wrong, I always thought that it hid the files not disallowed them to be created. I will try again monday by commenting out the veto directive and see if that is the problem. I will post my results to the list about what I find. Thanks a lot! Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
On Sunday 09 February 2003 04:34 am, Jon Reynolds wrote: I also think you guys might be on to something. The only difference between the 2 shares is that the ServerFiles share has a 'veto' option in it to hide these files. Maybe my understanding of veto is wrong, I always thought that it hid the files not disallowed them to be created. And that's all it would take. If the client creates the dot files and then can't read them, then what is the point? Previously NetAtalk created the dot files itself, so it made sense to hide them from the clients. But in the case of MacOS X Jaguar, the client is creating dot files because it needs them for something. On AppleShare I suspect Jaguar creates the dot files only to track window sizes and icon placements. In the case of SMB shares where one does not have Data and Resource forks, I would expect the dot files created by the X client would be used to provide this functionality. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
On Thu, Feb 06, 2003 at 03:09:00PM -0900, [EMAIL PROTECTED] wrote: Forgot to copy the list on this: We are having this issue with samba and OSX 10.2.3. We are using freebsd4.7 serving samba as a fileserver for our company, we have a mix of windows and macs connecting to it. The windows machines work just fine the macs are another story. I have narrowed it down to this: I can open a file/document from the fileserver on my mac and edit it but it tells me I dont have the permissions to copy it back. This is from a volume that I mounted on the desktop using the 'apple+k' to mount it. When I mount it by command line I can edit the file/document(anyfile) and copy it back with no problem I have also found this to be true on my linux system. Exact same I don't claim to be an Apple expert, but I seem to remember that Apple supports it's file naming conventions by creating an exta file on DOS style partitions which maps the Apple filename to the DOS filename. Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
Jeff Penn wrote: On Thu, Feb 06, 2003 at 03:09:00PM -0900, [EMAIL PROTECTED] wrote: Forgot to copy the list on this: We are having this issue with samba and OSX 10.2.3. We are using freebsd4.7 serving samba as a fileserver for our company, we have a mix of windows and macs connecting to it. The windows machines work just fine the macs are another story. I have narrowed it down to this: I can open a file/document from the fileserver on my mac and edit it but it tells me I dont have the permissions to copy it back. This is from a volume that I mounted on the desktop using the 'apple+k' to mount it. When I mount it by command line I can edit the file/document(anyfile) and copy it back with no problem I have also found this to be true on my linux system. Exact same I don't claim to be an Apple expert, but I seem to remember that Apple supports it's file naming conventions by creating an exta file on DOS style partitions which maps the Apple filename to the DOS filename. Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). I just thought of this ... Samba has the option to hide dot files which would prevent the Apples from ever seeing the .appledouble (as I remember) files at all. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
On Saturday 08 February 2003 09:28 am, Bill Moran wrote: Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). I just thought of this ... Samba has the option to hide dot files which would prevent the Apples from ever seeing the .appledouble (as I remember) files at all. Yeah But... The .AppleDouble directories were created by NetAtalk. They were not the creation of clients which had connected to the share. But you may be on to something as MacOS X does like to create a dot file/directory on shared resources, its just not called .AppleDouble. More like .sD2 IIRC. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
David Kelly wrote: On Saturday 08 February 2003 09:28 am, Bill Moran wrote: Maybe the Apple system has not got the necessary permissions to create this extra file. This could be way off the mark though :). I just thought of this ... Samba has the option to hide dot files which would prevent the Apples from ever seeing the .appledouble (as I remember) files at all. Yeah But... The .AppleDouble directories were created by NetAtalk. They were not the creation of clients which had connected to the share. But you may be on to something as MacOS X does like to create a dot file/directory on shared resources, its just not called .AppleDouble. More like .sD2 IIRC. Well, I could be wrong about, .AppleDouble specifically, but the whole theory that dotfiles could be disappearing into a Samba black hole is what I was trying to put across. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd4.7 and Samba and OS X
On Saturday 08 February 2003 09:29 pm, Bill Moran wrote: David Kelly wrote: But you may be on to something as MacOS X does like to create a dot file/directory on shared resources, its just not called .AppleDouble. More like .sD2 IIRC. Well, I could be wrong about, .AppleDouble specifically, but the whole theory that dotfiles could be disappearing into a Samba black hole is what I was trying to put across. Yes, I didn't mean to sound as if I was discounting your idea as I think you are on the right track. Here is a snippet from a filesystem which I know was being shared by NetAtalk and Samba. The only NetAtalk client recently was MacOS X 10.2.3 but has been used by everything since 7.6.1 and a good number of FreeBSD's since 3-something. ls -laCF | more total 200310 drwxr-xr-x 18 dkelly wheel 1536 Jan 15 11:35 ./ drwxrwxr-x 6 dkelly wheel512 Feb 7 14:27 ../ drwxr-xr-x 2 dkelly wheel512 Jan 6 16:46 .AppleDB/ drwxr-xr-x 11 dkelly wheel512 Nov 21 17:21 .AppleDesktop/ drwxr-xr-x 2 dkelly wheel512 Jan 15 11:35 .AppleDouble/ -rwxr--r-- 1 dkelly wheel 6148 Oct 18 16:14 .DS_Store* -rw-r--r-- 1 dkelly wheel 6148 Jan 15 11:35 :2eDS_Store I believe .DS_Store and :2eDS_Store are unique to MacOS X and created by MacOS X. 2e is hex for an ASCII dot, my guess is :2e is an Apple escape mechanism for the dot. Also think I have mounted the above on my Jaguar system via both AppleTalk and Samba protocols. This week I upgraded the above FreeBSD machine to 5.0. Prior to the upgrade I removed all ports. Had a rough time trying to upgrade via make. Another rough time trying to do a binary upgrade via CD. Eventually wiped my entire boot drive and did a clean installation from CD. So I don't have NetAtalk nor Samba reinstalled just yet. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
freebsd4.7 and Samba and OS X
Hello, We are having this issue with samba and OSX 10.2.3. We are using freebsd4.7 serving samba as a fileserver for our company, we have a mix of windows and macs connecting to it. The windows machines work just fine the macs are another story. I have narrowed it down to this: I can open a file/document from the fileserver on my mac and edit it but it tells me I dont have the permissions to copy it back. This is from a volume that I mounted on the desktop using the 'apple+k' to mount it. When I mount it by command line I can edit the file/document(anyfile) and copy it back with no problem. I have also found this to be true on my linux system. Exact same problem when trying to edit and copy a file back to the fileserver that has been mounted on the desktop, I get the permission denied error. When mounted by command line I can open any file and edit it then copy it back. Has anyone run into this before and have found a solution they would like to share? I have done google searches but from everything I find it doesn't answer my question or im just not posing the question correctly. Thanks for any help, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
