I was trying to learn more about Linux and came across the command ls ????? and it displayed a few files in the directory but I am not really sure what it is specifically displaying. I tried to use the man to explain it further but I couldn't find anything. Could someone please explain?
123475
If I have a number of directories, named, for example 10001 through 10025 is there any reason to use ls 1*/foo vs. ls 100??/foo?  I have a lot more than 25 of them, so I mostly curious if there's any differences in speed.  I know the difference in use between the two, that the asterisk will match longer file names, like 10001.backup. But let's say I don't have any files that don't follow my conventions. Is there any behind-the-scenes differences?
99279
I'd like to find where a file (with a partially-known filename) is in the file system.  I'd like to know how to do this from the command line, rather than using a GUI utility.  In Windows, I'd run the following:  cd /d C:\ dir *filename* /s   What's the Linux equivalent?
119826
On several Unix servers, I have seen below behavior:   I list all the files using ls -lrt: 3 files are being shown up  I open one of the files using vi editor  I close the open file   Now in some Unix system, I can still see the earlier screen as it is as in point 2 (listing those 3 files, ls -lrt output as it is) whereas on some systems, the text of recently opened file is printed.   I want to know which setting in profile or some *rc file this behavior depends.
72084
I'm learning Ubuntu and experimenting with things.  I noticed I couldnt create a directory within /sys  Is this a special directory or something? Are there other types of directories?  (I did a sudo -i and a chmod a+w /sys)
21956
I am trying to understand named pipes in the context of this particular example.  I type &lt;(ls -l) in my terminal and get the output as, bash: /dev/fd/63: Permission denied.  If I type cat &lt;(ls -l), I could see the directory contents. If I replace the cat with echo, I think I get the terminal name (or is it?).  echo &lt;(ls -l) gives the output as /dev/fd/63.  Also, this example output is unclear to me.  ls -l &lt;(echo "Whatever") lr-x------ 1 root root 64 Sep 17 13:18 /dev/fd/63 -&gt; pipe:[48078752]   However, if I give,ls -l &lt;() it lists me the directory contents.   What is happening in case of the named pipe?
104832
Why does ls .* print out the contents of the hidden directories? I want to print just the hidden files, and now see that   is a solution to this, yet I sill want to understand why the contents of the directories are shown. The contents of further nested directories are not shown.  Below is a partial output of ls .* in my home directory.  .bash_history .bash_profile .bashrc .coin_history .emacs .gitconfig .gitignore_global .grasp_jss  .ssh: config          github_rsa.pub  id_rsa.pub      known_hosts.old github_rsa      id_rsa          known_hosts     lambda.pem  .vim: colors   ftdetect syntax   This machine is running RHEL. Similar behavior observed on Mac OSX.
63794
Possible Duplicate:          Is there a command in Linux which displays when the file was created ? I see that ls -l gives the last modified time, but can I get the created time/date?
22670
What does size of a directory mean in output of ls -l command?
81833
Just started reading a bit about the linux file system. In several places I found quotes like this one:      Unix directories are lists of association structures, each of which contains one filename and one inode number.   So I expected to find out that each directory would contain the names of the files under it, with each file mapped to an inode. But when I do vim directory_name in ubuntu, I get something like this:  " ============================================================================ " Netrw Directory Listing                                        (netrw v156) "   /Users/user/workspace/folder "   Sorted by      name "   Sort sequence: [\/]$,\&lt;core\%(\.\d\+\)\=\&gt;,\.h$,\.c$,\.cpp$,\~\=\*$,*,\.o$,\.obj$,\.info$,\.swp$,\.bak$,\~$ "   Quick Help: &lt;F1&gt;:help  -:go up dir  D:delete  R:rename  s:sort-by  x:special " ============================================================================== ../ ./ folder1/ folder2/ file1 file2   I expected to see an inode number next to each file name, why isn't this the case?
66518
For command ls     -F, --classify           append indicator (one of */=&gt;@|) to entries   Wikipedia says * represents executable and / dir.  Regular files are not followed by any of the above symbols.  But * follows text file and pdf file too. Are they executables?  Do the -F indicators always mean same as the first field in -rwxrwx---?  It seems like there is no difference between hardlinks and the files  in either the -F indicators or the first field in -rwxrwx---. How do you distinguish them?  Thanks.
86602
Sometimes I see the following command:   find . -name  * -exec ls -a {} \;   I was asked to execute this.  What does {} \; mean here?
112061
I was making some changes to /etc/fstab, when this chicken and egg question occurred to me - if /etc/fstab contains the instructions for mounting the file systems, including the root partition, then how does the OS read that file in the first place?
77398
I just mistyped ls as la. Without noticing, I ran it:  tim@Hairy:~$ la detection.sh   output-2.jpg  output-4.jpg  output-6.jpg  output-8.jpg Test1.pdf output-1.jpg   output-3.jpg  output-5.jpg  output-7.jpg  output-9.jpg          tim@Hairy:~$ ls detection.sh   output-2.jpg  output-4.jpg  output-6.jpg  output-8.jpg Test1.pdf output-1.jpg   output-3.jpg  output-5.jpg  output-7.jpg  output-9.jpg    What's the difference between ls and la?
21636
There are two directories shown by 'ls'.  Normally directories anywhere are blue on black background.  But the first one is blue on green and impossible to read.  Why is this?  How to make it blue on black, or at least something light on something dark?  This is on Ubuntu 12.04, using bash in Gnome Terminal.  In Konsole, the blue is slightly darker, and possible to read, though could be way better.
16118
list=`ls -a R*` echo $list   Inside a shell script, this echo command will list all the files from current directory starting with R, but in one line. How can I print each item on one line?  I need a generic command for all the scenarios happening with ls, du, find -type -d, etc.
116924
I'd like to only the directory  $ ls -d  . #get . on macos   and the same on centos  [root@iz2ze9wve43n2nyuvmsfx5z ~]# ls -d . .   I find the solution:  [root@iz2ze9wve43n2nyuvmsfx5z /]# ls -d */ bin/   dev/  home/  lib64/       media/  opt/   root/  sbin/  sys/  usr/ boot/  etc/  lib/   lost+found/  mnt/    proc/  run/   srv/   tmp/  var/   but the manual specify     -d, --directory           list directories themselves, not their contents   What's the reason -d perform this way?
82167
There is a thread that talks about ls "*" not showing any files, but I actually wonder why the simple  ls *   command doesn't output anything in my terminal other than  ls: invalid option -- '|' Try 'ls --help' for more information.   while   ls   will list all the files in the current directories as    1                  ferol                      readme.txt  2                  fichier                    sarku  2018               GameShell                  Templates  22223333          '-|h4k3r|-'                 test  3                  hs_err_pid2301.log         test2  CA.txt             important.top.secret.txt   toto.text  CA.zip             JavaBlueJProject           tp1_inf1070  countryInfo.txt    liendur                   'tp1_inf1070_A19(2) (1)'  currency           liensymbolique             tp1_inf1070_A19.tar  curreny            LOL                        Videos  Desktop            Longueuil                 'VirtualBox VMs'  Documents          Music                      words  douffos            numbers                    Zip.zip  Downloads          Pictures  examples.desktop   Public   Any ideas as to why the globbing doesn't take effect here? I'm on Ubuntu, working in the terminal, I don't know if it makes a difference.  Thanks.