From fedora-docs-commits at redhat.com Wed Jun 10 15:28:35 2015 Content-Type: multipart/mixed; boundary="===============2171679614066326041==" MIME-Version: 1.0 From: fedora-docs-commits at redhat.com To: docs-commits at lists.fedoraproject.org Subject: securing-filesystems sn-introduction.xml,NONE,1.1 Date: Fri, 29 Jul 2005 11:00:18 -0400 Message-ID: <200507291500.j6TF0IiY031243@cvs-int.fedora.redhat.com> --===============2171679614066326041== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31227/securing-filesyst= ems Added Files: sn-introduction.xml = Log Message: Initial commit to the Fedora Docs repository. --- NEW FILE sn-introduction.xml --- Introduction
Intended Audience This document is intended for all end-users of the fedora distr= ibution. However it is my intention to present, as effectively as possib= le, this topic so that the following experienced audience can readily ac= quire valuable relevant information from this document as well: System Administrators Security Practitioners Power Users
Current Version The most current version of this document can be accessed at the following location: http://www.domain.com/docs/current/something.html This document is built from the following sources: Remote Development Versioning &doccvs; Local Development Identification= &docsysid;
Revision History &REVID; 2005-07-18 TRJ Imported into fedora-docs CVS. Altered document out= line. Added the character device content. 0.2 2005-05-13 TRJ Bugzilla submission. Received bugid: &BUG-NUM;. Alt= ered inclusive nature of the document title. 0.1 2005-05-04 TRJ Initial draft for fedora-docs
Feedback Have you found some missing information, missing links, or miss= ing characters? Maybe you just have some comments and/or suggestio= ns about this document? Mail it to the author of this document at the following address: &author.mail; Whenever possible please utilize the authors GnuPG key for these communications: KeyID: 1024D/57BF9042 2004-12-26 Thomas R. Jone= s ( IEEE Computer Society Account) <thomasjones@computer.org> Fingerprint: 5264 BCA1 6059 57A8 58E5 7F04 A11= E 5C13 57BF 9042
Copyright Information Copyright 2005 Thomas R. Jones &author.mail;
Legal Information &LEGALNOTICE-CONTENT;
System Requirements List requirements: materials, knowledge.
Document Conventions The following typographic and usage conventions occur in this document: Typographic and usage conventions Text typeMeaning Quoted text Quotes from people, quoted computer output.<= /entry> terminal view Literal computer input and output captured from= the terminal, usually rendered with a light grey ba= ckground. command Name of a command that can be entered on the co= mmand line. VARIABLE Name of a variable or pointer to content of a v= ariable, as in $VARNAME. Option to a command, as in the option to the ls command. argument Argument to a command, as in read man ls. command arguments Command synopsis or general usage, on a separat= ed line. filename Name of a file or directory, for example Change to the /usr/bin directory.= Key Keys to hit on the keyboard, such as type Q to quit. Button Graphical button to click, like the = OK button. Menu Choice Choice to select from a graphical menu, for instance: Select Help About Mozilla in your browser. Terminology Important term or concept: The Linux kernel is the heart of the system. See ????? link to related subject within this guide. The a= uthors site Clickable link to an external web resource.<= /entry>
--===============2171679614066326041==--