The Linux File System Standard
There are, of course, still unresolved issues which the FSSTND group is still going to have to face. One of the upcoming ones is going the be the organization of architecture-independent scripts and data files (/usr/share). Up until now, Linux has only been widely available on i386 and compatible machines, so the need for standardization of such files was non-existent. The rapid progress being made by the ports to other architectures (MC680x0, Alpha, MIPS, PowerPC) suggests that this issue will soon need to be dealt with. Another issue that is under some discussion is the creation of an /opt directory as in SVR4. The goal for such a directory would be to provide a location for large commercial or third party packages to install themselves without worrying about the requirements made by FSSTND for the other directory hierarchies.
By now your appetite should be whetted and you may want to read the actual FSSTND document yourself. Information about how to participate in the continuing development of the FSSTND is contained in the FSSTND itself. The participants would appreciate it if you carefully read the complete document before you join in. That way you'll be better prepared to contribute in a valuable way to the development of the standard.
The FSSTND provides the Linux community with an excellent reference document and has proven to be an important factor in the maturation of Linux. As Linux continues to evolve, so will the FSSTND. We are grateful to Linus Torvalds, H. J. Lu, the Free Software Foundation, and many others who have helped make Linux available. The FSSTND team has helped to standardize Linux, making it useful to a wider audience.
I would like to thank Daniel Quinlan for his many valuable corrections and suggestions for improvement to this article.
You can obtain the FSSTD document via FTP from tsx-11.mit.edu in /pub/linux/docs/linux-standards/fsstnd/. There is also an excellent FAQ (answers to Frequently Asked Questions) about the FSSTND, which is maintained by Ian McCloghrie, in the same directory.
Garrett D'Amore is a senior in computer science at San Diego State University, where he works with Linux and SunOS in the development of TCP/IP-based client-server applications using C++. He will be graduating in December, so he invites inquiries from interested employers. You can find him via e-mail at email@example.com or via the WWW at http://www.sdsu.edu/~garrett/
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Server Hardening
- EnterpriseDB's EDB Postgres Advanced Server and EDB Postgres Enterprise Manager
- The Death of RoboVM
- BitTorrent Inc.'s Sync
- The Humble Hacker?
- The US Government and Open-Source Software
- Open-Source Project Secretly Funded by CIA
- ACI Worldwide's UP Retail Payments
- New Container Image Standard Promises More Portable Apps
- AdaCore's SPARK Pro
In modern computer systems, privacy and security are mandatory. However, connections from the outside over public networks automatically imply risks. One easily available solution to avoid eavesdroppers’ attempts is SSH. But, its wide adoption during the past 21 years has made it a target for attackers, so hardening your system properly is a must.
Additionally, in highly regulated markets, you must comply with specific operational requirements, proving that you conform to standards and even that you have included new mandatory authentication methods, such as two-factor authentication. In this ebook, I discuss SSH and how to configure and manage it to guarantee that your network is safe, your data is secure and that you comply with relevant regulations.Get the Guide