OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 07-Aug-2003 16:17:18
Branch: HEAD Handle: 2003080715171800
Modified files:
openpkg-web facts.wml
Log:
update, correct and spell check facts
Summary:
Revision Changes Path
1.9 +24 -22 openpkg-web/facts.wml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/facts.wml
============================================================================
$ cvs diff -u -r1.8 -r1.9 facts.wml
--- openpkg-web/facts.wml 2 Apr 2003 10:04:35 -0000 1.8
+++ openpkg-web/facts.wml 7 Aug 2003 14:17:18 -0000 1.9
@@ -41,9 +41,9 @@
<p>
<li><b>Cross platform</b>
<br>
- OpenPKG supports FreeBSD, Linux and Solaris, it runs on Intel and Sparc
- CPUs. On any system the behaviour of OpenPKG is the same so engineers
- using it will see a unified environment accross these platforms. This
+ OpenPKG supports FreeBSD, Linux and Solaris, it runs on Intel, Sparc and Alpha
+ CPUs. On any system the behavior of OpenPKG is the same so engineers
+ using it will see a unified environment across these platforms. This
significantly reduces the complexities normally resulting from dissimilar
systems. Have your engineers do application configuration rather than
wasting time finding the differences between systems.
@@ -67,13 +67,13 @@
Officially released OpenPKG packages are digitally signed. Verification of
that sign makes any tampering on packages evident. Successful verification
assures that any package you grabbed came from a trusted source and
- includes the content you expect without any damage or suprises inside.
+ includes the content you expect without any damage or surprises inside.
<p>
<li><b>Package integrity verification</b>
<br>
Files from already installed packages can be compared against the original
package's content. Check system integrity any time you like. Ensure your
- last filesystem check did not damage your executeables.
+ last filesystem check did not damage any executable.
<p>
<li><b>Self contained Packages</b>
<br>
@@ -95,33 +95,35 @@
prefix this was our internal design decision. OpenPKG does not enforce
this prefix. It can be configured when bootstrapping. If you choose a
different path you must build your binaries yourself which is just a
- matter of CPU horsepower provided you have the source RPMs.
+ matter of CPU horsepower and source RPM download speed.
<p>
<li><b>Multiple instances</b>
<br>
Isolating multiple installations and creating virtual servers is a snap.
Just bootstrap OpenPKG to more than one location. We already got all the
- tweaks and quirks out of many packages. Assume network daemons will
+ tweaks and quirks out of the packages. Assume network daemons will
properly listen to configured not wildcard addresses and applications log
to their own not to the common system <i>var</i> area.
<p>
<li><b>Minimal OS intrusion</b>
<br>
- OpenPKG tries to not touch the operating system at all. Only very few
- adjustments are being done related to system startup and shutdown (rc) and
- periodic execution of commands (cron)
+ OpenPKG tries to not touch the operating system at all. Only very
+ few adjustments are being done related to user/group accounts,
+ system startup and shutdown (rc) and periodic execution of commands
+ (cron).
<p>
<li><b>Useful preconfiguration</b>
<br>
- Package installations yield useful preconfigurations which allow immediate
- exploration or usage of an application.
+ Package installations yield useful preconfigurations which allow
+ immediate exploration or usage of an application while avoiding
+ unnecessary security threats.
<p>
<li><b>Uninstallable packages</b>
<br>
A OpenPKG package can be removed entirely from the system. Every static
- content is removed automtically while variable data like confiuration and
- logs survive deinstallation. They can be the base of an upgrade or can be
- removed. Locating them is easy due to the clean filesystem structure that
+ content is removed automatically while variable user data like configuration and
+ databases survive deinstallation.
+ Locating user data is easy due to the clean filesystem structure that
OpenPKG enforces.
<p>
<li><b>Powerful queries</b>
@@ -129,14 +131,14 @@
RPM already provides powerful query mechanisms allowing insight view to
any package, list everything from textual description down to the
attributes of a single file. Never again be in doubt what the original
- permissons of the file you just accidently touched have been. OpenPKG has
- been desingend to provide as many useful informations as query results as
+ permissions of the file you just accidentally touched have been. OpenPKG has
+ been designed to provide as many useful informations as query results as
possible.
<p>
<li><b>Run-command facility</b>
<br>
The run-command facility makes it easy to enable or disable, run, stop,
- restart or reload daemons. Best of all, it works consistant across all
+ restart or reload daemons. Best of all, it works consistent across all
platforms.
</ul>
@@ -156,7 +158,7 @@
<li><b>Open source software</b>
<br>
OpenPKG is open source software. In the (unlikely) event you push it to
- the limits, have exhausted any documention or suspect you found a bug you
+ the limits, have exhausted any documentation or suspect you found a bug you
have full access to the source. This allows you to have an in-depth view
behind the scenes and we won't stop you if you proceed and tailor OpenPKG
to your needs.
@@ -167,14 +169,14 @@
<p>
<li><b>Dependencies for build and runtime</b>
<br>
- Source package include information for build-dependencies and binary
- packages include information for runtime- (aka install-) dependencies.
+ Source package include information for build dependencies and binary
+ packages include information for install dependencies.
<p>
<li><b>Clean and compact package specifications</b>
<br>
The one single <code>.spec</code> file is the ultimate source for any
information regarding the package from user viewable description over
- compiler options to install targes. It's all there.
+ compiler options to install targets. It's all there.
<p>
<li><b>Run-command facility</b>
<br>
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
