Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Rahul <nospam@xxxxxxxxxxxxxx>
- Date: Tue, 29 Jul 2008 23:44:32 +0000 (UTC)
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...)
--
Rahul
.
- Follow-Ups:
- Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Chris Davies
- Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Florian Diesch
- Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Robert Heller
- Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- From: Maxwell Lol
- Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- References:
- Prev by Date: Re: Which linux version
- Next by Date: Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
- 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
|