Double slash is more a URL thing; in UNIX FS it may be ignored or raise an error: no upside I have heard. Happens sometimes if you specify a dir with a trailing slash, like "find /tmp/" as I recall. A trailing slash is a file wildcard accessory to find just directories, and should be gracefully ignored.
You can specify new_child_dir if you only run it once, but if you run it twice, you get /a/b/c and /a/b/c/c, so always specify the new parent dir, and it cannot move.
Last edited by DGPickett; 11-27-2010 at 11:36 AM..
What is the difference between single and slash here and in general?
The extra slash is probably ignored.
Quote:
How to copy if we have a unique directory somewhere? Is some of above ways more prefered or... better solutions exists???
I'm not sure what you're asking. To copy into a directory you'd use copy. are you concerned about copying a directory into a place where something of that name might already exist?
In some early unixes the trailing "/" in "find" meant "follow links". I still type it out of habit, though you now need the "-follow" switch with "find". I don't recall a special meaning to "//" in the middle of a path.
What is the difference between single and slash here and in general?
How to copy if we have a unique directory somewhere? Is some of above ways more prefered or... better solutions exists???
Moderator's Comments:
use code tags, please!
I guess, its usually ignored by the bash. Its there, where I too have observed similarly, specially while specifying paths (in Linux commands) when mis-typed to put multiple / (i.e. // or even /// )
My feeling has been that bash parses them to make only one '/' in the command parameters. There is no difference otherwise. It's just a feature in bash not available in other older shells like sh, where, I hope, you'd get an error for such mis-types.
I guess, its usually ignored by the bash. Its there, where I too have observed similarly, specially while specifying paths (in Linux commands) when mis-typed to put multiple / (i.e. // or even /// )
My feeling has been that bash parses them to make only one '/' in the command parameters. There is no difference otherwise. It's just a feature in bash not available in other older shells like sh, where, I hope, you'd get an error for such mis-types.
Actually, AFAIK, system calls such as open(2) ignore consecutive slashes. I don't think this has anything to do with shells, and I wouldn't expect a shell to modify or complain about consecutive slashes.
In the awk I am trying to subtract the difference $3-$2 of each matching $4 before the first _ (underscore) and print that value in $13.
I think the awk will do that, but added comments. What I am not sure off is how to add a line or lines that will add sum each matching $13 value and put it in... (2 Replies)
Hi ..
I am trying to create one function.
It will have two arguments.
Argument1: a,b,d,f,g
Argument2:21212,sfsd,4546,67867,a,asda,b
So the output will be Argument1 - Argument2
which is d,f,g
Can anyone help with this one? (4 Replies)
I think both write at the end of the file ......
but is there a sharp difference between those 2 instruction .....
thank you
this is my 3rd question today forgive me :D (1 Reply)
just wondering what the difference is between 1,$ and /g when doing a substitution in vi. doesn't seem to be much difference from what i can see. (2 Replies)
Hello
I would like to know where there is a difference between these two machines?
HP9000-735/125
HP9000-B132L
What does that all mean?
Okay, HP= Hewlett Packard
But 9000, 725/125, B132L ????
I am asking that question because I am about to buy one for myself, so I can have some fun... (3 Replies)
11-26-2010
