In a shell, examine your disk layout using fdisk. For example:
fdisk /dev/sdaCommand (m for help):
pDisk /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?
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?
Download a tarball (from http://sourceforge.net, for example), and install it on your system with the following steps:
Unpack it using tar -xzvf file (or tar –xjvf file if it is compressed with bzip2).
Configure it with ./configure.
Build the software using make as directed in the documentation.
Install the software using the instructions provided.
Were there any difficulties with this procedure?
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)
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 ...