Date: Thu, 9 May 1996 11:09:34 -0500 (CDT) From: Dan Nelson <dan@dan.emsphone.com> To: freebsd-questions@FreeBSD.org Subject: Re: Please Help ... I am locked out of a FreeBSD machine Message-ID: <199605091609.LAA25050@dan.emsphone.com> In-Reply-To: <199605090333.NAA01970@genesis.atrad.adelaide.edu.au> from "Michael Smith" at May 9, 96 01:03:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
in the last episode, Michael Smith said: > James Raynard stands accused of saying: > > > Branson> chmod 644 -R .??* > > > > I prefer chmod 644 -R .[a-zA-Z]* myself > > > > > Branson> the '?'s will require two characters in the file > > > Branson> name.. not just one which very effectively skips '.' and > > > Branson> '..'. > > > > > > But it unfortunately misses all entries with a name of . followed by a > > > single character: .a, .b, .c, etc. But, hey, close enough! Do those > > > by hand, I say! > > > > You forgot the upper case ones 8-) > > # chmod 644 -R .[^.]* I've been wondering what you all were talking about, since on my machine, "echo .*" does NOT list "." or "..". I checked the man pages for zsh, and sure enough, under "FILENAME GENERATION (GLOBBING)", I see: No filename generation pattern matches the files "." or "..". Can ash maybe be patched to do this also? I can't think of a case where you would EVER want to match '.' or '..' in a wildcard. -Dan Nelson dan@dan.emsphone.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605091609.LAA25050>