home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!news.dell.com!uudell!pensoft!usenet
- From: stecz@pencom.com (John Steczkowski)
- Newsgroups: comp.unix.shell
- Subject: Re: Help using find with wildcards
- Message-ID: <1992Dec31.142249.11102@pencom.com>
- Date: 31 Dec 92 14:22:49 GMT
- References: <1992Dec31.043445.2794@mnemosyne.cs.du.edu>
- Sender: usenet@pencom.com (Usenet Pseudo User)
- Reply-To: stecz@pencom.com
- Distribution: austin
- Organization: Pencom Software
- Lines: 27
-
- In article <1992Dec31.043445.2794@mnemosyne.cs.du.edu> jefouger@nyx.cs.du.edu
- (Jim Fougeron) writes:
- > markn@ssd.comm.mot.com (Mark Nowak) writes:
- >
- > >Anybody know how to find files, directories, etc. when you
- > >don't know the exact name of the file you're looking for.
- > >For example, I'm looking for file abcde in some directory
- > >tree, but the only characters I know for sure are bcd. Is
- > >there a wat to use find to locate this file?
- >
- > >I'm thinking of something along the lines of:
- >
- > >find . -name *bcd* -print
- >
- > try: find . -name \*bcd\* -print
- >
- > >but that doesn't work.
-
- also try: find . -name "*bcd*" -print
-
- That is how I normally do it, and it works on many different UNIXes.
-
- --
- --
- John Steczkowski stecz@pencom.com
- "Achilles raised his spear, took careful aim, and hurled."
- from the Iliad
-