From 32e1656ffdc1d2a5023849275e41303739f7cd17 Mon Sep 17 00:00:00 2001 From: Tommy Reynolds Date: Thu, 2 Mar 2006 23:06:38 +0000 Subject: Replaced references to "-en.xml" to "-en_US.xml", including in the areas. --- common/bugreporting-en_US.xml | 17 + common/cvs-en_US.xml | 1014 +++++++++++++++++++++++++++++++ common/deprecatednotice-en_US.xml | 29 + common/draftnotice-en_US.xml | 8 + common/fedora-entities-en_US.ent | 76 +++ common/legacynotice-en_US.xml | 17 + common/legalnotice-content-en_US.xml | 71 +++ common/legalnotice-content-p1-en_US.xml | 16 + common/legalnotice-content-p2-en_US.xml | 16 + common/legalnotice-content-p3-en_US.xml | 15 + common/legalnotice-content-p4-en_US.xml | 14 + common/legalnotice-content-p5-en_US.xml | 14 + common/legalnotice-content-p6-en_US.xml | 15 + common/legalnotice-en_US.xml | 22 + common/legalnotice-opl-en_US.xml | 240 ++++++++ common/legalnotice-relnotes-en_US.xml | 37 ++ common/legalnotice-section-en_US.xml | 40 ++ common/obsoletenotice-en_US.xml | 14 + 18 files changed, 1675 insertions(+) create mode 100644 common/bugreporting-en_US.xml create mode 100644 common/cvs-en_US.xml create mode 100644 common/deprecatednotice-en_US.xml create mode 100644 common/draftnotice-en_US.xml create mode 100644 common/fedora-entities-en_US.ent create mode 100644 common/legacynotice-en_US.xml create mode 100644 common/legalnotice-content-en_US.xml create mode 100644 common/legalnotice-content-p1-en_US.xml create mode 100644 common/legalnotice-content-p2-en_US.xml create mode 100644 common/legalnotice-content-p3-en_US.xml create mode 100644 common/legalnotice-content-p4-en_US.xml create mode 100644 common/legalnotice-content-p5-en_US.xml create mode 100644 common/legalnotice-content-p6-en_US.xml create mode 100644 common/legalnotice-en_US.xml create mode 100644 common/legalnotice-opl-en_US.xml create mode 100644 common/legalnotice-relnotes-en_US.xml create mode 100644 common/legalnotice-section-en_US.xml create mode 100644 common/obsoletenotice-en_US.xml (limited to 'common') diff --git a/common/bugreporting-en_US.xml b/common/bugreporting-en_US.xml new file mode 100644 index 0000000..470f6b7 --- /dev/null +++ b/common/bugreporting-en_US.xml @@ -0,0 +1,17 @@ + + Reporting Document Errors + + + To report an error or omission in this document, file a bug report in &BZ; + at &BZ-URL;. When you file your bug, select "&BZ-PROD;" as the + Product, and select the title of this document as + the Component. The version of this document is + &DOCID;. + + + + The maintainers of this document will automatically receive your bug report. + On behalf of the entire &FED; community, thank you for helping us make + improvements. + + diff --git a/common/cvs-en_US.xml b/common/cvs-en_US.xml new file mode 100644 index 0000000..4bf39a5 --- /dev/null +++ b/common/cvs-en_US.xml @@ -0,0 +1,1014 @@ + + + + + + CVS + + The Concurrent Versions System (CVS) + provides a framework where multiple users can edit the same files. + As you can imagine, if a group of users edits the files in a single + directory, chaos would reign. Using CVS, + however, a group of people can safely work on the same set of files. + CVS keeps the master copy of the files, + and it records who changed what and when in a central repository. If + conflicts arise, CVS lets you know. + CVS is often used so that programmers can + share code, but it also works well for documentation. + + + cvs + +
+ How CVS Works + + cvs + how it works + + + cvs + overview + + + In most cases, each set of files that make up a package or project + is stored as a module on the CVS server. + + + + When working with files from CVS, you + checkout a copy of the module on your local + file system. After modifying one or more files, you + commit them back to the central + CVS repository server. + + + + With CVS you may edit a file without + first getting permission or locking the file. The + concurrent part of the + CVS name comes from its ability to + allow several different people to edit different parts of the same + file. As long as none of the changes overlap, + CVS can correctly record their changes. + In case of duplicate changes, they are clearly marked in the files + and the authors must resolve the issue among themselves. + + + + When you commit changes, only changes to files the server knows + about are committed. In other words, if you created a file in your + local checkout of a module, the new file is not automatically + uploaded to the server. You must add the + file to the repository and then commit it. If you remove a file + from your local checkout of a module, you must specify that you + want to remove it from the repository on the CVS server and then + commit the removal of the file. + + + + The specific commands to perform these actions are discussed in + . + + + + If someone has modified the file between the last time you grabbed + the file from CVS and when you try to commit a change, + CVS will try to merge the changes into + the master copy of the CVS server. If + the content you changed is in a different location in the file + than the content changed by someone else, chances are, the commit + action will go through without a conflict. + If someone modified the same content as the content you just + changed and tried to commit, you will see a message that a file + conflict has occurred. Thus, you need to + update your files frequently. It is a good + practice to update them right before you start modifying a file. + Refer to for + instructions on resolving conflicts. + +
+
+ Preparing For CVS Use + + cvs + preparing for use + + + Before using CVS, you need to establish + an account with the CVS server. After + getting an account, you do not need to perform these actions + again. + + +
+ Is CVS Installed On Your System + + cvs + RPM installation + + + You must have the CVS + RPM package installed. Verify its presence by + typing the command: + +$ rpm -q cvs + + If you see output similar to + cvs-1.11.19-1, then the package + is installed. A message similar to package cvs + is not installed means you must install the + cvs package before continuing. If you + do not know how to do this, consult your system administrator + who can install it for you. + +
+ +
+ Generating SSH Keys + + OpenSSH + authorization keys + + + The CVS server uses + SSH Protocol 2 keys to authenticate + users. Thus, you need to generate a pair of keys before applying + for a CVS account. If you already + have an SSH DSA key, + you may skip this step. + + + Tip + + You already have a DSA key if you have the + file ~/.ssh/id_dsa.pub on the system. + + + If your existing DSA key does not require a + passphrase, you are strongly urged to + generate one that does require a passphrase. + + + + Use the following steps to generate a DSA key + used by SSH Protocol 2. It is + required for an + cvs.fedora.redhat.com + CVS account. + + + + OpenSSH + ssh-keygen + + + + ssh-keygen + + + + + To generate a + DSA + key to work with version 2.0 protocol, at a shell prompt, + type the command: + +$ ssh-keygen -t dsa + + Accept the default file location of + ~/.ssh/id_dsa. You are strongly urged + to define and use a passphrase to + enhance the security of your key. Enter a passphrase + different than your account password and confirm it by + entering it again. + + + + + Copy your new key to the correct file by typing the + following at a shell prompt. + +$ cat ~/.ssh/id_dsa.pub>>~/.ssh/authorized_keys + + + Check this command carefully before you press the + ENTER + key. If ~/.ssh/authorized_keys + already exists, the contents of + ~/.ssh/id_dsa.pub will be appended to + the end of the ~/.ssh/authorized_keys + file. + + + + + + Change the permissions of your ~/.ssh + directory and your keys with the commands: + +$ chmod 755 ~/.ssh +$ chmod 644 ~/.ssh/authorized_keys + + + + Tip + + You can have your system remember your passphrase so that you + do not have to type it every time you access the + CVS server. Refer to the + documentation of the ssh-add + program. + + +
+
+
+ Configuring For CVS Access + + cvs + configuring for access + + + cvs + CVSROOT + + + cvs + CVS_RSH + + + CVSROOT + + + CVS_RSH + + + cvs + .cvsrc + + + + .cvsrc + + +
+ Avoiding Repetitive Typing + + cvs + avoiding repetitive typing + + + Many CVS commands need certain + command line switches to operate consistently. Rather than + typing them every time that command is used, you can save the + switches in a file that CVS will read + before executing your command line. + + + + Create a file named ~/.cvsrc in your home + directory. It should contain the following commands, one per + line: +cvs -z3 +diff -uNp +rdiff -uNp +update -dP + +
+ +
+ Configuring for Read-Only CVS Access + + cvs + configuring read-only access + + + cvs + anonymous access + + + If your goal is to download the various &FC; documents and to + render them on your system, you only need read-only access to + the CVS repository. Follow the + instructions in this section and then skip directly to + . + + + + Change directories to where you want your files from + CVS to be located, and execute the + following commands: + +$ export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs +$ cvs login +$ cvs checkout docs-common module-name +$ cvs checkout module-name +$ cd module-name + + Once you have checked the module out, it doesn't matter what + your + CVSROOT + is set to because it is stored in the file + CVS/Root for each directory in your local + repository. As long as your current working directory has a + CVS/ directory, the + CVS program will automatically locate + the &FC; repository. + +
+ +
+ Configuring Read/Write CVS Access + + cvs + configuring read/write access + + + cvs + configuring access for authors + + + To author a new document or to change an existing one, you must + obtain full read/write access to the &FC; Docs + CVS repository. For the full details + on this process, refer to the + http://fedoraproject.org/wiki/DocsProject/NewWriters + web site. Below is a summary: + + + + + + Subscribe to the + fedora-docs-list + , which is the main forum for the project. + + + + + Generate a GNU Privacy Guard (GPG) key to + identify yourself to the project. + + + + + Register for a + Bugzilla + account, if you do not have one already. + Bugzilla is how we keep track of bugs, + changes and projects. + + + + + Post a + self + introduction to the list. + + + + + + After your + self + introduction has been approved your + CVS access will be granted. + + + + Every author, and that includes you once your self introduction + has been received, has a unique + $CVSROOT + to access the CVS repository: + +$ export CVSROOT=:ext:yourname@cvs.fedora.redhat.com:/cvs/docs +$ export CVS_RSH=/usr/bin/ssh + + With the + $CVSROOT + and + $CVS_RSH + environment variables in place, you can access the repository: + +$ cvs co -c + + You will be asked for the passphrase for your + SSH key. Press + ENTER + and you should receive a list of modules already in the + repository. + +
+
+
+ Basic CVS Commands + + cvs + commands + + + After configuring your system to work with CVS, checkout the + modules you will be working on. + + + Tip + + To see if you need a correctly-set + $CVSROOT + variable, or the + repository command line switch, see + if you have a CVS/ subdirectory in your + working directory. + + + If you have a CVS/ directory, + CVS ignores any + $CVSROOT + or command line switch. + + +
+ Checking Out Modules + + cvs + checking out modules + + + You only need to checkout a module once. After a local copy of + the module is on your system, it is on your system. + + + + To checkout a module, use the following command: + +$ cvs co <module-name> + + For example, to checkout the + example-tutorial module, change + to your work directory, and execute the following command: + +$ cvs co example-tutorial + + A directory called example-tutorial/ is + created in the current directory. + + + + If a branch name is not specified when checking out a module, it + is referred to as the HEAD of the + CVS module. + + +
+ Checking Out Branches of Modules + + cvs + check out modules + checking out branches + + + Think of a CVS branch as a version + of the files for a particular version of a manual or package. + + + + To checkout a branch of a module, use the following command: + +$ cvs co <directory> <branchname> <module-name> + + A directory named <directory> + is created, and the files for the + <branchname> branch of the + <module-name> module are + copied in the directory. + + + + For example, to checkout a branch named BRANCH-VERSION-1.2 + from the mymodule module, use + the command: + +$ cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule + + The BRANCH-VERSION-1.2 branch of the module is checked out in + the mymodule-1.2 directory on your + system. + + + + To determine which branches and tags exist for a file, use the + command: + +$ cvs status <filename> + + For example, the status of the file + foo.sgml is as follows: + + + +=================================================================== +File: foo.sgml Status: Up-to-date + + Working revision: 1.47 + Repository revision: 1.47 /cvs/docs/custom-guide/rhl-cg-en_US.sgml,v + Sticky Tag: (none) + Sticky Date: (none) + Sticky Options: (none) + + Existing Tags: + BRANCH-VERSION-1.2 (branch: 1.25.2) + + + + Only tags marked as branches in the second column under the + Existing Tags section can be + checked out as a branch. + +
+
+ +
+ Updating Files + + cvs + updating files + + + To retrieve the latest versions of the files in a module, change + to the directory that contains the files for the module and + execute the command: + +cvs update + + The latest versions of all the files in the module are + downloaded into your local copy. If you notice a file conflict, + refer to . + +
+ +
+ Committing Files + + cvs + committing files + + + After modifying files in your local version of a module, commit + them to save the changes on the CVS + server: + +$ cvs commit "some log message" filename + + + If you would prefer to write your log message with your + favorite text editor, as defined by the $VISUAL or the $EDITOR + environment variable, just omit the -m "some + log message". The buffer will already contain + comments describing the change; you do not need to delete them + as you enter your own text. + + + + + The log message should be as descriptive as possible so that you + and anyone else working on the module understands what changed. + Using a log message such as updated some + files does not accurately describe what has changed + and will not help you in the future. If you are correcting a + bug, use the Bugzilla reference. + + + + The <filename> can be one + filename, a series of filenames separated by spaces, or a group + of filenames specified using wildcards such as + *.png or foo-*.sgml. + + + + If no filename or group of filenames is specified in the + commit command, all outstanding changes of + any kind are committed to the server. The command is recursive + and will include changes in any subdirectories of the module. + Use caution when issuing the commit command + without any filenames because you might not remember exactly + what files changed. + + + + If you notice a file conflict, refer to + . + +
+ +
+ Adding Files + + cvs + adding files + + + To add a file to a module, create the file in your local copy + then execute the following command: + +$ cvs add file-to-add + + After adding the file, you must commit the + add to copy it to the server: + +$ cvs commit "some log message" file-to-add +
+ +
+ Managing Binary Files + + cvs + binary files + + + The most commonly-archived files are simple text files but + sometimes binary files are also archived. The + cvs program recognizes most common + filename extentions such as .png or + .jpg, so cvs + usually "does the right thing". + + + + When a copy of a file is checked out of the repository, + cvs scans it for special keywords, + such as "$id:$" and + replaces the string with a generated value, such as the file + version number. + + + + This keyword substitution usually corrupts binary files, so it + must be turned off if cvs does not + recognize your file as binary. To mark your file as being + binary, and thus needing the keyword expansion turned off, use + the command: + +$ cvs filename + + Note that the file must already be checked in to the + CVS repository before the + command can be used. This is OK, since + the keyword expansion is done as the file is checked out and + copied to the local directory, not when the file is committed to + the repository. + + + Recovering a binary file + + If you check a binary file into the repository and then find + it corrupted when it is checked out, do not panic. Simply use + the command as described above, delete + your local file copy, and check it out again. + + +
+ +
+ Removing Files + + cvs + removing files + + + If a file is no longer needed in the module, use the + remove command to remove it from your local + copy and then commit the removal to the + server. Even though the file is removed from current version of + the module, an archived copy is still kept on the server and can + be retrieved at any time with the add + command. + +$ cvs rm -f file-to-remove + + After removing the file, you must commit the + removal: + +$ cvs commit "some log message" file-to-remove + + You can not use wildcards in the commit + command to identify removed files. They must be specified with a + exact filename. + + + + If you need to rename a file, it is best to rename the file on + the CVS server so that the history of + the file is preserved. If you need to rename a file, send an + email to + cvsdocs-administrator@fedora.redhat.com + asking to have the file renamed. + +
+ +
+ Status of Files + + cvs + status of files + + + Sometimes it is necessary to view the + status of a file in a + CVS module. To view the status of a + file, use the command: + +$ cvs status filename + + The status report of a repository file is as follows: + + + + + Up-to-date + + + Your revision of the file is identical to the latest + revision on the CVS server. + + + + + + Locally Modified + + + You have updated to the latest revision from the server, + but then you modified the file on your system. + + + + + + Locally Added + + + You added the file with the cvs add + command but have not yet committed the addition of the + file. + + + + + + Locally Removed + + + You removed the file with the cvs + remove command but have not yet committed the + removal. + + + + + + Needs Checkout + + + A newer version of the file is on the server and needs to + be retrieved. Even though the status includes the word + checkout, it really means that you need to update your + files with the cvs update command. + + + + + + Needs Patch + + + The revision in your local checkout needs a patch to be + the latest revision from the server. Issue the + cvs update command to resolve. + + + + + + Needs Merge + + + A newer revision exists on the server and your local + version contains modification not yet committed. This + status usually occurs if you don't have the latest + revision of the file and edit it anyway. + + + + + + File had conflicts on merge + + + Similar to Needs Merge, + except when you tried to issue the cvs + update command, the differences could not be + resolved automatically. Refer to + for + more information on resolving conflicts. + + + + + + Unknown + + + The CVS server does not know + anything about this file. It has neither been added nor + removed locally and has never been committed to the + server. This status usually occurs for files you should + not commit to CVS such as + generated-index.sgml or for files + that you want to add to the repository but have not yet + issued the cvs add command. + + + + +
+ +
+ Resolving Conflicts + + cvs + resolving conflicts + + + If you modify a file and the same region is modified by someone + else and committed first, you will probably see a message + similar to the following when committing the file or updating + your local copy of the module: + + + +RCS file: /cvs/docs/module-name/filename.sgml,v +retrieving revision 1.12 +retrieving revision 1.13 +Merging differences between 1.12 and 1.13 into filename.sgml +rcsmerge: warning: conflicts during merge +cvs server: conflicts found in filename.sgml +C filename.sgml + + + + To resolve the conflict, open the file, search for + <<<<<<< + and determine which version of the content is correct. For + example: + + + +<para> +Some sentence. +<<<<<<< filename.sgml +A sentence that was changed in the working copy. +======= +A same sentence that was changed differently and committed. +>>>>>>> 1.13 +</para> + + + + The content between the + <<<<<<<, + and the ======= is the content + from your working copy. The content between the + ======= and the + >>>>>>> is + the content from the server. + + + + Resolve the conflict by editing your copy, and commit the file. + +
+ +
+ Summary + + cvs + commands + summary of + + + All commands assume you are in the proper directory for the + CVS module. + + + Basic CVS Commands + + + + + + Command + Description + + + + + cvs checkout + <module-name> + or cvs co <module-name> + + Creates a directory called + <module-name> with the contents of the + module in the directory + + + cvs co -d <directory> -r <branchname><module-name> + + Creates the <directory> directory + with the contents of the <branchname> + branch of the <module-name> module + + + cvs update or cvs up + + Update your files with the latest files from the CVS server + + + cvs add <filename> + + Add a new file "filename" to the CVS server + + + cvs commit -m "My message" + <filename> + + Update file <filename> with the + latest copy from your computer + + + cvs log <filename> + + View the commit messages for the file <filename> + + + + cvs status <filename> + + View status of the file, such as Locally + Modified + + + + cvs status -v <filename> + + View existing tags and branches for file + + + cvs diff <filename> + + Show diff of the working copy of the file and the latest + version of the file for the branch + + + cvs diff -r1.1 -r1.2 <filename> + + Show diff of version 1.1 and 1.2 for file + + + +
+ + For more information, read the CVS manual available on your + system at + /usr/share/doc/cvs-<version-number>/cvs.ps + (the CVS version might vary) and visit the CVS webpage available + at + http://www.cvshome.org/. + + + Tip + + Since CVS is using + ssh to connect to the + CVS server, you will be prompted + your password before performing your + CVS request. If you want to + configure your machine so that you do not have to enter a + password, refer to the + &RH; + Linux 9 Customization Guide for details + about using ssh-agent. + + +
+
+ diff --git a/common/deprecatednotice-en_US.xml b/common/deprecatednotice-en_US.xml new file mode 100644 index 0000000..0eeca61 --- /dev/null +++ b/common/deprecatednotice-en_US.xml @@ -0,0 +1,29 @@ + + DEPRECATED DOCUMENT + + This document is no longer supported by the &FDP;. One or more of the + following situations may have occurred: + + + + + + Changes in Fedora may have made this document inaccurate. + + + + + A more relevant document may be available. + + + + + This document may have been subsumed in a different document. + + + + + + Refer to the revision history for more information. + + diff --git a/common/draftnotice-en_US.xml b/common/draftnotice-en_US.xml new file mode 100644 index 0000000..30a39a8 --- /dev/null +++ b/common/draftnotice-en_US.xml @@ -0,0 +1,8 @@ + + DRAFT + + This is a draft version of the document. It is subject to change at any time + and may not have been tested for technical accuracy yet. If you find any + errors, please report them via Bugzilla in bug &BUG-NUM;. + + diff --git a/common/fedora-entities-en_US.ent b/common/fedora-entities-en_US.ent new file mode 100644 index 0000000..662f98f --- /dev/null +++ b/common/fedora-entities-en_US.ent @@ -0,0 +1,76 @@ + + + + + + + + + + + + + + + + +http://fedora.redhat.com/"> +http://fedora.redhat.com/projects/docs/"> +http://fedora.redhat.com/docs/"> + + +http://bugzilla.redhat.com/"> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +"> +"> + + + + + + diff --git a/common/legacynotice-en_US.xml b/common/legacynotice-en_US.xml new file mode 100644 index 0000000..e7e140c --- /dev/null +++ b/common/legacynotice-en_US.xml @@ -0,0 +1,17 @@ + + LEGACY DOCUMENT + + This document relates to a version of &FC; that is no longer + supported by the &FP;. Changes in later versions of &FC; may have + made this document inaccurate. Please check the &FDP; website at + &FDPDOCS-URL; for a current version before you continue reading this + document. + + + + This version of the document will not be changed or amended, except + to correct errors that may result in data loss or a system security + weakness. If you believe that you have found such an error, please + report it via &BZ; in bug &BUG-NUM;. + + diff --git a/common/legalnotice-content-en_US.xml b/common/legalnotice-content-en_US.xml new file mode 100644 index 0000000..c6cba56 --- /dev/null +++ b/common/legalnotice-content-en_US.xml @@ -0,0 +1,71 @@ + + + + + + Copyright (c) 2006 by Fedora Foundation and others. This material may be + distributed only subject to the terms and conditions set forth in the Open + Publication License, v1.0, available at . + + + + Garrett LeSage created the admonition graphics (note, tip, important, + caution, and warning). + Tommy Reynolds Tommy.Reynolds@MegaCoder.com created the callout graphics. + They all may be freely redistributed with documentation + produced for the Fedora Project. + + + + + FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc., + are registered or pending registration in the U.S. and other countries, and + are used here under license to the Fedora Foundation. + + + + Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of + Red Hat, Inc. in the United States and other countries. + + + + All other trademarks and copyrights referred to are the property of their + respective owners. + + + + Documentation, as with software itself, may be subject to export control. + Read about Fedora Project export controls at . + + + diff --git a/common/legalnotice-content-p1-en_US.xml b/common/legalnotice-content-p1-en_US.xml new file mode 100644 index 0000000..92e546f --- /dev/null +++ b/common/legalnotice-content-p1-en_US.xml @@ -0,0 +1,16 @@ + + + +%FEDORA-ENTITIES; + +]> + + + Copyright (c) 2006 by Fedora Foundation and others. This material may be + distributed only subject to the terms and conditions set forth in the Open + Publication License, v1.0, available at . + diff --git a/common/legalnotice-content-p2-en_US.xml b/common/legalnotice-content-p2-en_US.xml new file mode 100644 index 0000000..67d7789 --- /dev/null +++ b/common/legalnotice-content-p2-en_US.xml @@ -0,0 +1,16 @@ + + + +%FEDORA-ENTITIES; + +]> + + + Garrett LeSage created the admonition graphics (note, tip, important, caution, + and warning). Tommy Reynolds Tommy.Reynolds@MegaCoder.com + created the callout graphics. They all may be freely redistributed with + documentation produced for the Fedora Project. + diff --git a/common/legalnotice-content-p3-en_US.xml b/common/legalnotice-content-p3-en_US.xml new file mode 100644 index 0000000..300797a --- /dev/null +++ b/common/legalnotice-content-p3-en_US.xml @@ -0,0 +1,15 @@ + + + +%FEDORA-ENTITIES; + +]> + + + FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc., + are registered or pending registration in the U.S. and other countries, and + are used here under license to the Fedora Foundation. + diff --git a/common/legalnotice-content-p4-en_US.xml b/common/legalnotice-content-p4-en_US.xml new file mode 100644 index 0000000..22d17c1 --- /dev/null +++ b/common/legalnotice-content-p4-en_US.xml @@ -0,0 +1,14 @@ + + + +%FEDORA-ENTITIES; + +]> + + + &RH; and the &RH; "Shadow Man" logo are registered trademarks of &FORMAL-RHI; + in the United States and other countries. + diff --git a/common/legalnotice-content-p5-en_US.xml b/common/legalnotice-content-p5-en_US.xml new file mode 100644 index 0000000..5b07163 --- /dev/null +++ b/common/legalnotice-content-p5-en_US.xml @@ -0,0 +1,14 @@ + + + +%FEDORA-ENTITIES; + +]> + + + All other trademarks and copyrights referred to are the property of their + respective owners. + diff --git a/common/legalnotice-content-p6-en_US.xml b/common/legalnotice-content-p6-en_US.xml new file mode 100644 index 0000000..bc31a09 --- /dev/null +++ b/common/legalnotice-content-p6-en_US.xml @@ -0,0 +1,15 @@ + + + +%FEDORA-ENTITIES; + +]> + + + Documentation, as with software itself, may be subject to export control. + Read about Fedora Project export controls at http://fedoraproject.org/wiki/Legal/Export. + diff --git a/common/legalnotice-en_US.xml b/common/legalnotice-en_US.xml new file mode 100644 index 0000000..d549c65 --- /dev/null +++ b/common/legalnotice-en_US.xml @@ -0,0 +1,22 @@ + + + +%FEDORA-ENTITIES; + +]> + + + + + + + + diff --git a/common/legalnotice-opl-en_US.xml b/common/legalnotice-opl-en_US.xml new file mode 100644 index 0000000..605c0be --- /dev/null +++ b/common/legalnotice-opl-en_US.xml @@ -0,0 +1,240 @@ + + + +%FEDORA-ENTITIES; + +]> + + + + + + + Permission is granted to copy, distribute, and/or modify this + document under the terms of the Open Publication Licence, Version + 1.0, or any later version. The terms of the OPL are set out below. + + + + REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED + VERSIONS + + Open Publication works may be reproduced and distributed in + whole or in part, in any medium physical or electronic, provided + that the terms of this license are adhered to, and that this + license or an incorporation of it by reference (with any options + elected by the author(s) and/or publisher) is displayed in the + reproduction. + + + + Proper form for an incorporation by reference is as follows: + + + + Copyright (c) <year> by <author's name or designee>. + This material may be distributed only subject to the terms and + conditions set forth in the Open Publication License, vX.Y or + later (the latest version is presently available at ). + + + + The reference must be immediately followed with any options + elected by the author(s) and/or publisher of the document (see + section VI). Commercial redistribution of Open + Publication-licensed material is permitted. Any publication in + standard (paper) book form shall require the citation of the + original publisher and author. The publisher and author's names + shall appear on all outer surfaces of the book. On all outer + surfaces of the book the original publisher's name shall be as + large as the title of the work and cited as possessive with + respect to the title. + + + + COPYRIGHT + + The copyright to each Open Publication is owned by its author(s) + or designee. + + + + SCOPE OF LICENSE + + + The following license terms apply to all Open Publication works, + unless otherwise explicitly stated in the document. + + + + Mere aggregation of Open Publication works or a portion of an + Open Publication work with other works or programs on the same + media shall not cause this license to apply to those other + works. The aggregate work shall contain a notice specifying the + inclusion of the Open Publication material and appropriate + copyright notice. + + + + SEVERABILITY. If any part of this license is found to be + unenforceable in any jurisdiction, the remaining portions of the + license remain in force. + + + + NO WARRANTY. Open Publication works are licensed and provided + "as is" without warranty of any kind, express or implied, + including, but not limited to, the implied warranties of + merchantability and fitness for a particular purpose or a + warranty of non-infringement. + + + + REQUIREMENTS ON MODIFIED WORKS + + + All modified versions of documents covered by this license, + including translations, anthologies, compilations and partial + documents, must meet the following requirements: + + + + + + The modified version must be labeled as such. + + + + + The person making the modifications must be identified and + the modifications dated. + + + + + Acknowledgement of the original author and publisher if + applicable must be retained according to normal academic + citation practices. + + + + + The location of the original unmodified document must be + identified. + + + + + The original author's (or authors') name(s) may not be used + to assert or imply endorsement of the resulting document + without the original author's (or authors') permission. + + + + + + GOOD-PRACTICE RECOMMENDATIONS + + + In addition to the requirements of this license, it is requested + from and strongly recommended of redistributors that: + + + + + + If you are distributing Open Publication works on hardcopy + or CD-ROM, you provide email notification to the authors of + your intent to redistribute at least thirty days before your + manuscript or media freeze, to give the authors time to + provide updated documents. This notification should describe + modifications, if any, made to the document. + + + + + All substantive modifications (including deletions) be + either clearly marked up in the document or else described + in an attachment to the document. + + + + + Finally, while it is not mandatory under this license, it is + considered good form to offer a free copy of any hardcopy + and CD-ROM expression of an Open Publication-licensed work + to its author(s). + + + + + + + LICENSE OPTIONS + + + The author(s) and/or publisher of an Open Publication-licensed + document may elect certain options by appending language to the + reference to or copy of the license. These options are + considered part of the license instance and must be included + with the license (or its incorporation by reference) in derived + works. + + + + A. To prohibit distribution of substantively modified versions + without the explicit permission of the author(s). "Substantive + modification" is defined as a change to the semantic content of + the document, and excludes mere changes in format or + typographical corrections. + + + + To accomplish this, add the phrase 'Distribution of + substantively modified versions of this document is prohibited + without the explicit permission of the copyright holder.' to the + license reference or copy. + + + + B. To prohibit any publication of this work or derivative works + in whole or in part in standard (paper) book form for commercial + purposes is prohibited unless prior permission is obtained from + the copyright holder. + + + + To accomplish this, add the phrase 'Distribution of the work or + derivative of the work in any standard (paper) book form is + prohibited unless prior permission is obtained from the + copyright holder.' to the license reference or copy. + + + + + + diff --git a/common/legalnotice-relnotes-en_US.xml b/common/legalnotice-relnotes-en_US.xml new file mode 100644 index 0000000..73545f8 --- /dev/null +++ b/common/legalnotice-relnotes-en_US.xml @@ -0,0 +1,37 @@ + + + +%FEDORA-ENTITIES; + +]> + + + + + + This document is released under the terms of the Open Publication License. + For more details, read the full legalnotice in . + + + Latest Release Notes on the Web + + These release notes may be updated. Visit to view the latest + release notes for Fedora Core 5. + + + diff --git a/common/legalnotice-section-en_US.xml b/common/legalnotice-section-en_US.xml new file mode 100644 index 0000000..190fe63 --- /dev/null +++ b/common/legalnotice-section-en_US.xml @@ -0,0 +1,40 @@ + + + + + %FEDORA-ENTITIES; + +]> + + +
+ Legal Notice + + + + + + +
+ diff --git a/common/obsoletenotice-en_US.xml b/common/obsoletenotice-en_US.xml new file mode 100644 index 0000000..b00c915 --- /dev/null +++ b/common/obsoletenotice-en_US.xml @@ -0,0 +1,14 @@ + + OBSOLETE DOCUMENT + + This document relates to a version of &FC; that is no longer + supported. Changes in later versions of &FC; may have made this + document inaccurate. Please check the &FDP; website at + &FDPDOCS-URL; for a current version before you continue reading this + document. + + + + This version of the document will not be changed or amended. + + -- cgit