Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.

Rahul <nospam@xxxxxxxxxxxxxx> wrote:

Allen Kistler <ackistler@xxxxxxxxx> wrote in
news:e6Njk.15713$xZ.11898@xxxxxxxxxxxxxxxxxxxx:

You're not missing anything.
That's the design.
It keeps you from changing the current directory, the parent
directory, and (in the case of -R) all the children of the parent
directory.


Ah! That explains the mess I created then! :-(

I tried a 'chown -R foouser .*' and screwed up tons of user permissions
since it acted on the .. dir too which wasn't the way I intended. My stupid
mistake.

But then again: how does one tackle dirs of the sort .ssh/ .vim/ etc.? If
these also reside under /home/foouser and I want to chown them don't I need
to have a way to wildcard them? (by going up one level and doing a chown -R
foouser /home/foouser/ seems an option...)

chown -R .
chowns recursively everything in your current working dir.

In some shells you can configure how . is handled when expanding
*. For bash have a look for dotglob in the bash manpage.


Florian
--
<http://www.florian-diesch.de/>
-----------------------------------------------------------------------
** Hi! I'm a signature virus! Copy me into your signature, please! **
-----------------------------------------------------------------------
.