In this video, I go over how to find files in Linux terminal. In this Linux Tutorial you will learn everything you ever wanted to know about the find commend and even some stuff you didn’t know you wanted to know.. Basic syntax. -find options starting/path expression. $ find -name media*. Note: -name is CASE SENSITIVE for results. $ find /var/html -name *.html. $ find -type d -iname Downloads. Note: -iname makes it so results are not matched based on CASE.. Advanced syntax. Find Files based on modified in the past 1 day. $ find -mtime -1. Note: cull this down by using | grep partial file name. Or Find Files based on modified in the past 10 minutes. $ find -mmin -10. OR find Files based on modified in the past 10 minutes and greater than 10 megs. $ find -mmin -10 -size +10M. You can also add the -delete command at the end to delete ALL FILES FOUND!!! Use with extreme caution! Bonus easily find where a program is located with «whereis». $ whereis gimp. ┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅. Titus Tech Talk ➜ https://www.youtube.com/c/ChrisTitusTechStreams. Recommended Windows Anti-Virus ➜ https://links.christitus.com/antivirus. Recommended VPN Service ➜ https://links.christitus.com/expressvpn. Recommended Web Browser ➜ https://links.christitus.com/brave. Website Recommendations ➜ https://www.christitus.com/recommendations. My Gear ➜ https://www.amazon.com/shop/christitustech. ���� Contact Me ����. YouTube Membership ➜ https://www.youtube.com/channel/UCg6gPGh8HU2U01vaFCAsvmQ/join. ChrisTitus.com Members (Patreon Alternative) ➜ https://christitus.com/members/. Twitter ➜ https://twitter.com/christitustech. ┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅┅. DISCLAIMER: This video and description contain affiliate links, which means that if you click on one of the product links, I’ll receive a small commission. This helps supports the channel and allows us to continue to make videos like this. Thank you for your support! Please note: by clicking any of the above links you are NOT charged extra and in some instances will pay a discounted rate.
В данном видео мы рассмотрим команду find с опцией -name linux. Установка и настройка linux в Бердянске. Обслуживание организаций под ОС linux., ремонт ноутбуков, компьютеров, мониторов, ТВ, телевизоров, планшетов, сборка и настройка. Профи сервис г.Бердянск ул. Смоленская 3
Все дистрибутивы Linux имеют сходное дерево папок и файлов, которое определяется стандартом FHS. Разбираемся со стандартом, а так же учимся искать файлы, команды и информацию о них.
В данном видео мы рассмотрим команду find с опцией -name linux. Установка и настройка linux в Бердянске. Обслуживание организаций под ОС linux., ремонт ноутбуков, компьютеров, мониторов, ТВ, телевизоров, планшетов, сборка и настройка. Профи сервис г.Бердянск ул. Смоленская 3
Linux команда find команда поиска файлов.. Ссылка на видео «Linux/Ubuntu шаблоны подстановки (wildcards).». https://www.youtube.com/watch?v=BxEIYeNRCGE. Ссылка на видео «Linux навигация относительные и абсолютные пути (ссылки).». https://www.youtube.com/watch?v=ShBhgZJ2ADs. #!/bin/bash. # find поиска файла по параметрам. # 0:18 поиск файла по имени в текущей директории. find -name file_name. # 1:05 поиск файла по имени в текущей директории без учёта регистра. find -iname file_name. # 2:06 поиск файла по имени в домашней директории без учёта регистр. find -iname file_name. # 2:21 поиск файла по имени по всей файловой системе без учёта регистра. find / -iname file_name. # 2:51 поиск по имени с помощью шаблонов подстановки. find -iname fi?e_nam? find -iname f*. # 4:20 поиск по размеру (все, что больше). find -size +1000k. # 4:51 поиск по размеру (все, что меньше). find -size -1k. # 5:07 найти пустой файл. find -empty. # 5:44 справка. find -help
For people who think the least amount of characters typed in terminal is best, enable globbing and use «ls **» with grep. Less optimized than find (probably, idk), but quick and useful if you’re already somewhere deep in your filesystem (don’t use it in root dir; it grabs every file from every subdirectory and will take hours to finish, or give up after 5 minutes).
I’ve always preferred to enable globbing and use «ls ** | grep -i [stuff]» to find things, just cause I never got used to find. However, filtering by time and size does sound pretty powerful, but I’m not sure that I have a use for that. Reassuring to know that this video exists if I ever find myself needing this command! Great vid!
Edit: I realize that my preferred method probably isn’t as efficient as whatever algorithms/methods the find command uses, and can probably do a full search without me having to think too hard about narrowing my search. Methods like using information directly from the system, rather than expanding my grep query into a massively clustered regex command…. I’ll come back to this video the next time I lose something in my system!
Thank you, even after using Linux for 10 years and trying to puzzle out man pages (which are complete, detailed, factual, and often utterly useless), I’d given up on finding via terminal (except for executables when I can use whereis ) because I never got the command parameters right I’d either get no result, or the entire disk volume listed!
Привет Кирилл, как ты? Могу ли я быть наглым и попросить тебя, если у тебя есть на это время, создать ролик по теме 110.3 Securing data with encryption? Я собираюсь в понедельник сдавать экзамен 102 и как на зло ничего из этой темы не могу понять. В любом случае спасибо заранее и хорошего дня )))
From a Terminal beginners perspective i feel like you went really really fast in this video, id like to know what every bit of the command does and have time to comprehend that personally, like really overexplaining things would be helpful for it to stick in. Overall though its a wellmade video with great info, thanks:)
May I ask what distro you are using for these examples? It has always been my experience that you must quote wildcarded file names to prevent the shell from expanding the wildcard (which produces unexpected results and/or errors) and allows find itself to operate on the wildcards. Are you using as the starting directory because you are limiting the search to your home directory? Starting with returns absolute path names relative to your home directory, starting the path name with / returns absolute path names relative to /, starting with dot (.) returns relative path names relative to current directory. This is how I learned to use find (-print is technically correct but redundant in later versions of find.) find all files in my home directory that start with the string ‘media’: cd; find. -name ‘media*’ -print find /home/user -name ‘media*’ -print find -name ‘media*’ -print find all files in my home directory that contain the string ‘media’ (use of grep is not necessary and also forks additional processes): cd; find. -name ‘*media*’ -print find all files in the file system that contain the string ‘media’ (you will be restricted from certain directories as an ordinary user): cd /; find. -name ‘*media*’ -print find / -name ‘*media*’ -print
If any part of my comment is incorrect or inappropriate, I apologize in advance.
Oops, to be clear… the strings apply only to the actual file name and not to the content of the file.
Скажите пожалуйста, как просто найти нужный файл без всей этой мороки, как скажем в Ворд, просто пишешь нужное слово и запускаешь поисковик, а через несколько секунд, появляются все документы, содержащие искомое слвово? Спасибо.
Not relative to this video but have a couple of Linux questions.
I am planning on rooting my Samsung Galaxy Tab E tablet and was wondering what Linux should I put on it (or should I keep the default and just get rid of the bloatwear)?
Also, when my daughter buys her aunt’s laptop, I shall be having fun with her Chromebook and putting Linux on it. I was raised on computers and know basic programming (the logic behind programming but not the languages per say), which Linux should I install (realize it is a Chromebook so no heavy gaming on it)?
Chris, you should have used ‘media*’ between quotes. If you had a file in your current directory named fi. ‘media.jpg’ then bash would have replaced your medi* with media.jpg and you would be looking only for that filename. If you had two filenames starting with media, bash would have replaced media* with those 2 names and the find command would have thrown an error.
So I guess it is time for you to make a video talking about wildcards and globbing 😉
Linux команда find команда поиска файлов.
Ссылка на видео «Linux/Ubuntu шаблоны подстановки (wildcards).»
https://www.youtube.com/watch?v=BxEIYeNRCGE
Ссылка на видео «Linux навигация относительные и абсолютные пути (ссылки).»
https://www.youtube.com/watch?v=ShBhgZJ2ADs
#!/bin/bash
# find поиска файла по параметрам
# 0:18 поиск файла по имени в текущей директории
find -name file_name
# 1:05 поиск файла по имени в текущей директории без учёта регистра
find -iname file_name
# 2:06 поиск файла по имени в домашней директории без учёта регистр
find -iname file_name
# 2:21 поиск файла по имени по всей файловой системе без учёта регистра
find / -iname file_name
# 2:51 поиск по имени с помощью шаблонов подстановки
find -iname fi?e_nam?
find -iname f*
# 4:20 поиск по размеру (все, что больше)
find -size +1000k
# 4:51 поиск по размеру (все, что меньше)
find -size -1k
# 5:07 найти пустой файл
find -empty
# 5:44 справка
find -help
For people who think the least amount of characters typed in terminal is best, enable globbing and use «ls **» with grep. Less optimized than find (probably, idk), but quick and useful if you’re already somewhere deep in your filesystem (don’t use it in root dir; it grabs every file from every subdirectory and will take hours to finish, or give up after 5 minutes).
I’ve always preferred to enable globbing and use «ls ** | grep -i [stuff]» to find things, just cause I never got used to find. However, filtering by time and size does sound pretty powerful, but I’m not sure that I have a use for that. Reassuring to know that this video exists if I ever find myself needing this command! Great vid!
Edit: I realize that my preferred method probably isn’t as efficient as whatever algorithms/methods the find command uses, and can probably do a full search without me having to think too hard about narrowing my search. Methods like using information directly from the system, rather than expanding my grep query into a massively clustered regex command…. I’ll come back to this video the next time I lose something in my system!
Thank you, even after using Linux for 10 years and trying to puzzle out man pages (which are complete, detailed, factual, and often utterly useless), I’d given up on finding via terminal (except for executables when I can use whereis ) because I never got the command parameters right I’d either get no result, or the entire disk volume listed!
Linus команда grep поиск фрагмента текста в файле (файлах).
#!/bin/bash
# grep поиск фрагмента в файле (файлах)
# 1:12 поиск фрагмента в файле
grep ‘MyVideos’ text_file
# 1:38 поиск фрагмента во всех файлах текущей директории
grep ‘MyVideos’./*
# 2:21 проверка числа вхождений в файлы текущей директории
grep -с ‘MyVideos’./*
# 3:06 поиск фрагмента без учёта регистра
grep -i ‘myvideos’./*
# 4:28 поиск по содержимому файла
grep -f ttt./*
# перенаправление потока
ls -l../ | grep -f ttt
Привет Кирилл, как ты?
Могу ли я быть наглым и попросить тебя, если у тебя есть на это время, создать ролик по теме 110.3 Securing data with encryption?
Я собираюсь в понедельник сдавать экзамен 102 и как на зло ничего из этой темы не могу понять.
В любом случае спасибо заранее и хорошего дня )))
Hey Chris,
From a Terminal beginners perspective i feel like you went really really fast in this video, id like to know what every bit of the command does and have time to comprehend that personally, like really overexplaining things would be helpful for it to stick in. Overall though its a wellmade video with great info, thanks:)
May I ask what distro you are using for these examples? It has always been my experience that you must quote wildcarded file names to prevent the shell from expanding the wildcard (which produces unexpected results and/or errors) and allows find itself to operate on the wildcards. Are you using as the starting directory because you are limiting the search to your home directory? Starting with returns absolute path names relative to your home directory, starting the path name with / returns absolute path names relative to /, starting with dot (.) returns relative path names relative to current directory. This is how I learned to use find (-print is technically correct but redundant in later versions of find.)
find all files in my home directory that start with the string ‘media’:
cd; find. -name ‘media*’ -print
find /home/user -name ‘media*’ -print
find -name ‘media*’ -print
find all files in my home directory that contain the string ‘media’ (use of grep is not necessary and also forks additional processes):
cd; find. -name ‘*media*’ -print
find all files in the file system that contain the string ‘media’ (you will be restricted from certain directories as an ordinary user):
cd /; find. -name ‘*media*’ -print
find / -name ‘*media*’ -print
If any part of my comment is incorrect or inappropriate, I apologize in advance.
Oops, to be clear… the strings apply only to the actual file name and not to the content of the file.
Скажите пожалуйста, как просто найти нужный файл без всей этой мороки, как скажем в Ворд, просто пишешь нужное слово и запускаешь поисковик, а через несколько секунд, появляются все документы, содержащие искомое слвово? Спасибо.
Not relative to this video but have a couple of Linux questions.
I am planning on rooting my Samsung Galaxy Tab E tablet and was wondering what Linux should I put on it (or should I keep the default and just get rid of the bloatwear)?
Also, when my daughter buys her aunt’s laptop, I shall be having fun with her Chromebook and putting Linux on it. I was raised on computers and know basic programming (the logic behind programming but not the languages per say), which Linux should I install (realize it is a Chromebook so no heavy gaming on it)?
Chris, you should have used ‘media*’ between quotes.
If you had a file in your current directory named fi. ‘media.jpg’ then bash would have replaced your medi* with media.jpg and you would be looking only for that filename.
If you had two filenames starting with media, bash would have replaced media* with those 2 names and the find command would have thrown an error.
So I guess it is time for you to make a video talking about wildcards and globbing 😉