Copying files from x86 to ppc

I

info1686

Registered
Hi all,
I am trying to move some files from an x86 machine to a ppc machine. Both are running Mac OS X 10.4
The files have some extended attributes set for them.
Hence, I used the tar utlity to create an archive and then moved the archive.
However, the file data is moved correctly but all the extended attributes are lost
Why is this?
I learnt that all extended attributes are stored in the resource fork.
Both the machines have the HFS+ filesystem.
Hence, even the resource forks must get copied right?

Thanks....
 
Why didn't you use the MacOS X built-in ZIP facility? You could have also simply networked the two computers and skipped the archive step.
 
Yes, why not? The disk image should be HFS+ (Mac OS Extended) formatted. This will preserve the files as they are. Make sure both OSs are 10.4.11 fully updated as well.
 
No I mean just as a regular file not as a disk image..
Just moving a regular file from x86 to ppc machine ( both Mac OS X ). Do the extended attributes stay or are lost?
 
If you move a file from a Mac to a Mac the resourceforks and other data bound to the files are kept.
Unless you copy them with Terminal (and if you do use Terminal, and use cpmac instead of cp they are kept).

What files are they? Anything for system or library? Anything for a cpu specific program or a driver? What particular attributes are lost?
 
They are just regular files.
I had some some extended attributes like user.name and some ACL's
They are lost
for ex :
consider a file 1.txt
I created a tar archive of this file arc.tar
The tar contained 2 files 1.txt ._1.txt
Then I transferred the files to another machine (ppc ) using FTP
When I extracted the archive there, all attributes set are gone
Only the data stays.
I read that ._1.txt holds the resource fork information
 
Like I said: Create a HFS+ disk image, copy the files to it in Finder, transport disk image to destination, mount disk image, copy files to where you want them, all attributes are preserved correctly.
 
File systems supporting ACLs

Access Control Lists can only be used on file systems which are capable of storing them. Mac OS X allows the usage of ACLs for the following types of file systems, if the computers hosting these file systems are using an operating system version compatible with ACLs:

disk volumes formatted with the Mac OS Extended file system (HFS+),
network volumes accessed via the Apple Filing Protocol (AFP, AppleShare)
network volumes accessed via the SMB/CIFS Protocol (Microsoft® Windows).

Other file systems, including disk volumes formatted using UFS, FAT, VFAT, FAT32, or NTFS, and network volumes accessed via NFS, FTP, or WebDAV cannot support Access Control Lists. link
 
You must log in or register to reply here.
Back
Top