Permalink
Browse files

Corrections for consistency

  • Loading branch information...
1 parent b19dd9a commit 87fb8384ffc5230d1602222ec72c03ba688d3ffc @zyv zyv committed Aug 17, 2012
Showing with 46 additions and 46 deletions.
  1. +2 −2 README.md
  2. +25 −25 faq/index.md
  3. +5 −5 index.md
  4. +6 −6 package/index.md
  5. +1 −1 package/quickstart.md
  6. +1 −1 package/rebuild.md
  7. +6 −6 use/index.md
View
@@ -10,7 +10,7 @@ This is the Jeykll website content for http://repoforge.org/
Goal of the website:
-* how to install repoforge
+* how to install RepoForge
* how to cooperate/contribute
* information for mirror users
* where to find information
@@ -39,6 +39,6 @@ How to get a copy of this website running on your local machine.
Random Notes
------------
-GitHub supports ASCIIdoc but getting that working on the localhost with jeykll has proven to be troublesome. Getting the ball rolling with markdown as default markup. Helpful hint for markdown: `gem install cheat` and then `cheat markdown`
+GitHub supports ASCIIdoc but getting that working on the localhost with jeykll has proven to be troublesome. Getting the ball rolling with markdown as default markup. Helpful hint for markdown: `gem install cheat` and then `cheat markdown`.
Web design: html5 + blueprint + ghetto css to start with.
View
@@ -15,51 +15,51 @@ See [Using RepoForge](/use "Using RepoForge")
### How can I contribute? ###
-There are numerous ways you can help. Feel free to do more than one!
-* promote RepoForge - let people know when it helped you solve a problem.
+There are numerous ways you can help. Feel free to do more than one!
+* Promote RepoForge - let people know when it helped you solve a problem
* Get active on [our mailinglists](http://lists.repoforge.org/mailman/listinfo)
* Test the various packages in the repos, and let the package maintainers know about any problems you find
-* Become a [packager](/package "RepoForge contributor") by fixing packages or adding new packages.
-* Get forking. Fork the repository you want to assist with, fix things, submit pull requests: _for example, for the package that is [this website](http://github.com/RepoForge/RepoForge.github.com/)_.
-* Become a Mirror! You can setup a mirror of RepoForge - more details on that below.
+* Become a [packager](/package "RepoForge contributor") by fixing packages or adding new packages
+* Get forking. Fork the repository you want to assist with, fix things, submit pull requests: _for example, for the package that is [this website](http://github.com/repoforge/repoforge.github.com/)_
+* Become a mirror! You can setup a mirror of RepoForge - more details on that below
### Why are there now several repositories? What is "rfx"? ###
Our goal is to move all packages that conflict with upstream packages into a separate "extras" repository; this way, users who want to be confident that our packages will not cause conflicts with upstream can enable the base repository, and users who want newer versions of packages (and are willing to tolerate some package conflicts) can enable the extras repository.
-More information is in [this post](http://lists.RepoForge.org/pipermail/users/2010-November/018282.html).
+More information is in [this post](http://lists.repoforge.org/pipermail/users/2010-November/018282.html).
### How to become a mirror for RepoForge? ###
#### Mirror Requirements ####
We have a few requirements for those wishing to run a mirror:
-1. You must subscribe to the mailing list for mirror maintainers.
-2. At least 140 GB of available disk space. The current distribution directory is around 90 GB, but we wish to leave room for considerable expansion.
-3. You must not trim or abridge the mirrored tree in any way.
-4. You must not modify the mirrored tree in any way. In particular, index.html, HEADER.html and README.html files must not be altered or removed.
-5. Your mirror must not be shown "inside" another site using, for instance, frames.
-6. You must do an update-check at least once a day, and preferably four times a day.
-7. Do not rsync more rapidly than every hour.
-8. Sync on a random minute so it is more likely the requests will be spaced out with other mirrors.
-9. You must use 'RepoForge' name for the mirror.
+1. You must subscribe to the mailing list for mirror maintainers
+2. At least 140 GB of available disk space. The current distribution directory is around 90 GB, but we wish to leave room for considerable expansion
+3. You must not trim or abridge the mirrored tree in any way
+4. You must not modify the mirrored tree in any way. In particular, index.html, HEADER.html and README.html files must not be altered or removed
+5. Your mirror must not be shown "inside" another site using, for instance, frames
+6. You must do an update-check at least once a day, and preferably four times a day
+7. Do not rsync more rapidly than every hour
+8. Sync on a random minute so it is more likely the requests will be spaced out with other mirrors
+9. You must use 'repoforge' name for the mirror
#### Mirroring techniques ####
We only support rsync for updating mirrors. You can find details on rsync at http://rsync.samba.org/. Update your mirror with:
- /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/RepoForge/ /path/to/local/mirror/RepoForge
+ /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_repoforge_mirror/repoforge/ /path/to/local/mirror/repoforge
We highly recommend the use of a lock file in your cron script, so that you do not spawn multiple connections, which is hard on our servers and on your mirror. Update your mirror with:
- /usr/bin/flock -w 60 /var/lock/EUAK1qEPB3SM /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/RepoForge/ /path/to/local/mirror/RepoForge
+ /usr/bin/flock -w 60 /var/lock/EUAK1qEPB3SM /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_repoforge_mirror/repoforge/ /path/to/local/mirror/repoforge
Create your unique lockfile with:
cat /dev/urandom | tr -dc [:alnum:] | head -c12; echo
#### After I setup a mirror, what next? ####
-You will need to INFORM us of your new mirror. Once the site is configured, tested, and updating consistently, you should subscribe to the mirror maintainers mailing list.
+You will need to *inform* us of your new mirror. Once the site is configured, tested, and updating consistently, you should subscribe to the mirror maintainers mailing list.
Provide us with details of your mirror:
* URL of mirror
@@ -72,24 +72,24 @@ Provide us with details of your mirror:
* Asia:
- **ftp.riken.jp** (Japan) - *rsync://ftp.riken.jp/RepoForge/*
+ **ftp.riken.jp** (Japan) - *rsync://ftp.riken.jp/repoforge/*
* Europe:
- **mirror1.hs-esslingen.de** (Germany) - *rsync://mirror1.hs-esslingen.de/RepoForge/*
+ **mirror1.hs-esslingen.de** (Germany) - *rsync://mirror1.hs-esslingen.de/repoforge/*
- **repository.vsb.cz** (Czech Republic) - *rsync://repository.vsb.cz/RepoForge/*
+ **repository.vsb.cz** (Czech Republic) - *rsync://repository.vsb.cz/repoforge/*
* North-America / South-America:
- **RepoForge.eecs.wsu.edu** (United States) - *rsync://RepoForge.eecs.wsu.edu/RepoForge/*
+ **repoforge.eecs.wsu.edu** (United States) - *rsync://repoforge.eecs.wsu.edu/repoforge/*
Notes:
-* If/when your mirror is on the list, you can change the IP of the mirror without notifying us.
-* If the best contact point for your mirror is not the address you are subscribed to the [mailing list](http://lists.RepoForge.org/mailman/listinfo/mirrors) with, please provide the email address of your preferred contact as well.
+* If/when your mirror is on the list, you can change the IP of the mirror without notifying us
+* If the best contact point for your mirror is not the address you are subscribed to the [mailing list](http://lists.repoforge.org/mailman/listinfo/mirrors) with, please provide the email address of your preferred contact as well
* Please alert the mailing list if anything about the server changes like location, available bandwidth, frequency of updates, etc.
### Why is this FAQ so short? ###
-Because you have yet to [fork it on GitHub](http://github.com/RepoForge/RepoForge.github.com/) to add other questions/answers.
+Because you have yet to [fork it on GitHub](http://github.com/repoforge/repoforge.github.com/) to add other questions/answers.
View
@@ -4,12 +4,12 @@ title: RepoForge Project
---
## Welcome to RepoForge! ##
-_RepoForge is the new RPMforge. Please excuse the dust as we move in and remodel._
+_RepoForge is the new RPMforge. Please excuse the dust as we move in and remodel._
The RepoForge project maintains RPM packages for:
* Red Hat Enterprise Linux (RHEL)
-* CentOS
-* Scientific Linux.
+* CentOS
+* Scientific Linux
We provide a set of repositories compatible with various RHEL versions, providing packages for:
- Servers _(eg. monitoring, troubleshooting, management)_
@@ -19,6 +19,6 @@ We provide a set of repositories compatible with various RHEL versions, providin
For more information please see:
* [faq](/faq "repoforge faq") - some questions, some answers
-* [using](/use "install repoforge") - Configure your system for RepoForge.
-* [packagers](/package "contribute packages to repoforge") - RepoForge welcome contributions.
+* [using](/use "install repoforge") - Configure your system for RepoForge
+* [packagers](/package "contribute packages to repoforge") - RepoForge welcome contributions
View
@@ -6,17 +6,17 @@ title: Building and Contributing Packages
[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
## Contributing New Packages ##
-RepoForge welcomes contributions!
+RepoForge welcomes contributions!
To contribute a new package, or a fix to an existing package, use the following procedure:
-1. Create an account on [GitHub](https://github.com/).
-2. [Fork](http://help.github.com/fork-a-repo/) our [git repository](https://github.com/repoforge/rpms).
-3. Make changes and commit them to your fork. See [BuildSystem](quickstart.html) for details on setting up a good build environment.
-4. Submit a [pull request](http://help.github.com/pull-requests/) when your contribution is ready.
+1. Create an account on [GitHub](https://github.com/)
+2. [Fork](http://help.github.com/fork-a-repo/) our [git repository](https://github.com/repoforge/rpms)
+3. Make changes and commit them to your fork. See [BuildSystem](quickstart.html) for details on setting up a good build environment
+4. Submit a [pull request](http://help.github.com/pull-requests/) when your contribution is ready
## Follow the community ##
-* [Subscribe to the mailing list(s)](http://lists.repoforge.org/mailman/listinfo) - and of course, review the archives
+* [Subscribe to the mailing list(s)](http://lists.repoforge.org/mailman/listinfo) - and, of course, review the archives
* Some of us hang out on #repoforge on irc.freenode.net
* Check out our [RepoForge bugtracker on github](https://github.com/repoforge/rpms/issues)
@@ -2,7 +2,7 @@
layout: default
title: quick start
---
-[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
+[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
## Quick Start build system ##
View
@@ -83,4 +83,4 @@ Finally, try to build the package from the specfile:
If rpm complains about unmet dependencies, use yum to install them; unfortunately, you cannot use yum-builddep to automate the process when building from a specfile.
-From here on, the process is the same as when rebuilding a SRPM.
+From here on, the process is the same as when rebuilding a SRPM.
View
@@ -3,7 +3,7 @@ title: Using RepoForge
layout: default
---
-## Using RepoForge ##
+## Using RepoForge ##
First download the appropriate `rpmforge-release` package for your distribution:
@@ -18,9 +18,9 @@ More detailed instructions and recommendations are available on the [CentOS wiki
Hints:
-* Use `cat /etc/redhat-release` to find which release of EL you are using.
-* Use `uname -a` to find your processor architecture.
-* Use `rpm -ivh package-filename` to install the rpmforge-release package (also works with URLs).
+* Use `cat /etc/redhat-release` to find which release of EL you are using
+* Use `uname -a` to find your processor architecture
+* Use `rpm -ivh package-filename` to install the rpmforge-release package (also works with URLs)
* You can use `wget` or `curl` to download the package using one of the above links if needed (for example on a server with no X Window)
-* Then you can use `yum` to install the available packages from the RepoForge repo.
-* Afterward, you can disable accidental updates from the repo by setting `enabled = 0` in the repo definition file in `/etc/yum.repos.d/`.
+* Then you can use `yum` to install the available packages from the RepoForge repo
+* Afterward, you can disable accidental updates from the repo by setting `enabled = 0` in the repo definition file in `/etc/yum.repos.d/`

0 comments on commit 87fb838

Please sign in to comment.