From 4e8cd3321ba77720e3ebd73f743beacd7be97566 Mon Sep 17 00:00:00 2001 From: elmimmo Date: Mon, 4 Feb 2019 00:26:41 +0000 Subject: [PATCH] --- ...x_with_dumb_FAT32_devices_not_a_valid_use_case__63__.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/Git-annex_with_dumb_FAT32_devices_not_a_valid_use_case__63__.mdwn diff --git a/doc/forum/Git-annex_with_dumb_FAT32_devices_not_a_valid_use_case__63__.mdwn b/doc/forum/Git-annex_with_dumb_FAT32_devices_not_a_valid_use_case__63__.mdwn new file mode 100644 index 0000000000..fed743e3f8 --- /dev/null +++ b/doc/forum/Git-annex_with_dumb_FAT32_devices_not_a_valid_use_case__63__.mdwn @@ -0,0 +1,5 @@ +Am I right in concluding that using an array of limited storage devices that require FAT32 is not a valid use case for git-annex? + +Dumb devices that require FAT32, that need all present files to be unlocked in order to not choke on them (i.e. unlike with git-annex’ text-files-as-symlinks on crippled filesystems), that also therefore need missing files to be hidden, and that are storage space-constrained, I would say are extremely common. Yet, if I understood correctly, v7 repos are required for being able to hiding missing files, but at the same time, on v7 and FAT32 filesystems, files that are present take up double their file size. + +Am I right, or I am missing a way to use those?