Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: "s. keeling" <keeling@xxxxxxxxxxx>
- Date: Wed, 30 Jul 2008 02:01:06 +0200 (CEST)
Allen Kistler <ackistler@xxxxxxxxx>:
Rahul wrote:
I tried going to /home/foouser/ and then doing a 'chown -R foouser *'
It seems to change the ownership recursively for all dirs and files under
/home/foouser/ except those starting with a . (dot)
Is this behaviour of the * wildcard by design or am I just missing
something here? I'm confused!
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.
Yes, and the OP's answer is:
chown -R foouser /home/foouser
acting on the dir and children, whatever they may be. "." is special
in *nix shell, as are many other characters. Learning the bash shell
from O'Reilly is a smooth intro, and your distro may offer some
already installed (bash-doc and abs-guide in Debian).
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.
.
- References:
- Prev by Date: Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- Next by Date: Re: Which linux version
- Previous by thread: Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- Next by thread: Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- Index(es):
Relevant Pages
|