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

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!

--
Rahul
.

Relevant Pages

  • Re: confusing behaviour of the * wildcard when handling "dot" files and dirs.
    ... It seems to change the ownership recursively for all dirs and files under ... Is this behaviour of the * wildcard by design or am I just missing something here? ... It keeps you from changing the current directory, the parent directory, and all the children of the parent directory. ...
    (comp.os.linux.misc)
  • Re: Norvig on Lisp vs Python revised
    ... > be similarly missing things for Python but not knowing the language I ... design and evolution of a programming language. ... various versions of the HOPL-2 paper (well over a dozen reviews) was ...
    (comp.lang.lisp)
  • Re: Read Only Users
    ... > No, Dan, you're not missing anything. ... > MS will change the design. ... When they try to save it brings up a windows logon box asking ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Problem with locked files - solved (inheritable handles)
    ... Sorry, Don, but you are missing the most important point, which in my view is how one might solve Dylan's specific ... also look back at the original post, Dylan states, "The secondary process does need to inherit some handles (because I ... still think that my suggested change to the crt would accomodate Dylan's design. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: unable to find platform.bib
    ... just copy the file from the BSP. ... this occurs early in the creation of your OS design. ... prevent it's pre-processing and results in a missing output file. ... (l'indirizzo di reply di questo messaggio non è ...
    (microsoft.public.windowsce.platbuilder)