1. In a shell, examine your disk layout using fdisk. For example:

    # fdisk /dev/sda
    Command (m for help): p
    Disk /dev/sda: 200.0 GB, 200049647616 bytes
    255 heads, 63 sectors/track, 24321 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0003bf13
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1          25      200781   83  Linux
    /dev/sda2              26          89      514080   82  Linux swap / Solaris
    /dev/sda3              90       24321   194643540   83  Linux

    Is the entire disk consumed by the existing filesystems?

  2. Examine how system directories are mapped to disk partitions on your system. Are /var and /tmp in their own partitions? Is /boot in its own partition within cylinder 1024? Is the root filesystem relatively small?

  3. Download a tarball (from http://sourceforge.net, for example), and install it on your system with the following steps:

    1. Unpack it using tar -xzvf file (or tar –xjvf file if it is compressed with bzip2).

    2. Configure it with ./configure.

    3. Build the software using make as directed in the documentation.

    4. Install the software using the instructions provided.

    Were there any difficulties with this procedure?

  4. Use ldd to examine library dependencies of executable programs on your system. For example:

    # ldd `which gcc`
     linux-gate.so.1 => (0x00110000)
     libc.so.6 => /lib/libc.so.6 (0x00682000)
     /lib/ld-linux.so.2 (0x00663000)
  5. Using a system that utilizes dpkg, obtain a list of all packages installed under dpkg management with dpkg -l | less. Find a package in the list that looks unfamiliar, and query information about ...

Get LPI Linux Certification in a Nutshell, 3rd Edition now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.