Re: Bash don't interpret ~ path with multiple options.

2018-06-04 Thread Greg Wooledge
On Sun, Jun 03, 2018 at 02:32:03PM -0400, Chet Ramey wrote: > On 6/2/18 10:08 PM, Jungsub Shin wrote: > > # mount -o remount,append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount > > > > mount failed with ~/test_aufs/ro1 path isn't exist message. > > So i try to debug with strace and i find out bash don'

Re: Bash don't interpret ~ path with multiple options.

2018-06-03 Thread Chet Ramey
On 6/2/18 10:08 PM, Jungsub Shin wrote: > When i try mount aufs, i find some problem with bash. > > # mount -o remount,append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount > > mount failed with ~/test_aufs/ro1 path isn't exist message. > So i try to debug with strace and i find out bash don't replace ~

Re: Bash don't interpret ~ path with multiple options.

2018-06-03 Thread L A Walsh
Bash will only replace '~' when it has a space before it and it is not in quotes. It also won't expand '~' if it has special characters in it. In your lines, the '~' after the equal won't be replaced but the one at the end should be. Jungsub Shin wrote: When i try mount aufs, i find some

Bash don't interpret ~ path with multiple options.

2018-06-03 Thread Jungsub Shin
When i try mount aufs, i find some problem with bash. # mount -o remount,append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount mount failed with ~/test_aufs/ro1 path isn't exist message. So i try to debug with strace and i find out bash don't replace ~ path to absolute path. So i try again with split o