I have an Ubuntu based file server that i have setup, or so i thought, that would allow macs/linux and windblows machines to view and edit files.
on the mac, the native file browser has no problem reading and accessing the file server files. the file browser on bibble seems to only want to open directories which have the apple double store stuff in it. that is the :2eds..... files. what is going on? the only way for bibble to see a directory is to have had the mac create it and for me to copy files to it.
is this a 'feature'? is there some setting the mac or the AFP code on the file server to allow bibble to see the files?
is this 'feature' also part of the aftershot pro versions? i have tried the aftershot pro initial release on linux and they remove the 'perfectly clear' feature, which i use a lot. i haven't loaded the aftershot pro on the mac because of that.
any suggestions here?
file browser on mac with network drive
-
afx
- Posts: 1675
- Joined: Thu Jan 12, 2012 1:38 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- Video Card: FirePro 4900
- Monitor/Display Make & Model: NEC PA301w, ColorMunki
- Location: München
- Contact:
Re: file browser on mac with network drive
AS still has Perfectly Clear.
No idea about the mac, but user user mounted stuff on Linux is not visible because of the silly .gfs mount point which is a hidden directory because of the ".". Using regular mounts on Linux works just fine.
You also might want to experiment with CIFS and NFS mounts instead of AFP.
cheers
afx
No idea about the mac, but user user mounted stuff on Linux is not visible because of the silly .gfs mount point which is a hidden directory because of the ".". Using regular mounts on Linux works just fine.
You also might want to experiment with CIFS and NFS mounts instead of AFP.
cheers
afx
Send bugs to the Monkey // AfterShot Kickstart Guide // sRGB clipping sucks and Adobe RGB is just as bad
Bibble since 2005 // W7 64 on quad Phenom // Ubuntu 14.4 on quad i7 and dualcore AMD // Images
Bibble since 2005 // W7 64 on quad Phenom // Ubuntu 14.4 on quad i7 and dualcore AMD // Images
-
ktom
- Posts: 3
- Joined: Sat Mar 31, 2012 3:16 am
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- motherboard: giga byte ma785g
- processor: AMD
- ram: 4GB
- Video Card: nvidia
- Hard_Drive_Capacity: 500G
- Monitor/Display Make & Model: dell 24wfp
Re: file browser on mac with network drive
thanks for the response!!
I am not sure what you are referring to with the .gfs statement. The filesystem was created and a regular NFS file system not as an AFP.
the mount point as defined in fstab is:
/dev/md0 /data ext3 noatime,rw 0 0
it is exported normally as well.
/data -sync,rw,subtree_check
pretty standard as far as i know.
My understanding of the AFP implementation is that it is 'rider' so to speak on the standard linux filesystem. I am the least familiar with the way the mac filesystems work and hence the options that the AFP implementation is meant to provide. The mac created directories alway have this file " :2eDS_Store" and the .AppleDouble file.
I am looking for clues as to why bibble can't write to the file system while the standard mac file browser can. bibble can view access the file system normally.
any mac experts out there?
i will load the AS to see if i can find the perfectly clear. thanks.
I am not sure what you are referring to with the .gfs statement. The filesystem was created and a regular NFS file system not as an AFP.
the mount point as defined in fstab is:
/dev/md0 /data ext3 noatime,rw 0 0
it is exported normally as well.
/data -sync,rw,subtree_check
pretty standard as far as i know.
My understanding of the AFP implementation is that it is 'rider' so to speak on the standard linux filesystem. I am the least familiar with the way the mac filesystems work and hence the options that the AFP implementation is meant to provide. The mac created directories alway have this file " :2eDS_Store" and the .AppleDouble file.
I am looking for clues as to why bibble can't write to the file system while the standard mac file browser can. bibble can view access the file system normally.
any mac experts out there?
i will load the AS to see if i can find the perfectly clear. thanks.