stewartsmith/libeatmydata
View on GitHub ↗ ★ 500 C
libeatmydata - because fsync() should be a no-op
11 mentions on Hacker News by 11 people: 4 stories, 7 comments · first 2017-12-04 · latest 2025-10-14
20082026
-
▲ 1
Eatmydatastory by limbicsystem · 2025-10-14 · 0 comments
-
▲ 2
libeatmydata – because fsync() should be a no-opstory by tosh · 2024-09-17 · 0 comments
-
▲ 2
Libeatmydata – because fsync() should be a no-opstory by eatonphil · 2023-04-03 · 0 comments
-
▲ 2
Libeatmydata – because fsync() should be a no-opstory by harporoeder · 2021-04-12 · 0 comments