Mdthbs

Why limit to revolvers?

Is it rude to tell recruiters I would only change jobs for a better salary?

Align by center of symbol

Cubic programming and beyond?

Remove intersect line for one circle using venndiagram2sets

School House Points (Python + SQLite)

How would someone destroy a black hole that’s at the centre of a planet?

What are some symbols representing peasants/oppressed persons fighting back?

Add region constraint to Graphics

As a DM, how to avoid unconscious metagaming when dealing with a high AC character?

Is killing off one of my queer characters homophobic?

Construct a pentagon avoiding compass use

How do I define this subset using mathematical notation?

How did John Lennon tune his guitar

Why are Japanese translated subtitles non-conversational?

Crab Nebula short story from 1960s or '70s

Are villager price increases due to killing them temporary?

How to draw a gif with expanding circles that reveal lines connecting a non-centered point to the expanding circle using Tikz

How to determine port and starboard on a rotating wheel space station?

Can a continent naturally split into two distant parts within a week?

Why does the Earth have a z-component at the start of the J2000 epoch?

Why use null function instead of == []

Do native speakers use ZVE or CPU?

How can we better understand multiplicative inverse modulo something?

What is the Linux equivalent of DOS “dir /s /b filename”?

Detecting pattern at the end of a line with grepWhat is the Unix (QNX) equivalent of Windows command line “dir /s /b”List files larger than {size} sorted by dateDiffering outputs of the commands “ls .*” and “ls *.”Listing directories and understanding lsWhat is the alternative for ls command in linux?How to sort files by part of the filename?Move files only if filename based regex does not match file in target dirWhat does a red-colored filename mean?What is the Unix (QNX) equivalent of Windows command line “dir /s /b”ls listing directory argument does not work as per expectedHow to list all files in current directory whose second character is a digit?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

17

3

List all files/dirs in or below the current directory that match 'filename'.

ls

share|improve this question

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

add a comment | 

17

3

List all files/dirs in or below the current directory that match 'filename'.

ls

share|improve this question

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

add a comment | 

List all files/dirs in or below the current directory that match 'filename'.

ls

share|improve this question

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

share|improve this question

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

share|improve this question

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

asked Feb 9 '11 at 20:00

mackenirmackenir

18811 gold badge11 silver badge55 bronze badges

4 Answers
4

active

oldest

votes

28

The direct equivalent is

find . -iname <filename>

which will list all files and directories called <filename> in the current directory and any subdirectories, ignoring case.

If your version of find doesn't support -iname, you can use -name instead. Note that unlike -iname, -name is case sensitive.

If you only want to list files called <filename>, and not directories, add -type f

find . -iname <filename> -type f

If you want to use wildcards, you need to put quotes around it, e.g.

find . -iname "*.txt" -type f

otherwise the shell will expand it.

As others have pointed out, you can also do:

find . | grep ".txt$"

grep will print lines based on regular expressions, which are more powerful than wildcards, but have a different syntax.

See man find and man grep for more details.

share|improve this answer

edited Feb 16 '14 at 17:56

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  If <filename> contains wildcards, use quotes around it, e.g. find . -name '*.txt'.
  
  – Gilles
  Feb 9 '11 at 23:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles, updated my answer to say that, thanks.
  
  – Mikel
  Feb 10 '11 at 4:32
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Using <filename> as marker for userinput is a bad habit in command-line environment, where < and > most of the time have specific meaning. I suggest just using filename, maybe FILENAME to emphasize it. Most people will understand, and those, who won't, might cause harm when not understanding that they aren't supposed to hit less-than or greater-than sign.
  
  – user unknown
  Feb 10 '11 at 8:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  <filename> is a convention in a lot of UNIX documentation, so I think it's useful for people to be aware of it, but I agree FILENAME might be easier to understand.
  
  – Mikel
  Feb 10 '11 at 10:48
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  find -iname <filename> is better since it is case-insensitive like DOS
  
  – Agnel Kurian
  Feb 16 '14 at 17:18
  

  
  
  
  

 | 
show 1 more comment

8

Some shells allow ls **/filename, which is quite convenient.

