.sync.ffs_db vs. sync.ffs_db

Discuss new features and functions
Posts: 16
Joined: 11 Mar 2010

arneko

Dear Zenju,
I am using FFS sync quite happily in a multiplatform environment (Linux and Windows, that is. I often miss it when working on a mac though)
As a multiplatform user, something that bugs me is, why many programs choose
-files marked as invisible on win Platforms
-files with a dot as first symbol on *nix systems
(that is true for many programs, not just FFS)

for their configuration files, databases etc.

In my opinion, it would be quite simple to do both:
-put a dot in front
-mark it as invisible
(at least on MS-filesystems, since I am quite positive that you can't mark anything as invisible on *nix filesystems)
While I am not sure if *nix implementations of FAT or NTFS support marking a file as invisible, I am pretty sure that Windows supports naming files with a dot as first symbol.

So why the hassle of having different names? In the past that seemed to make sense, since FFS used different formats for Linux and Win (+32vs64 bit!), but if I understood your changelog correctly that isn't true anymore.

So is there a deeper reason behind this that I cannot grasp, or is it just the legacy of darker times? If so, I would welcome the switch to .sync.ffs_db on all platforms. Even if Linux users might be the only ones who benefit from that...


Thanks for the great program!

Arne
User avatar
Site Admin
Posts: 7212
Joined: 9 Dec 2007

Zenju

The 32 and 64 bit file format were unified some time ago. But there are at least these differences between Windows and Linux: Latter contains case-sensitive file names, former case-insensitive. The optional file id representations may be different for the same files mounted unter both OSs.
Posts: 16
Joined: 11 Mar 2010

arneko

The 32 and 64 bit file format were unified some time ago. But there are at least these differences between Windows and Linux: Latter contains case-sensitive file names, former case-insensitive. The optional file id representations may be different for the same files mounted unter both OSs.Zenju
Point taken. Though I must say, the implications of case sensitivity vs. insensitivity are just mind boggling in a multi-platform environment. Gives me a headache.
Simply astonishing... :-)