Reading your blog seems Parallels Desktop 8 is incoming. So I want to ask what if this gonna be fixed in version 8? Would I be eligible for free update?
I've submitted 2 bug reports, one for this no symlinks issue, 2nd for bad AVX code execution, none were fixed so far, regardless of numerous updates.
Please at least try to be honest with us. Keep in mind that many of us are developers capable of writing VFS code.
I think this feature has low priority, because (1) most of your users are not pro/developers/engineers, so it doesn't matter for them (2) we have already paid for your product, so attractive features like Retina support are top on the list, because that can seduce new users and bring you profit. Anyway this only proves that you are no different from any other, you love us until we pay, then suddenly all your love is gone.
Going back to the subject, having symlinks is rather simple task for UNIX/driver developer. I'd do it myself if I had source-code for both host and guest code, all I have now is guest prl_fs code. But if you need guidelines, here they're:
(1) in order to provide symlink support you need to provide extra callback methods in prl_fs/SharedFolders/Guest/Linux/prl_fs/file.c symlink, follow_link, readlink in struct file_operations prlfs_file_fops and struct file_operations prlfs_dir_fops
(2) note symlink is just a TEXT, so both symlink and readlink need just pass the supplied buffer to/from host functions with same name at given path (resolved similarly as in prlfs_open). Not hard at all!
(3) follow_link may be just a little more complicated, because it should follow link relatively to guest, still I do not see anything hard there!
I've submitted 2 bug reports, one for this no symlinks issue, 2nd for bad AVX code execution, none were fixed so far, regardless of numerous updates.
Guys,
we do care actually - it's really hard to implement in current realization of shared folders, but we're investigating the thing. Sorry for inconvenience.
Please at least try to be honest with us. Keep in mind that many of us are developers capable of writing VFS code.
I think this feature has low priority, because (1) most of your users are not pro/developers/engineers, so it doesn't matter for them (2) we have already paid for your product, so attractive features like Retina support are top on the list, because that can seduce new users and bring you profit. Anyway this only proves that you are no different from any other, you love us until we pay, then suddenly all your love is gone.
Going back to the subject, having symlinks is rather simple task for UNIX/driver developer. I'd do it myself if I had source-code for both host and guest code, all I have now is guest prl_fs code. But if you need guidelines, here they're:
(1) in order to provide symlink support you need to provide extra callback methods in prl_fs/SharedFolders/Guest/Linux/prl_fs/file.c symlink, follow_link, readlink in struct file_operations prlfs_file_fops and struct file_operations prlfs_dir_fops
(2) note symlink is just a TEXT, so both symlink and readlink need just pass the supplied buffer to/from host functions with same name at given path (resolved similarly as in prlfs_open). Not hard at all!
(3) follow_link may be just a little more complicated, because it should follow link relatively to guest, still I do not see anything hard there!