share|improve this answer

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Good point. In recent versions of bash, running shopt -s globstar; echo **/filename is equivalent to find . -name "filename". It also works in zsh.
  
  – Mikel
  Feb 10 '11 at 4:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This 'ls **/filename` is fine, but seems not go more that one directory level deep.
  
  – Sopalajo de Arrierez
  Apr 12 '14 at 23:14
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @sopalajo-de-arrierez If you do shopt -s globstar, it will probably work for you. Recursive globbing is a feature that is available only in some shells, and sometimes, it is not on by default.
  
  – Shawn J. Goff
  Apr 13 '14 at 3:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ops... I understand now, @ShawnJ.Goff: the shopt command enables the option globstar on. Now it works like a charm. Thanks a lot.
  
  – Sopalajo de Arrierez
  Apr 13 '14 at 12:05
  
  
  

  
  
  
  

add a comment | 

4

You can do this with

find . | egrep filename

share|improve this answer

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You could also do it in one with find . -regextype posix-egrep -regex '.*filename.*' (I don't know if the egrep part is important, but you used egrep in your answer so I included it)
  
  – Michael Mrozek♦
  Feb 9 '11 at 20:29
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You can, but grep is different than the equivalent DOS command. grep uses regular expressions, while the DOS command uses shell wildcards.
  
  – Mikel
  Feb 9 '11 at 20:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Come to think of it, shell globs are also different than DOS wildcards. For instance, find . -name "*.*" won't do what you'd expect from a DOS background. Globs are close enough to be recognizable, though, while regexes are an entirely new beast.
  
  – Jander
  Feb 10 '11 at 8:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What does *.*.* do in a modern dos i.e. windows cmd? What about *.*.*.*?
  
  – ctrl-alt-delor
  Jun 30 '16 at 8:30
  

  
  
  
  

add a comment | 

0

It can be also: tree -if </your/path> or 'pwd' as a path

share|improve this answer

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f7169%2fwhat-is-the-linux-equivalent-of-dos-dir-s-b-filename%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

28

The direct equivalent is

find . -iname <filename>

which will list all files and directories called <filename> in the current directory and any subdirectories, ignoring case.

If your version of find doesn't support -iname, you can use -name instead. Note that unlike -iname, -name is case sensitive.

If you only want to list files called <filename>, and not directories, add -type f

find . -iname <filename> -type f

If you want to use wildcards, you need to put quotes around it, e.g.

find . -iname "*.txt" -type f

otherwise the shell will expand it.

As others have pointed out, you can also do:

find . | grep ".txt$"

grep will print lines based on regular expressions, which are more powerful than wildcards, but have a different syntax.

See man find and man grep for more details.

share|improve this answer

edited Feb 16 '14 at 17:56

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  If <filename> contains wildcards, use quotes around it, e.g. find . -name '*.txt'.
  
  – Gilles
  Feb 9 '11 at 23:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles, updated my answer to say that, thanks.
  
  – Mikel
  Feb 10 '11 at 4:32
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Using <filename> as marker for userinput is a bad habit in command-line environment, where < and > most of the time have specific meaning. I suggest just using filename, maybe FILENAME to emphasize it. Most people will understand, and those, who won't, might cause harm when not understanding that they aren't supposed to hit less-than or greater-than sign.
  
  – user unknown
  Feb 10 '11 at 8:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  <filename> is a convention in a lot of UNIX documentation, so I think it's useful for people to be aware of it, but I agree FILENAME might be easier to understand.
  
  – Mikel
  Feb 10 '11 at 10:48
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  find -iname <filename> is better since it is case-insensitive like DOS
  
  – Agnel Kurian
  Feb 16 '14 at 17:18
  

  
  
  
  

 | 
show 1 more comment

28

The direct equivalent is

find . -iname <filename>

which will list all files and directories called <filename> in the current directory and any subdirectories, ignoring case.

If your version of find doesn't support -iname, you can use -name instead. Note that unlike -iname, -name is case sensitive.

If you only want to list files called <filename>, and not directories, add -type f

find . -iname <filename> -type f

If you want to use wildcards, you need to put quotes around it, e.g.

find . -iname "*.txt" -type f

otherwise the shell will expand it.

As others have pointed out, you can also do:

find . | grep ".txt$"

grep will print lines based on regular expressions, which are more powerful than wildcards, but have a different syntax.

See man find and man grep for more details.

share|improve this answer

edited Feb 16 '14 at 17:56

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  If <filename> contains wildcards, use quotes around it, e.g. find . -name '*.txt'.
  
  – Gilles
  Feb 9 '11 at 23:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles, updated my answer to say that, thanks.
  
  – Mikel
  Feb 10 '11 at 4:32
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Using <filename> as marker for userinput is a bad habit in command-line environment, where < and > most of the time have specific meaning. I suggest just using filename, maybe FILENAME to emphasize it. Most people will understand, and those, who won't, might cause harm when not understanding that they aren't supposed to hit less-than or greater-than sign.
  
  – user unknown
  Feb 10 '11 at 8:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  <filename> is a convention in a lot of UNIX documentation, so I think it's useful for people to be aware of it, but I agree FILENAME might be easier to understand.
  
  – Mikel
  Feb 10 '11 at 10:48
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  find -iname <filename> is better since it is case-insensitive like DOS
  
  – Agnel Kurian
  Feb 16 '14 at 17:18
  

  
  
  
  

 | 
show 1 more comment

The direct equivalent is

find . -iname <filename>

which will list all files and directories called <filename> in the current directory and any subdirectories, ignoring case.

If your version of find doesn't support -iname, you can use -name instead. Note that unlike -iname, -name is case sensitive.

If you only want to list files called <filename>, and not directories, add -type f

find . -iname <filename> -type f

If you want to use wildcards, you need to put quotes around it, e.g.

find . -iname "*.txt" -type f

otherwise the shell will expand it.

As others have pointed out, you can also do:

find . | grep ".txt$"

grep will print lines based on regular expressions, which are more powerful than wildcards, but have a different syntax.

See man find and man grep for more details.

share|improve this answer

edited Feb 16 '14 at 17:56

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

find . -iname <filename>

find . -iname <filename> -type f

find . -iname "*.txt" -type f

find . | grep ".txt$"

share|improve this answer

edited Feb 16 '14 at 17:56

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

answered Feb 9 '11 at 20:33

MikelMikel

41.4k1010 gold badges104104 silver badges128128 bronze badges

8

Some shells allow ls **/filename, which is quite convenient.

share|improve this answer

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Good point. In recent versions of bash, running shopt -s globstar; echo **/filename is equivalent to find . -name "filename". It also works in zsh.
  
  – Mikel
  Feb 10 '11 at 4:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This 'ls **/filename` is fine, but seems not go more that one directory level deep.
  
  – Sopalajo de Arrierez
  Apr 12 '14 at 23:14
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @sopalajo-de-arrierez If you do shopt -s globstar, it will probably work for you. Recursive globbing is a feature that is available only in some shells, and sometimes, it is not on by default.
  
  – Shawn J. Goff
  Apr 13 '14 at 3:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ops... I understand now, @ShawnJ.Goff: the shopt command enables the option globstar on. Now it works like a charm. Thanks a lot.
  
  – Sopalajo de Arrierez
  Apr 13 '14 at 12:05
  
  
  

  
  
  
  

