From 98d9f5ea263e29052decd37c47824ec963e3e0b6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebasti=C3=A3o=20Ribeiro=20Monteiro=20Filho?= Date: Fri, 16 Aug 2024 01:09:15 -0300 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 09ba117..b91766a 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ The shareware limitation is only imposed on the tool(zicroram) side; which means - For those who are under Security-Enhanced Linux (SELinux), you can still normally use the program, however if you(or the system) ever makes any changes to SELinux metadata features for a given specific data, those changes can't be detected as of yet and therefore not backed up from ram to disk on user request when using '--mmbackup', '--mtbackup', '--checks', '--mmremove'. Any other types of changes will be detected and backed up normally. -- Reflink file support is non-existent; currently, neither TMPFS nor RAMFS supports CoW/Reflink data; in other words as of this date it'd be impossible to give it support today. However, this is only a problem when doing DATA BACKUPS using '--mmbackup', '--mtbackup', '--mmremove' after changing/editing/updating the reflinked file in RAM. If no editing of reflinked files takes places, then doing DATA BACKUPS isn't a problem and should be fine. +- Reflink file support is non-existent; currently, neither TMPFS nor RAMFS supports CoW/Reflink data; in other words as of this date it'd be impossible to give it support today. However, this is only a problem when doing DATA BACKUPS using '--mmbackup', '--mtbackup', '--mmremove' after changing/editing/updating the reflinked file in RAM. If no editing of reflinked files takes place, then doing DATA BACKUPS isn't a problem and should be fine. **About Current Limitations:** About reflinks/CoW'd files not being supported on TMPFS/RAMFS, there's nothing that can currently be done.