Timeline for Can version control systems use the filesystem log to capture changes?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2015 at 13:37 | vote | accept | Milind R | ||
| Nov 4, 2015 at 8:35 | comment | added | gbjbaanb | You'd have to write such a thing as part of the filesystem driver - I doubt you'd have enough control over when the log was flushed to reliably use it for userland purposes. | |
| Nov 4, 2015 at 4:20 | comment | added | Milind R | Useful link, thanks. The very robustness seen there is what prompted me to wonder about piggybacking on it. So we can capture the operations happening in a local repository till the next commit, and then flush? | |
| Nov 3, 2015 at 12:01 | comment | added | gbjbaanb | @MilindR they do, but not forever - where would they keep them? You'd fill up your disk with journals. So they keep data in the transaction log file only until the data is flushed to disk, then the log is reset. See this page about NTFS journalling | |
| Nov 3, 2015 at 11:56 | comment | added | Milind R | I thought journaling file systems kept meticulous logs. Either way, a file system driver should work right? | |
| Nov 3, 2015 at 11:16 | history | answered | gbjbaanb | CC BY-SA 3.0 |