add a comment | 

8

Some shells allow ls **/filename, which is quite convenient.

share|improve this answer

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Good point. In recent versions of bash, running shopt -s globstar; echo **/filename is equivalent to find . -name "filename". It also works in zsh.
  
  – Mikel
  Feb 10 '11 at 4:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This 'ls **/filename` is fine, but seems not go more that one directory level deep.
  
  – Sopalajo de Arrierez
  Apr 12 '14 at 23:14
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @sopalajo-de-arrierez If you do shopt -s globstar, it will probably work for you. Recursive globbing is a feature that is available only in some shells, and sometimes, it is not on by default.
  
  – Shawn J. Goff
  Apr 13 '14 at 3:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ops... I understand now, @ShawnJ.Goff: the shopt command enables the option globstar on. Now it works like a charm. Thanks a lot.
  
  – Sopalajo de Arrierez
  Apr 13 '14 at 12:05
  
  
  

  
  
  
  

add a comment | 

Some shells allow ls **/filename, which is quite convenient.

share|improve this answer

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

share|improve this answer

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

answered Feb 10 '11 at 3:42

Shawn J. GoffShawn J. Goff

31k1919 gold badges114114 silver badges134134 bronze badges

4

You can do this with

find . | egrep filename

share|improve this answer

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You could also do it in one with find . -regextype posix-egrep -regex '.*filename.*' (I don't know if the egrep part is important, but you used egrep in your answer so I included it)
  
  – Michael Mrozek♦
  Feb 9 '11 at 20:29
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You can, but grep is different than the equivalent DOS command. grep uses regular expressions, while the DOS command uses shell wildcards.
  
  – Mikel
  Feb 9 '11 at 20:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Come to think of it, shell globs are also different than DOS wildcards. For instance, find . -name "*.*" won't do what you'd expect from a DOS background. Globs are close enough to be recognizable, though, while regexes are an entirely new beast.
  
  – Jander
  Feb 10 '11 at 8:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What does *.*.* do in a modern dos i.e. windows cmd? What about *.*.*.*?
  
  – ctrl-alt-delor
  Jun 30 '16 at 8:30
  

  
  
  
  

add a comment | 

4

You can do this with

find . | egrep filename

share|improve this answer

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You could also do it in one with find . -regextype posix-egrep -regex '.*filename.*' (I don't know if the egrep part is important, but you used egrep in your answer so I included it)
  
  – Michael Mrozek♦
  Feb 9 '11 at 20:29
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You can, but grep is different than the equivalent DOS command. grep uses regular expressions, while the DOS command uses shell wildcards.
  
  – Mikel
  Feb 9 '11 at 20:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Come to think of it, shell globs are also different than DOS wildcards. For instance, find . -name "*.*" won't do what you'd expect from a DOS background. Globs are close enough to be recognizable, though, while regexes are an entirely new beast.
  
  – Jander
  Feb 10 '11 at 8:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What does *.*.* do in a modern dos i.e. windows cmd? What about *.*.*.*?
  
  – ctrl-alt-delor
  Jun 30 '16 at 8:30
  

  
  
  
  

add a comment | 

You can do this with

find . | egrep filename

share|improve this answer

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

find . | egrep filename

share|improve this answer

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

answered Feb 9 '11 at 20:03

MattenMatten

14133 bronze badges

0

It can be also: tree -if </your/path> or 'pwd' as a path

share|improve this answer

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

add a comment | 

0

It can be also: tree -if </your/path> or 'pwd' as a path

share|improve this answer

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

add a comment | 

It can be also: tree -if </your/path> or 'pwd' as a path

share|improve this answer

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

share|improve this answer

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1

answered Jun 8 '16 at 14:47

Michael FatahovMichael Fatahov

1