Loading modules You can (Remote web server) load any module that
Loading modules You can load any module that has been compiled and installed (to the /lib/modules directory) into your running kernel using the insmod command. The most common reasons for loading a module are that you want to use a feature temporarily (such as loading a module to support a special file system on a floppy you want to access) or to identify module that will be used by a particular piece of hardware that could not be autodetected. Here is an example of the insmod command being used to load the parport module. The parport module is used to provide the core functions for sharing a parallel port with multiple devices. # insmod parport Using /lib/modules/2.4.6-3.1/kernel/drivers/parport/parport.o After parport is loaded you could load the parport_pc module to define the PC-style ports that are available through the interface. The parport_pc module lets you optionally define the addresses and IRQ numbers associated with each device sharing the parallel port. Here is an example: # insmod parport_pc io=0×3bc irq=auto In the previous example, a device is identified as having an address of 0×3bc. The IRQ for the device is auto-detected. The insmod command loads modules temporarily. At the next system reboot, the modules you enter disappear. To permanently add the module to your system, add the insmod command line to one of the start-up scripts that are run a boot time. Removing modules You can remove a module from a running kernel using the rmmod command. For example, to remove the module parport_pc from the current kernel, type the following: # rmmod parport_pc If the module is not currently busy, the parport_pc module is removed from the running kernel. Working with File Systems File systems in Red Hat Linux are organized in a hierarchy, beginning from root (/) and continuing downward in a structure of directories and subdirectories. As an administrator of a Red Hat Linux system, it is your duty to make sure that all the disk drives that represent your file system are available to the users of the computer. It is also your job to make sure that there is enough disk space in the right places in the file system for users to store the information they need. File systems are organized differently in Linux than they are in MS Windows operating systems. Instead of drive letters (e.g., A:, B:, C:) for each local disk, network file system, CD-ROM, or other type of storage medium, everything fits neatly into the directory structure. It is up to an administrator to create a mount point in the file system and then connect the disk to that point in the file system. Cross Reference Information on how the Linux file system is organized is provided in Chapter 3. The organization of your file system begins when you install Linux. Part of the installation process is to divide your hard disk (or disks) into partitions. Those partitions can then be assigned to:
You want to have a cheap webhost for your apache application, then check apache web hosting services.