Your message dated Fri, 22 Nov 2013 14:25:42 -0500
with message-id <[email protected]>
and subject line Accidental extra word in ext4 section of mount man page
has caused the Debian Bug report #599550,
regarding Accidental extra word in ext4 section of mount man page
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
599550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599550
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mount
Version: 2.17.2-3.2
Severity: minor
>From the ext4 section of the mount man page:
"Many broken applications don't use fsync() when noauto_da_alloc replacing
existing files via patterns such as"
It looks like the "noauto_da_alloc" got in there because the text was pasted
from the Linux kernel ext4 documentation which included the option names in a
different column.
Francis
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35.7 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mount depends on:
ii libblkid1 2.17.2-3.2 block device id library
ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libsepol1 2.0.41-1 SELinux library for manipulating b
ii libuuid1 2.17.2-3.2 Universally Unique ID library
mount recommends no packages.
Versions of packages mount suggests:
pn nfs-common <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Version: 2.20.1-5
Looks like this got fixed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSj6+2AAoJEJrBOlT6nu75ao8H/icWntRgEh0EQnAlnwcU5X9U
lLV8lhr3WKqKQaHa62BQu/zWNmciVT8r3bs65cePn4rls92zMQxAt13IZLUpxjLy
H8KK3faJ6DB+Hga+om3hdZqa+B8rMdHiVpyQY4o/MD61pFd5KNt1GHMt4AIki11a
0HWA6dOMnCyAmGyUa+ZKh+y+QnRrygCuzG5vL6/1hzZ5VAY6uJpS4QpGDaNoz2g4
+U9HwrLsEtVDfreav38VK7Hx0NvjqQJv5/7Nz97TzAs/9Kel9fzwLzJElk1LGVdN
z1ftYVp+VI9bN0SYBpmwFfbRPBbLRyo2PKBTt8geZLaYA08MHZBz2BDz1Mx211M=
=tiW1
-----END PGP SIGNATURE-----
--- End Message ---
