summaryrefslogtreecommitdiff
path: root/doc/forum/parted:_invalid_token:_fat
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/parted:_invalid_token:_fat')
-rw-r--r--doc/forum/parted:_invalid_token:_fat/comment_1_0ad5e1df0db6dbdaba298f5f890d79a2._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/parted:_invalid_token:_fat/comment_1_0ad5e1df0db6dbdaba298f5f890d79a2._comment b/doc/forum/parted:_invalid_token:_fat/comment_1_0ad5e1df0db6dbdaba298f5f890d79a2._comment
new file mode 100644
index 00000000..b859054d
--- /dev/null
+++ b/doc/forum/parted:_invalid_token:_fat/comment_1_0ad5e1df0db6dbdaba298f5f890d79a2._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-12-20T16:52:30Z"
+ content="""
+Your change seems right. I think the mount error is unrelated;
+it comes from DiskImage which mounts the loopback device with
+-t auto, so the parted name for fat shouldn't impact that.
+
+There might be something in dmesg about why the mount failed.
+"""]]