Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Ignoramus19611 <ignoramus19611@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Jul 2008 06:56:26 -0500
On 2008-07-29, Rahul <nospam@xxxxxxxxxxxxxx> wrote:
I tried going to /home/foouser/ and then doing a 'chown -R foouser *'
try
chown -R foouser ~foouser
by default * expansion does not see .* files
i
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!
--
Due to extreme spam originating from Google Groups, and their inattention
to spammers, I and many others block all articles originating
from Google Groups. If you want your postings to be seen by
more readers you will need to find a different means of
posting on Usenet.
http://improve-usenet.org/
.
- References:
- Prev by Date: Re: mysqld wont start...
- Next by Date: Re: mysqld wont start...
- Previous by thread: Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- Next by thread: Which linux distribution support l7-filter and ipp2p?
- Index(es):
Relevant Pages
|