Bob Proulx wrote:
I generally dislike combining the functionality of several different
commands into one command. In this case combining mkdir and chmod and
I don't see any reason they can't be used individually. Plus mkdir
already allows you to create directories with a specified
Hi Bob,
I was using exactly that shell function that you described, but it
doesn't work for
mkdir -p foo/bar
I'm using the alias you gave, which works better. Thanks.
I've noticed one issue, which I feel is a bug in mkdir. When using mkdir
-pm, the specified mode is applied only to the
Hi
I'm not sure, but I think I found a bug in sha1sum. It's easy to
reproduce with any file that contains a backslash (\) in the name:
echo test test
$ sha1sum test
4e1243bd22c66e76c2ba9eddc1f91394e57f9f83 test
$ mv test 'test\test'
$ sha1sum 'test\test'
Theo Band writes:
Hi
I'm not sure, but I think I found a bug in sha1sum. It's easy to
reproduce with any file that contains a backslash (\) in the name:
echo test test
$ sha1sum test
4e1243bd22c66e76c2ba9eddc1f91394e57f9f83 test
$ mv test 'test\test'
$ sha1sum 'test\test'
Hi.
When doing something like:
cp --no-dereference --preserve=all --parents --no-clobber ${pathname}
${destination}
Then the file (if it's not a directory) will be copied to
${destination}/${pathname} including all the directories within ${pathname}
(e.g. ./foo/bar/file).
While the owner
On 05/30/11 10:29, Shaun Jackman wrote:
When using mkdir
-pm, the specified mode is applied only to the final directory and not
the parent directories
That behavior is required by POSIX; see
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/mkdir.html.
Perhaps an argument could be
