-
Notifications
You must be signed in to change notification settings - Fork 286
Time to mark as deprecated? #217
Comments
It's stable. If you are using it within operating parameters then it works fine and will continue to work fine. |
Thank you @JakeWharton! Do you know if it should be used on F2FS devices? I'm trying to figure out if F2FS supports "atomic segment writes", as I am not seeing much information on that concept on the web. |
I personally do not. I've only worked on and maintained the higher-level APIs surrounding the low-level behavior on the file system. I was not involved in the research that went into guaranteeing the correct semantics were available. This library is something like 13 years old at this point. |
@eburke - do you have any knowledge of any other file systems besides YAFFS/YAFFS2 that support "atomic segment writes"? Does that concept have another or more encompassing name? I'm not seeing much information on that concept on the web. cc @jaegeuk - do you know if F2FS supports "atomic segment writes"? |
Eric is retired. I can only hope he has disabled all notifications from GitHub and will never see this. |
IIRC @crazybob would be better to ask. Honestly I'm not sure any of us ever followed up on that, we just noticed it was likely not as valid under ext4 but it still functioned so we left it. |
Given that there are stale issues, PR's, no updates, and it doesn't work without possibility for corruption on almost all modern filesystems (eg ext4), is it time to mark this project as deprecated?
The text was updated successfully, but these errors were encountered: