caja should display 'birth' of files/folders

[mabra]

Expected behaviour

Righ click on a file or folder The dialog appears AND shows even the birth of a file

Actual behaviour

no birth of file/dir is shown

Steps to reproduce the behaviour

MATE general version

Package version

debian(bullseye), caja: 1.24.0-1

Linux Distribution

debian bullseye

Link to bugreport of your Distribution (requirement)

This will probably a very easy change and make the birth of files/folders visible - birth does not exist on extX, but on zfs, for example.

[lukefromdc]

ZFS isn't even supported on many Linux distros due to license issues

[mabra]

Creation timestamps were not only forseen since about 2007, nut already present in the following fileystems: CP/M, DECtape,Level-D, RT-11,exFAT, FAT12, FAT16, FAT32, HPFS, ReFS, HFS, HFS Plus, UFS2, HAMMER, ext4, NOVA, F2FS, GPFS, NILFS, JFS, QFS, BFS, NSS, NWFS, ODS-5, APFS, UDF, ZFS, Btrfs, ISO 9660, Joliet, High Sierra, BlueStore/Cephfs. I stopped my move to Linux (someday very early) and my first fileserver came into the house, since samba implemented this via extended attributes - so I was able to keep my development files, which reach back to 1986 .... Is'nt it a wonder, that everythings today uses timestamps (see certificates), but Linux still keeps ignorant even against it's own rules?

[Yetoo1]

@mabra In Caja 1.26.1 I can see creation date that corresponds to stat Birth when viewing file properties. Additionally, birth does exist on ext4 but it's not supposed to change without debugfs. I say not supposed to because I have experienced birth times changing if merely accessing the file after a long time. Other open source filesystems including OpenZFS have the problem of having birth time but not being able to change it easily such that it would actually be useful. You can't see birthtime with kernel version before 4.11 because kernel system call didn't expose it. 4.11 introduced statx in June 2017 and stat from coreutils introduced it in October to late 2019/early 2020 (not sure the exact version) (so regular end user able to access it from this point). I share the frustration with fragile and limiting filesystem behavior though.

[mabra]

Thank you for this lot of information and the future of caja. I am just bound to caja 1.24 (from debian/bullseye repo). Nearly all my filesystems are ZFS and I can - for a single case - use stat to see birth. I am installing ZFS inside (K)VMs, because no "passthrough" filesystems support it.