The following sections give you
some pointers on where to look for these important elements.
If GUI administrative tools for Linux have become so good, why do you need to know
about administrative files? For one thing, while GUI tools differ among Linux versions,
many underlying configuration files are the same. So, if you learn to work with them, you can work
with almost any Linux system. Also, if a feature is broken or if you need to do something that??™s not
supported by the GUI, when you ask for help, Linux experts almost always tell you how to change
the configuration file directly.
Administrative Commands
Only the root user is intended to use many administrative commands. When you log in as root (or
use su - from the shell to become root), your $PATH variable is set to include some directories
that contain commands for the root user. These include the following:
/sbin??”Contains commands for modifying your disk partitions (such as fdisk),
checking file systems (fsck), and changing system states (init).
/usr/sbin??”Contains commands for managing user accounts (such as useradd) and
adding mount points for automounting file systems (automount). Commands that run
as daemon processes are also contained in this directory. (Look for commands that end in
d, such as sshd, pppd, and cupsd.
Pages:
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337