I've built a new samba server to replace an aging Apple 9500 running 8.6 that is acting as a 'file server'. The other macs run 9.2 and 10.2, which are the computers that will be served (I HOPE!) by the samba server. I have installed DAVE in order to be able to copy the files over to the new server. However, as the files copy, they disappear on the samba server. Someone said it is because of the data and resource forks in the old mac os, and to tell DAVE to, as I believe he said, merge the two forks. However, I see no such option in the DAVE setup. Am I missing something, or is there another way to do this? Also, will I have a problem with files name preservation of the mac files on the new server? Thanks, Matt
At 08:00 AM 10/26/2002 -0500, you wrote:>I've built a new samba server to replace an aging Apple 9500 running 8.6 >that is acting as a 'file server'. The other macs run 9.2 and 10.2, which >are the computers that will be served (I HOPE!) by the samba server. > >I have installed DAVE in order to be able to copy the files over to the >new server. However, as the files copy, they disappear on the samba >server. Someone said it is because of the data and resource forks in the >old mac os, and to tell DAVE to, as I believe he said, merge the two >forks. However, I see no such option in the DAVE setup. > >Am I missing something, or is there another way to do this? Also, will I >have a problem with files name preservation of the mac files on the new server? > >Thanks, > >MattFollowing up to myself while I await someone else's insight.... I just found that if I copy the files via my win2k workstation, the files stay put. What? -- Matt
Since I posted this over the weekend, I thought I'd throw it out one more time to see if anyone else might see it and has any ideas on this. Thanks for your indulgence. -- Matt At 08:34 AM 10/26/2002 -0500, you wrote:>At 08:00 AM 10/26/2002 -0500, you wrote: >>I've built a new samba server to replace an aging Apple 9500 running 8.6 >>that is acting as a 'file server'. The other macs run 9.2 and 10.2, >>which are the computers that will be served (I HOPE!) by the samba server. >> >>I have installed DAVE in order to be able to copy the files over to the >>new server. However, as the files copy, they disappear on the samba >>server. Someone said it is because of the data and resource forks in >>the old mac os, and to tell DAVE to, as I believe he said, merge the two >>forks. However, I see no such option in the DAVE setup. >> >>Am I missing something, or is there another way to do this? Also, will I >>have a problem with files name preservation of the mac files on the new server? >> >>Thanks, >> >>Matt > >Following up to myself while I await someone else's insight.... I just >found that if I copy the files via my win2k workstation, the files stay >put. What? > >-- >Matt
Matt, I am not sure what the problem is but in the smb.conf file on the Samba server the following lines should be set to preserve file name case for Macintosh applications: preserve case = yes short preserve case = yes I have run Samba servers on Solaris and Linux machines with no problems connecting and transferring files to and fro from Mac OS 8.6, 9.2, and 10.1.5 all running Dave. You should run at least Dave 3.1. You can use netatalk. I have used it on Linux but you have configure that in Samba when you compile if you want them to work together. Or you can just use netatalk. I prefer Dave because it is actually easier to setup. You are also not adding another protocol to worry about. Don Werder aettinger1984@comcast.net> >Subject: Re: [Samba] Older Mac to SAMBA copy >From: "Bradley W. Langhorst" <brad@langhorst.com> >To: Matt Nelson <matt@nelsonprinting.com> >Cc: samba@lists.samba.org >Date: 29 Oct 2002 11:53:23 -0500 > >On Tue, 2002-10-29 at 10:41, Matt Nelson wrote: > >>I was planning to use (and that is what is installed now), DAVE by Thursby >>inc. That allows SMB usage on a Mac. Its the file corruption that is >>occurring on a mac to samba copy, that doesn't occur on a mac to samba VIA >>windows 2k wkstn that has me stumped. >> > >this is probably a bug in DAVE - i've had lots of problems with it >before. > >>Any ideas folks? *pleading* >> >then listen to to the people who have told you this (including me) > >Sorry to repeat myself but you don't seem to get it. Unless I >misunderstand something about your situation samba is not the right >choice for your application. You should be using netatalk. > >really - not kidding - use netatalk > >brad > > >
I did that, still no luck. Files just dissappear. If I run netatalk, can the pc clients still work with the files as well? I don't understand why a direct copy fails, and a copy VIA a windows workstation works. That makes *no* sense. -- Matt At 03:44 PM 10/29/2002 -0500, you wrote:>Matt, >I am not sure what the problem is but in the smb.conf file on the Samba >server the following lines should be set to >preserve file name case for Macintosh applications: > >preserve case = yes >short preserve case = yes > >I have run Samba servers on Solaris and Linux machines with no problems >connecting and transferring files to and fro from Mac OS 8.6, 9.2, and >10.1.5 all running Dave. You should run at least Dave 3.1. > >You can use netatalk. I have used it on Linux but you have configure that >in Samba when you compile if you want them to work together. Or you can >just use netatalk. I prefer Dave because it is actually easier to setup. >You are also not adding another protocol to worry about. > >Don Werder >aettinger1984@comcast.net > > >> >>Subject: Re: [Samba] Older Mac to SAMBA copy >>From: "Bradley W. Langhorst" <brad@langhorst.com> >>To: Matt Nelson <matt@nelsonprinting.com> >>Cc: samba@lists.samba.org >>Date: 29 Oct 2002 11:53:23 -0500 >> >>On Tue, 2002-10-29 at 10:41, Matt Nelson wrote: >> >>>I was planning to use (and that is what is installed now), DAVE by >>>Thursby inc. That allows SMB usage on a Mac. Its the file corruption >>>that is occurring on a mac to samba copy, that doesn't occur on a mac to >>>samba VIA windows 2k wkstn that has me stumped. >>this is probably a bug in DAVE - i've had lots of problems with it >>before. >> >>>Any ideas folks? *pleading* >>then listen to to the people who have told you this (including me) >> >>Sorry to repeat myself but you don't seem to get it. Unless I >>misunderstand something about your situation samba is not the right >>choice for your application. You should be using netatalk. >> >>really - not kidding - use netatalk >>brad >> >> > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba