"J. R. Okajima":
> I don't think these are bugs since they are following "Dashism" instead
> of "Bashism." I understand that debian has a policy to be
:::
It may not be important anymore, but I've just found that I was
confusing. And I think it may be better to post again.
For "echo \t" in aubusy, it was already converted to printf in 2014.
Here is the past commit in aufs-util.git.
J. R. Okajima
commit 128319896a3ba2b2a234eb7e283dcbe5a3671d36
Author: J. R. Okajima <[email protected]>
Date: Sun Mar 23 22:19:44 2014 +0900
bugfix: convert a few "echo"es to "printf"s
While UNIX standards (IEEE Std 1003.1) describes that "echo" command
interprets the backslash sequence unless "-n" is specified, some major
shells don't.
Convert them to "printf".
Reported-by: Guan Xin <[email protected]>
Signed-off-by: J. R. Okajima <[email protected]>
diff --git a/aubusy b/aubusy
index b8408fa..7873e7f 100755
--- a/aubusy
+++ b/aubusy
@@ -27,9 +27,9 @@ test $# -ne 2 &&
{
echo Invalid argument
echo Usage: $(basename $0) '[-v]' aufs_mntpnt branch_path
- echo '\tprint PIDs which make the branch busy and un-removable.'
- echo '\t-v prints additional information, the inode number in aufs,'
- echo '\tthe branch index, and the actual inode number on that branch.'
+ printf '\tprint PIDs which make the branch busy and un-removable.\n'
+ printf '\t-v prints additional information, the inode number in aufs,\n'
+ printf '\tthe branch index, and the actual inode number on that
branch.\n'
} 1>&2 &&
exit 1
