I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Is there a commonly used procedure to do the above task of copying a Mac (HFS, I think) system to a linux box from the linux box?
This sort of runs into another project we have in the works where we want to make the equivalent of a SAN/NAS type storage system. We want to have a cluster of Centos boxes running for shared storage, and have the ability to add to it seamlessly. But now, I'm wondering if it won't run into the same problem with the HFS or other filesystems that may be used. I understand NAS storage sort of handles the different filesystem protocols by interface, so I wondering if anyone has a pointer to something like this also.
Google keeps pointing me in a circle back to an old HFS+ driver that sort of stopped development in 2003. The trail ends very abruptly.
Sorry to be so windy, but offer thanks in advance for any clues.
Steve Campbell
Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Offhand, I'd try NFS rather than CIFS. Wild guess says the NAS box stores the Macintosh 'resource forks' in alternate files, using some funky naming convention, and likely masks this from "windows" systems connecting via SMB/CIFS. its extremely unlikely its using HFS as the internal storage, much more likely its e3fs or similar. If you pulled the drives from the NAS box and direct connected them to a linux box, you could probably figure out what they were doing by poking around, assuming you could hook up to the raid structure (some of those boxes use proprietary raid extensions, like ReadyNAS with its 'raid-x' expandable/restripable raid.
John R Pierce wrote:
Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Offhand, I'd try NFS rather than CIFS. Wild guess says the NAS box stores the Macintosh 'resource forks' in alternate files, using some funky naming convention, and likely masks this from "windows" systems connecting via SMB/CIFS. its extremely unlikely its using HFS as the internal storage, much more likely its e3fs or similar. If you pulled the drives from the NAS box and direct connected them to a linux box, you could probably figure out what they were doing by poking around, assuming you could hook up to the raid structure (some of those boxes use proprietary raid extensions, like ReadyNAS with its 'raid-x' expandable/restripable raid.
How would the Linux box see anything different if mounted NFS? I agree that CIFS is probably just emulating Windows, so I understand that part. I'll have to research the e3fs stuff as I'm not familiar with all of that also. This is the kind of problem that really just humbles me so much.
Thanks,
Steve
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Steve Campbell wrote:
How would the Linux box see anything different if mounted NFS? I agree that CIFS is probably just emulating Windows, so I understand that part. I'll have to research the e3fs stuff as I'm not familiar with all of that also. This is the kind of problem that really just humbles me so much.
well, my gut feeling is, NFS is likely closer to the NAS boxes' native linux filesystem than CIFS (which is likely Samba based on this NAS box), and would be more likely to make hidden files accessible.
while I'm rather unfamiliar with the specifics of macintosh->linux file sharing implementations, I'd guess there's several ways a Linux server could emulate Macintosh 'resource forks'...
1) store the fork data in a seperate file in hte same directory with a hidden filename like .MACFORK.originalfilename
2) store the fork data in a hidden parallel directory, like ./.MACFORK/originalfilename
ahhhh. NetATalk uses ./.AppleDouble to store the RK's and other metadata for the files in each directory. so, if you have a file ./MyMacFile, presumably, there's something in ./AppleDouble that correlates to this and contains the RK for MyMacFile
see http://netatalk.sourceforge.net/wiki/index.php/SpecialFilesFolders?PHPSESSID...
chances are pretty good that if your NAS box supports appletalk stuff, this is what its using.
On Wed, 2008-01-09 at 15:49 -0500, Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Is there a commonly used procedure to do the above task of copying a Mac (HFS, I think) system to a linux box from the linux box?
This sort of runs into another project we have in the works where we want to make the equivalent of a SAN/NAS type storage system. We want to have a cluster of Centos boxes running for shared storage, and have the ability to add to it seamlessly. But now, I'm wondering if it won't run into the same problem with the HFS or other filesystems that may be used. I understand NAS storage sort of handles the different filesystem protocols by interface, so I wondering if anyone has a pointer to something like this also.
Google keeps pointing me in a circle back to an old HFS+ driver that sort of stopped development in 2003. The trail ends very abruptly.
Sorry to be so windy, but offer thanks in advance for any clues.
---- If you want to be certain that you preserve the Macintosh resource forks, you might want to add Netatalk (http://netatalk.sourceforge.net), which makes it a real AFPoverTCP file server. Then you use a Macintosh to copy the files over.
Otherwise, I would suggest that you use tar to copy the folders over which should preserve all of the contents.
Are you sure that those are really HFS (or HFSPlus) filesystems?
Craig
On Wed, 2008-01-09 at 14:09 -0700, Craig White wrote:
On Wed, 2008-01-09 at 15:49 -0500, Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Is there a commonly used procedure to do the above task of copying a Mac (HFS, I think) system to a linux box from the linux box?
This sort of runs into another project we have in the works where we want to make the equivalent of a SAN/NAS type storage system. We want to have a cluster of Centos boxes running for shared storage, and have the ability to add to it seamlessly. But now, I'm wondering if it won't run into the same problem with the HFS or other filesystems that may be used. I understand NAS storage sort of handles the different filesystem protocols by interface, so I wondering if anyone has a pointer to something like this also.
Google keeps pointing me in a circle back to an old HFS+ driver that sort of stopped development in 2003. The trail ends very abruptly.
Sorry to be so windy, but offer thanks in advance for any clues.
If you want to be certain that you preserve the Macintosh resource forks, you might want to add Netatalk (http://netatalk.sourceforge.net), which makes it a real AFPoverTCP file server. Then you use a Macintosh to copy the files over.
Otherwise, I would suggest that you use tar to copy the folders over which should preserve all of the contents.
Are you sure that those are really HFS (or HFSPlus) filesystems?
---- on second thought...tar probably won't work. Every system has a different methodology for storing the resource fork (the Macintosh curse).
Best to just use a Mac to copy Macintosh files and let each system create/maintain/discard resource fork info as it sees fit.
Craig
Craig White wrote:
On Wed, 2008-01-09 at 15:49 -0500, Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Is there a commonly used procedure to do the above task of copying a Mac (HFS, I think) system to a linux box from the linux box?
This sort of runs into another project we have in the works where we want to make the equivalent of a SAN/NAS type storage system. We want to have a cluster of Centos boxes running for shared storage, and have the ability to add to it seamlessly. But now, I'm wondering if it won't run into the same problem with the HFS or other filesystems that may be used. I understand NAS storage sort of handles the different filesystem protocols by interface, so I wondering if anyone has a pointer to something like this also.
Google keeps pointing me in a circle back to an old HFS+ driver that sort of stopped development in 2003. The trail ends very abruptly.
Sorry to be so windy, but offer thanks in advance for any clues.
If you want to be certain that you preserve the Macintosh resource forks, you might want to add Netatalk (http://netatalk.sourceforge.net), which makes it a real AFPoverTCP file server. Then you use a Macintosh to copy the files over.
Otherwise, I would suggest that you use tar to copy the folders over which should preserve all of the contents.
Are you sure that those are really HFS (or HFSPlus) filesystems?
No, I'm not sure of anything on the Thecus, as I didn't have anything to do with it's setup or population. I was just asked to back it up. Seems like when it comes to doing the important stuff, they always come to the Linux guys.
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Sorry to be so dense that I can't answer your questions on the subject. It's all new to me. Thanks, though.
Steve
Craig
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, 2008-01-09 at 16:38 -0500, Steve Campbell wrote:
Craig White wrote:
On Wed, 2008-01-09 at 15:49 -0500, Steve Campbell wrote:
I ran into a problem that I couldn't resolve straight away, but would like to solve for sometime in the future.
We have a Thecus storage server (similar to a Buffalo TeraByte, if that helps?) that has a Mac filesystem on it. The mother board was failing, but the drives are still OK. A new box has been added, so the urgency is sort of gone. I was going to try and back up the data to a new CentOS 5.1 box I had until the new Thecus arrived, but ran into the problem of Mac resource forks not being copied when I mounted the Thecus as a CIFS system.
Is there a commonly used procedure to do the above task of copying a Mac (HFS, I think) system to a linux box from the linux box?
This sort of runs into another project we have in the works where we want to make the equivalent of a SAN/NAS type storage system. We want to have a cluster of Centos boxes running for shared storage, and have the ability to add to it seamlessly. But now, I'm wondering if it won't run into the same problem with the HFS or other filesystems that may be used. I understand NAS storage sort of handles the different filesystem protocols by interface, so I wondering if anyone has a pointer to something like this also.
Google keeps pointing me in a circle back to an old HFS+ driver that sort of stopped development in 2003. The trail ends very abruptly.
Sorry to be so windy, but offer thanks in advance for any clues.
If you want to be certain that you preserve the Macintosh resource forks, you might want to add Netatalk (http://netatalk.sourceforge.net), which makes it a real AFPoverTCP file server. Then you use a Macintosh to copy the files over.
Otherwise, I would suggest that you use tar to copy the folders over which should preserve all of the contents.
Are you sure that those are really HFS (or HFSPlus) filesystems?
No, I'm not sure of anything on the Thecus, as I didn't have anything to do with it's setup or population. I was just asked to back it up. Seems like when it comes to doing the important stuff, they always come to the Linux guys.
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Sorry to be so dense that I can't answer your questions on the subject. It's all new to me. Thanks, though.
---- I doubt it had HFS/HFSPlus filesystem but rather used something like Netatalk for Apple clients. Easy way to find out...sit in front of a Mac and see if you can connect to it by...
Go (menu) => Connect to Server => afp://ip_address_of_server
and if it offers login, it's a Macintosh file server
Again, I would use a Macintosh to move the files if retaining the resource forks is important. That's the only way to ensure that they are moved and work.
Note that if a Mac copies the files to a Samba (CIFS) server, the resource forks will be discarded. I don't know what will happen if NFS.
Craig
Steve Campbell wrote:
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Having almost bought one of their products (ended up going with QNap instead), I'm almost certain from my research at the time that the Thecus NAS appliances run a linux-based OS and most likely use ext3 filesystem (as a previous poster mentioned).
When shared over the network (NFS, CIFS, etc.), the filesystem on the NAS or server doesn't actually matter. Macs can still mount the network share and read/write to it. It doesn't have to be HFS for this to happen.
In terms of the resource forks, I'd be surprised if this is even an issue. Can you clarify what problems/issues/symptoms you are seeing that makes you believe you need to "copy" the resource forks?
What kind of files are these? If they are regular documents (Office, Adobe, images, videos, etc.), you should have no problems just copying the files from the mounted drive to somewhere else (another Mac, a Windows box, or a Linux box).
If they are applications or some other binaries, there *might* be issues, but even then, I'm not convinced.
p.s. Unless you are still using pre-OS X Macs, in which case, all bets are off...
johnn
Johnny Tan wrote:
Steve Campbell wrote:
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Having almost bought one of their products (ended up going with QNap instead), I'm almost certain from my research at the time that the Thecus NAS appliances run a linux-based OS and most likely use ext3 filesystem (as a previous poster mentioned).
When shared over the network (NFS, CIFS, etc.), the filesystem on the NAS or server doesn't actually matter. Macs can still mount the network share and read/write to it. It doesn't have to be HFS for this to happen.
In terms of the resource forks, I'd be surprised if this is even an issue. Can you clarify what problems/issues/symptoms you are seeing that makes you believe you need to "copy" the resource forks?
What kind of files are these? If they are regular documents (Office, Adobe, images, videos, etc.), you should have no problems just copying the files from the mounted drive to somewhere else (another Mac, a Windows box, or a Linux box).
If they are applications or some other binaries, there *might* be issues, but even then, I'm not convinced.
p.s. Unless you are still using pre-OS X Macs, in which case, all bets are off...
Good explanation.
Unfortunately, these are pre OS X files. They probably are more messed up than usual as they are 2003-2008 MultiAd Creator files. A lot of the fonts, font info, graphic stuff were placed in the meta files, and without those, they are useless without a lot of extra work to recreate the set of files.
The reason I feel the resource files are needed is that I started copying the files from the Thecus, and then rewrote them back to another area on the Thecus. I then tried to "explore" or view them on the Mac that originally wrote them with no success.
I have no need to use these original files other than to have them as a backup source for the originals.
I think I'm hearing everyone say just to mount my Centos partition on a Mac and copy them from the Thecus to the Centos partition.. Is that the concensus here? If so what, then, is the best way to export the Centos partition so that the Mac can access it?
Thanks for the informative thread and answers to all.
Steve
johnn _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2008-01-10 at 09:00 -0500, Steve Campbell wrote:
Johnny Tan wrote:
Steve Campbell wrote:
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Having almost bought one of their products (ended up going with QNap instead), I'm almost certain from my research at the time that the Thecus NAS appliances run a linux-based OS and most likely use ext3 filesystem (as a previous poster mentioned).
When shared over the network (NFS, CIFS, etc.), the filesystem on the NAS or server doesn't actually matter. Macs can still mount the network share and read/write to it. It doesn't have to be HFS for this to happen.
In terms of the resource forks, I'd be surprised if this is even an issue. Can you clarify what problems/issues/symptoms you are seeing that makes you believe you need to "copy" the resource forks?
What kind of files are these? If they are regular documents (Office, Adobe, images, videos, etc.), you should have no problems just copying the files from the mounted drive to somewhere else (another Mac, a Windows box, or a Linux box).
If they are applications or some other binaries, there *might* be issues, but even then, I'm not convinced.
p.s. Unless you are still using pre-OS X Macs, in which case, all bets are off...
Good explanation.
Unfortunately, these are pre OS X files. They probably are more messed up than usual as they are 2003-2008 MultiAd Creator files. A lot of the fonts, font info, graphic stuff were placed in the meta files, and without those, they are useless without a lot of extra work to recreate the set of files.
The reason I feel the resource files are needed is that I started copying the files from the Thecus, and then rewrote them back to another area on the Thecus. I then tried to "explore" or view them on the Mac that originally wrote them with no success.
I have no need to use these original files other than to have them as a backup source for the originals.
I think I'm hearing everyone say just to mount my Centos partition on a Mac and copy them from the Thecus to the Centos partition.. Is that the concensus here? If so what, then, is the best way to export the Centos partition so that the Mac can access it?
Thanks for the informative thread and answers to all.
---- netatalk - link provided earlier in thread, use their cvs version for CentOS 5
if you have Mac OS 9 clients, you *might* want to use CentOS-plus kernel since it includes appletalk module which means that with netatalk and appletalk module, CentOS server will actually show up in the Chooser. Otherwise, you will have to connect to the printer via IP address not difficult for OS 9 computers but certainly not the most user friendly setup.
Craig
Craig White wrote:
On Thu, 2008-01-10 at 09:00 -0500, Steve Campbell wrote:
Johnny Tan wrote:
Steve Campbell wrote:
I don't understand, though, how it could have been populated with Mac stuff unless it either had a Mac fs or something or the sorts. A Mac wrote the data, but I'm not sure what type of format the system had. I really don't have a clue about this or how to fix up the NAS if we ever get that far.
Having almost bought one of their products (ended up going with QNap instead), I'm almost certain from my research at the time that the Thecus NAS appliances run a linux-based OS and most likely use ext3 filesystem (as a previous poster mentioned).
When shared over the network (NFS, CIFS, etc.), the filesystem on the NAS or server doesn't actually matter. Macs can still mount the network share and read/write to it. It doesn't have to be HFS for this to happen.
In terms of the resource forks, I'd be surprised if this is even an issue. Can you clarify what problems/issues/symptoms you are seeing that makes you believe you need to "copy" the resource forks?
What kind of files are these? If they are regular documents (Office, Adobe, images, videos, etc.), you should have no problems just copying the files from the mounted drive to somewhere else (another Mac, a Windows box, or a Linux box).
If they are applications or some other binaries, there *might* be issues, but even then, I'm not convinced.
p.s. Unless you are still using pre-OS X Macs, in which case, all bets are off...
Good explanation.
Unfortunately, these are pre OS X files. They probably are more messed up than usual as they are 2003-2008 MultiAd Creator files. A lot of the fonts, font info, graphic stuff were placed in the meta files, and without those, they are useless without a lot of extra work to recreate the set of files.
The reason I feel the resource files are needed is that I started copying the files from the Thecus, and then rewrote them back to another area on the Thecus. I then tried to "explore" or view them on the Mac that originally wrote them with no success.
I have no need to use these original files other than to have them as a backup source for the originals.
I think I'm hearing everyone say just to mount my Centos partition on a Mac and copy them from the Thecus to the Centos partition.. Is that the concensus here? If so what, then, is the best way to export the Centos partition so that the Mac can access it?
Thanks for the informative thread and answers to all.
netatalk - link provided earlier in thread, use their cvs version for CentOS 5
Never used CVS to access a file. I don't see how I can get the files here. For now, I've downloaded the 2.0.3 stable. What are the reasons for using cvs with my 5.1? Will it fail on config/make or what? (Only if you have time to explain)
if you have Mac OS 9 clients, you *might* want to use CentOS-plus kernel since it includes appletalk module which means that with netatalk and appletalk module, CentOS server will actually show up in the Chooser. Otherwise, you will have to connect to the printer via IP address not difficult for OS 9 computers but certainly not the most user friendly setup.
I've started installing the plus kernels, (xen and vanilla, I may try both). The Mac is an older one so I'll definitely try one of those two kernels. Probably try the stable netatalk just to see also.
Now to find the time to read the manual and do some of this.
Thanks Craig.
Steve
Craig
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2008-01-10 at 12:01 -0500, Steve Campbell wrote:
netatalk - link provided earlier in thread, use their cvs version for CentOS 5
Never used CVS to access a file. I don't see how I can get the files here. For now, I've downloaded the 2.0.3 stable. What are the reasons for using cvs with my 5.1? Will it fail on config/make or what? (Only if you have time to explain)
---- yes, compile will fail.
probably time to learn about cvs then, it's not difficult and instructions are there on netatalk cvs (anonymous login is fine)
you simply download the source via cvs command instead of clicking a tarball, otherwise, little difference ----
if you have Mac OS 9 clients, you *might* want to use CentOS-plus kernel since it includes appletalk module which means that with netatalk and appletalk module, CentOS server will actually show up in the Chooser. Otherwise, you will have to connect to the printer via IP address not difficult for OS 9 computers but certainly not the most user friendly setup.
I've started installing the plus kernels, (xen and vanilla, I may try both). The Mac is an older one so I'll definitely try one of those two kernels. Probably try the stable netatalk just to see also.
Now to find the time to read the manual and do some of this.
---- stable (2.0.3) netatalk simply won't compile on CentOS 5 - netatalk developers know that.
xen kernel has nothing to do with this. You don't have to use CentOS-Plus kernel if you don't care whether the server appears in the chooser of the older Macs (that's known as DDP). You don't have to use the CentOS-Plus kernel if you download the kernel source and compile your own appletalk module but that's probably more than most are willing to do and CentOS generously makes their CentOS-plus kernel available which greatly simplifies this because it includes the modules that RHEL decided to omit because they don't want to support them.
Bonus plan today...I'm feeling generous. This is my compile options for Netatalk on CentOS-5...
# cat /opt/netatalk-cvs/compile_neta ./configure \ --enable-overwrite \ --prefix=/usr \ --exec-prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var/lib \ --enable-redhat \ --enable-timelord \ --enable-cups \ --with-did=cnid \ --with-db3=/usr \ --with-pam \ --with-shadow \ --with-tcp-wrappers \ --with-ssl-dir=/usr \ --enable-fhs \ --with-gssapi=/usr/kerberos/include \ --enable-krb4-uam \ --enable-krbV-uam \ --with-mutex="x86/gcc-assembly"
You're gonna need openssl-devel, krb5-devel, db4-devel, cups-devel packages installed for this set of compile options to work.
Craig
Craig White wrote:
On Thu, 2008-01-10 at 12:01 -0500, Steve Campbell wrote:
netatalk - link provided earlier in thread, use their cvs version for CentOS 5
Never used CVS to access a file. I don't see how I can get the files here. For now, I've downloaded the 2.0.3 stable. What are the reasons for using cvs with my 5.1? Will it fail on config/make or what? (Only if you have time to explain)
yes, compile will fail.
probably time to learn about cvs then, it's not difficult and instructions are there on netatalk cvs (anonymous login is fine)
I've been reading those docs since you mentioned the cvs. It will take me a little time, though, as there are a few other things going on around here today. But it's sounds like time well spent when I get around to it.
you simply download the source via cvs command instead of clicking a tarball, otherwise, little difference
if you have Mac OS 9 clients, you *might* want to use CentOS-plus kernel since it includes appletalk module which means that with netatalk and appletalk module, CentOS server will actually show up in the Chooser. Otherwise, you will have to connect to the printer via IP address not difficult for OS 9 computers but certainly not the most user friendly setup.
I've started installing the plus kernels, (xen and vanilla, I may try both). The Mac is an older one so I'll definitely try one of those two kernels. Probably try the stable netatalk just to see also.
Now to find the time to read the manual and do some of this.
stable (2.0.3) netatalk simply won't compile on CentOS 5 - netatalk developers know that.
Bummer!
xen kernel has nothing to do with this. You don't have to use CentOS-Plus kernel if you don't care whether the server appears in the chooser of the older Macs (that's known as DDP). You don't have to use the CentOS-Plus kernel if you download the kernel source and compile your own appletalk module but that's probably more than most are willing to do and CentOS generously makes their CentOS-plus kernel available which greatly simplifies this because it includes the modules that RHEL decided to omit because they don't want to support them.
I installed the xen kernel as well to maybe prevent a lot of problems on reboot since that's what is running now. Once I get the machine tested, I'll probably trash it and start over without xen. This was mostly a test machine for some new raid cages we're trying and it happened to have enough storage to back up the Thecus. A convenience server for now. Since I'll reinstall it fresh, it seems like a good machine to play with for those later problems with the NAS junk.
Bonus plan today...I'm feeling generous. This is my compile options for Netatalk on CentOS-5...
Thanks, you've been more than generous, in my opinion.
# cat /opt/netatalk-cvs/compile_neta ./configure \ --enable-overwrite \ --prefix=/usr \ --exec-prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var/lib \ --enable-redhat \ --enable-timelord \ --enable-cups \ --with-did=cnid \ --with-db3=/usr \ --with-pam \ --with-shadow \ --with-tcp-wrappers \ --with-ssl-dir=/usr \ --enable-fhs \ --with-gssapi=/usr/kerberos/include \ --enable-krb4-uam \ --enable-krbV-uam \ --with-mutex="x86/gcc-assembly"
You're gonna need openssl-devel, krb5-devel, db4-devel, cups-devel packages installed for this set of compile options to work.
Craig
Steve
I just wanted to thank everyone for their input. I got NetATalk working last week, and finally tested it thoroughly yesterday, and it works like a charm.
Thanks
Steve Campbell
Steve Campbell wrote:
I have no need to use these original files other than to have them as a backup source for the originals.
I think I'm hearing everyone say just to mount my Centos partition on a Mac and copy them from the Thecus to the Centos partition.. Is that the concensus here? If so what, then, is the best way to export the Centos partition so that the Mac can access it?
Another possibility is to dd the drive.
johnn
Steve Campbell wrote:
Unfortunately, these are pre OS X files. They probably are more messed up than usual as they are 2003-2008 MultiAd Creator files. A lot of the fonts, font info, graphic stuff were placed in the meta files, and without those, they are useless without a lot of extra work to recreate the set of files.
The reason I feel the resource files are needed is that I started copying the files from the Thecus, and then rewrote them back to another area on the Thecus. I then tried to "explore" or view them on the Mac that originally wrote them with no success.
I have no need to use these original files other than to have them as a backup source for the originals.
I think I'm hearing everyone say just to mount my Centos partition on a Mac and copy them from the Thecus to the Centos partition.. Is that the concensus here? If so what, then, is the best way to export the Centos partition so that the Mac can access it?
If you are building a new file server box from scratch, you might want to look at SME server from http://www.contribs.org. It is Centos-based and I think it still supports netatalk.
-
Craig White -
Craig White -
John R Pierce -
Johnny Tan -
Les Mikesell -
Steve Campbell