From 904ccd1641e5cc187ef0ca65e929687756e9a1b6 Mon Sep 17 00:00:00 2001
From: "http://schnouki.net/" <Schnouki@web>
Date: Fri, 29 May 2015 12:20:09 +0000
Subject: [PATCH] Added a comment

---
 .../comment_3_17752e96baaf46f3048b14a9ec288e3b._comment   | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/devblog/day_288__microrelease_prep/comment_3_17752e96baaf46f3048b14a9ec288e3b._comment

diff --git a/doc/devblog/day_288__microrelease_prep/comment_3_17752e96baaf46f3048b14a9ec288e3b._comment b/doc/devblog/day_288__microrelease_prep/comment_3_17752e96baaf46f3048b14a9ec288e3b._comment
new file mode 100644
index 0000000000..b6e65a9293
--- /dev/null
+++ b/doc/devblog/day_288__microrelease_prep/comment_3_17752e96baaf46f3048b14a9ec288e3b._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://schnouki.net/"
+ nickname="Schnouki"
+ subject="comment 3"
+ date="2015-05-29T12:20:08Z"
+ content="""
+A while ago I needed a tool to emulate slow IO (low bandwidth and high latency). I ended writing a small FUSE driver (in Go, just for fun) that did this by adding some delay to each function call. Hacky, but simpler than setting up a device mapper or NBD. I guess you could also emulate IO errors with something like this. If you're interested I can clean up my code and push it to a public repo.
+"""]]