Birmingham mumbai

[
 49 
]
This is what you're actually seeing here—the UID for the user, as well as the GID for 
the user's primary group. Again, we'll get to groups in more detail later.
You probably also noticed
 that the 
/etc/passwd
 file on your system contains entries 
for many more users than the ones we've created ourselves. This is perfectly normal, 
as Linux uses user accounts for various processes and services that run in the 
background. You'll likely never interact with the default accounts at all, though you 
may someday create your own system user for a process to run as. For example, 
perhaps you'll create a data processor account for an automated data-processing 
script to run under.
Anyway, back to our 
/etc/passwd
 file. The fifth column is designated for user info, 
most commonly the user's first and last names. In my example, the fifth field is blank 
for 
jdoe
, as I created 
jdoe
 with the 
useradd
 command, which didn't prompt me for 
the first and last names. This field is also nicknamed the 
GECOS
 field, and you may see 
it referred to as such when you read the documentation.
In the sixth column, the home directory for each user is shown. In the case of 
jdoe
, 
it's set as 
/home/jdoe
. Finally, we designate the user's shell as 
/bin/bash
. This field 
refers to the default shell the user will use, which defaults to 
/bin/bash
 when an 
account is created with the 
adduser
 command, and 
/bin/sh
 when created with the 
useradd
 command. (If you have no preference, 
/bin/bash
 is the best choice for most.) 
If we want the user to use a different shell, we can clarify that here (though shells 
other than 
/bin/bash
 are beyond the scope of this book). If we wanted, we could 
change the user's shell to something invalid to prevent them from logging in at all. 
This is useful for when a security issue requires us to disable an account quickly.