ls -lrt interpretation drwxrwx--- 3 600 was 16384 May 24
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
As druuna pointed, it's a numeric uid which is not associated with any user. However, you can check it in /etc/passwd file, if entry still exits:
~$ grep 600 /etc/passwd
There is a possibility that the user associated with this uid has removed and he was owner of the file "statements", so instead of showing the owner name in ls -lrt output, it's showing his numeric uid only.
For more details on file permissions, read file permissions tutorial.
what is the difference between user and uid of particular directory?
Whenever a user account is created, a numeric uid gets assigned to him by system itself. On the other hand, directory do not has any uid, but they have an owner (some user) and a main group assigned to them.
In your case, 600 is uid of the owner of the "statement" directory and "was" is its main group.
As said above, 600 is nothing but uid (user identification number) of the owner of the directory. And perhaps the user has been deleted, so command is showing you only numeric uid, not the username i.e. owner name.
It's uid of the owner of the file "movie" i.e. 1000 is druuna's uid, not for file itself.
Yes, for the file/directory itself!
Owner and group are represented by numbers and all files (dirs, special files etc) are associated with a uid/gid number and not a human readable name.
The uid/gid number is "fixed" and belongs to that file/directory. Only on my 3 boxes this uid translates to druuna, it will not on your box. If no match for this uid can be made, the number itself is shown (as is the case for the OP) and if a match is made some other user name will be shown.
A practical example would be tar. When tarring files/directories these are stored in the archive with the associated uid/gid (not the name), when you untar this file on a box that does not have an association with this uid/gid (in /etc/passwd and/or /etc/group) it will show the number.
So files and directories _do_ have uid's and gid's!