sidney
4th July 2004, 03:21 PM
I was using a Redhat 9 server to mount hfs cdrom iso images, serving them using netatalk to Macs running MacOS9. The entries in /etc/fstab used the afpd option of hfs which was necessary to get the resource forks to properly get to netatalk. Without the afpd option, the macs would not see the resource forks of the files.
I replaced the OS with a fresh install of Fedora Core 2. The hfs driver in the 2.6 kernel no longer has the afpd option. I found this comment on a kernel mailing list that said
"The HFS driver got a major cleanup and a lot of broken options were removed, most notably if you want to continue using netatalk with this driver, you have to fix netatalk first."
http://www.kerneltraffic.org/kernel-traffic/kt20031026_236.html#6
The version of netatalk that comes with Fedora Core 2 is 1.6.4, the latest stable version. The changelog for it mentions kernel 2.6 and is a few months more recent than the above comment.
Has anyone used a 2.6 kernel for serving an hfs cdrom to a classic Mac and if so, how did you do it?
[update] I installed netatalk version 2.0 beta 2 from sources and got the same result.
I replaced the OS with a fresh install of Fedora Core 2. The hfs driver in the 2.6 kernel no longer has the afpd option. I found this comment on a kernel mailing list that said
"The HFS driver got a major cleanup and a lot of broken options were removed, most notably if you want to continue using netatalk with this driver, you have to fix netatalk first."
http://www.kerneltraffic.org/kernel-traffic/kt20031026_236.html#6
The version of netatalk that comes with Fedora Core 2 is 1.6.4, the latest stable version. The changelog for it mentions kernel 2.6 and is a few months more recent than the above comment.
Has anyone used a 2.6 kernel for serving an hfs cdrom to a classic Mac and if so, how did you do it?
[update] I installed netatalk version 2.0 beta 2 from sources and got the same result.
