In: Root » Computers and technology » Linux Commands » Reviewing Linux File System Standards
Reviewing Linux File System StandardsOne argument you hear regularly against Linux is that there are too many different distributions, and that multiple distributions lead to fragmentation. This fragmentation will eventuate in different, incompatible Linux versions. This is, without a doubt, complete nonsense that plays on “FUD” (Fear, Uncertainty, and Doubt). These types of arguments usually stem from a misunderstanding of the kernel and distributions. However, the Linux community has realized that it has grown past the stage of informal understandings about how things should be done. As a result, two types of standards are actively being worked on. The first standard is the File Hierarchy Standard (FHS). This is an attempt by many of the Linux distributions to standardize on a directory layout so that developers have an easy time making sure their applications work across multiple distributions without difficulty. As of this writing, Red Hat is almost completely compliant, and it is likely that most other distributions are as well. The other standard is the Linux Standard Base Specification (LSB). Like the FHS, the LSB is a standards group that specifies what a Linux distribution should have in terms of libraries and tools. A developer who only assumes that a Linux machine complies with the LSB and FHS is guaranteed to have an application that will work with all Linux installations. All of the major distributors have joined these standards groups, including organizations like Red Hat, Caldera, SuSE, Debian, Mandrake, and Turbo Linux. This should ensure that all desktop distributions will have a certain amount of common ground that a developer can rely on. From a system administrator’s point of view, these standards are interesting but not crucial to administering a Linux network. However, it never hurts to learn more about both. For more information on the FHS, go to their web site at http://www.pathname.com/fhs. To find out more about the LSB, check out http://www.linuxbase.org. Linux tutorial SummaryIn this module, you learned about Linux’s command-line interface through BASH, many command-line tools, and a few editors. As you continue through this article, you’ll find many references to the information in this module, so be sure that you get comfortable with working at the command line. You may find it a bit annoying at first, especially if you are used to a GUI for performing many of the basic tasks mentioned here—but stick with it. You may even find yourself eventually working faster at the command line than with the GUI! Obviously, this module can’t cover all the command-line tools available to you as part of your default Linux installation. I highly recommend taking some time to look into some of the reference books available, which give complete documentation on this subject. Linux: The Complete Reference, Fourth Edition, by Richard Petersen (McGraw-Hill/Osborne, 2001) is an excellent choice for a solid, thorough guide that covers everything available on your Linux system. For a helpful but less comprehensive approach to the considerable detail of Linux systems, try Linux in a Nutshell, Third Edition, edited by Ellen Siever (O’Reilly & Associates, 2000). In addition, there are a wealth of texts on shell programming at various levels and from various points of view. Get whatever suits you; shell programming is a skill well worth learning even if you don’t do system administration. |
legal disclaimer
Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.
related articles
Learning Who Is Logged In: who On systems that allow users to log in to other users’ machines or special servers, you will want to know who is logged in. You can generate such a report by using the who command: [michael@workbox michael]$ who The who report looks like this: michael tty1 Jun 14 18:22 rwhite pts/9 Jun 14 18:29 (:0) root pts/11 Jun 14 21:12 (:0) root pts/12 Jun 14 23:38 (:0) A Variation on who: w The w command di...
Remote X Displays In Linux tutorial 1, I said that X offers the ability to display content on other hosts’ screens. This makes it possible to log in to a server that has a special program on it and have the display redirected to the screen in front of you. Allowing this to happen is a two-step process. The first step is telling your machine that it should allow connections from another host for X displays. This is done with the xhost command: [michael@workbox michael]$ xhost +ungerer...
3. Editing text filesin Linux Red Hat
Editing Text Files Editors are by the far the bulkiest of common tools, but they are also the most useful. Without them, making any kind of change to a text file would be a tremendous undertaking. Regardless of your Linux distribution, you will have gotten a few editors. You should take a few moments to get comfortable with them before you’re busy fighting another problem. NOTE Although all of the editors listed here come with Red Hat 8, not all of them are installed by default. ...
4. Linux is built upon the foundation of file systems
File Systems Linux is built upon the foundation of file systems. They are the mechanisms by which the disk gets organized, providing all of the abstraction layers above sectors and cylinders. In this module, you’ll learn about the composition and management of these abstraction layers supported by the default Linux file system, ext2, and its more robust counterpart, ext3. This module covers the many aspects of managing disks. This includes creating partitions, establishing file systems, automating the process ...
5. Mounting and Unmounting Local Disks
Linux’s strong points include its flexibility and the way it lends itself to seamless management of file locations. Partitions are mounted so that they appear as just another subdirectory. Even a substantial number of file systems look, to the user, like one large directory tree. This characteristic is especially helpful to the administrator, who can relocate partitions to various servers but can have the partitions still mounted to the same location in the directory tree; users of the file system need not know abou...
6. The fsck tool short for File System ChecK
Using fsck The fsck tool, short for File System ChecK, is used to diagnose and repair file systems that may have become damaged in the course of daily operations. Such repairs are usually necessary after a system crash in which the system did not get a chance to fully flush all of its internal buffers to disk. (Although this tool’s name bears a striking resemblance to one of the expressions often uttered after a system crash, that this tool is part of the recovery process is strictly coincidence.) Us...
7. The process of adding a disk under Linux on the Intel
Adding and Partitioning a Disk The process of adding a disk under Linux on the Intel (x86) platform is relatively easy. Assuming you are adding a disk that is of similar type to your existing disks (e.g., adding an IDE disk to a system that already has IDE drives or adding a SCSI disk to a system that already has SCSI drives), the system should automatically detect the new disk at boot time, and all that is left is partitioning it and creating a file system on it. If you are adding a new type of disk (...
8. With the partitions created you need to put file systems on them
Syncing disks. WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information. [root@tedford /root]# If you needed to write an /etc/fstab file yourself for this configuration, it would look something like this: /dev/hdb1 / ext3 defaults 1 1 /dev/hdb2 swap swap defaults 0 0 /dev/hdb3 /usr ext3 defaults 1 2 /dev/hdb5 /home ext3 defaults 1 2 /dev/hdb6 /var ext3 defaults 1 2 /dev/hdb...
9. Mounting NFS partitions works much the same way as mounting local partitions
Mounting NFS Partitions Mounting NFS partitions works much the same way as mounting local partitions. The only difference is in how the partition is addressed. On local disks, partitions are addressed by their device name, such as /dev/hda1. In NFS mounts, partitions are referenced by their hostnames and export directories. Thus, if the server named ungerer is allowing your host to mount the directory /export/SL1200/MK2 and you want to mount this to /projects/topsecret1, you would use this command:...