head	1.11;
access;
symbols;
locks; strict;
comment	@# @;


1.11
date	2004.06.30.14.14.46;	author rse;	state dead;
branches;
next	1.10;

1.10
date	2004.06.30.12.53.44;	author rse;	state Exp;
branches;
next	1.9;

1.9
date	2003.08.07.14.17.18;	author thl;	state Exp;
branches;
next	1.8;

1.8
date	2003.04.02.10.04.35;	author thl;	state Exp;
branches;
next	1.7;

1.7
date	2003.01.22.13.12.54;	author rse;	state Exp;
branches;
next	1.6;

1.6
date	2002.03.28.15.04.55;	author thl;	state Exp;
branches;
next	1.5;

1.5
date	2002.01.11.18.10.35;	author rse;	state Exp;
branches;
next	1.4;

1.4
date	2001.12.04.08.53.22;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2001.12.03.16.30.38;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2001.12.03.15.56.25;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2001.12.03.15.24.07;	author rse;	state Exp;
branches;
next	;


desc
@@


1.11
log
@remove old facts in favor of flyer
@
text
@
#use "page.inc" page=facts

<title>Facts and Features</title>

<h1>Facts and Features</h1>

These are facts about and features of OpenPKG concerning 
IT <a href="#manager">managers</a>, 
system <a href="#admin">administrators</a> and engineers and
software package system <a href="#developer">developers</a>.

<a name="manager">
<h2>IT Managers</h2>
</a>

<ul>
<li><b>Cost reduction</b>
    <br>
    If the unified approach of OpenPKG is used, the cross-platform Unix
    system administration costs can be reduced substantially. Experience
    shows that a factor of 50% is expectable. This way resources can
    be freed and the efforts spent on important service improvements
    instead of wasting them for tedious administration tasks only.
<p>
<li><b>Open source software</b>
    <br>
    OpenPKG is <a href="http://www.opensource.org/">Open Source</a> software.
    You don't have to pay any license fees but nevertheless receive a high
    quality application created by enthusiastic developers which are
    experienced system administrators and know what they're doing.
<p>
<li><b>High quality consistent installation</b>
    <br>
    Your engineers need no experience in package porting. They just install
    and concentrate on their primary task of configuring the applications.
    This makes installations consistent and more reliable.
<p>
<li><b>Multiple instances</b>
    <br>
    Need virtual servers? OpenPKG is good for you! It can be installed more
    than once on a single machine squeezing out everything the device can
    offer.
<p>
<li><b>Built-in porting knowledge</b>
    <br>
    Application packages were build by experienced developers with portability
    in mind. Take advantage of that free service.
<p>
<li><b>Cross platform</b>
    <br>
    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.
<p>
<li><b>Minimum OS dependencies</b>
    <br>
    A OpenPKG installation has minimum dependencies to the underlying
    operating system.  In fact, OpenPKG ignores most packages bundled with the
    OS.  Withdraw any items from your customer meetings discussion list that
    favor one operating system over the other because of vendor supplied or
    omitted packages. You're free now.
</ul>

<a name="admin">
<h2>System Administrators and Engineers</h2>
</a>

<ul>
<li><b>Signed packages</b>
    <br>
    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 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 any executable.
<p>
<li><b>Self contained Packages</b>
    <br>
    A OpenPKG package contains either source and instructions to create or
    binaries to install an application. If the build or install process
    depends on other packages, OpenPKG will tell you about these dependencies
    and halt the process until you resolve the dependencies installing related
    OpenPKG packages. You don't have to touch the base operating system ever.
<p>
<li><b>Support for unprivileged user</b>
    <br>
    Unless a package explicitly requires root privileges, i.e. a network
    daemon listing on a UDP/TCP port below 1024, a user can place a private
    instance of OpenPKG in any writable location like his home directory.
<p>
<li><b>Arbitrary prefix</b>
    <br>
    Although our binary packages are usually build for the hardcoded /cw
    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 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 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 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 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 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>
    <br>
    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
    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 consistent across all
    platforms.
</ul>

<a name="developer">
<h2>Software Package Developers</h2>
</a>

<ul>
<li><b>Support for entire package lifecycle</b>
    <br>
    With OpenPKG you create packages from original tar-balls. You specify
    instructions how to fetch original sources and patches, commands to bundle
    everything together into a source RPM and list how to build a binary RPM.
    All instructions are placed in a single <C>.spec</C> file which is more or
    less a shell script.
<p>
<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 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.
<p>
<li><b>Support for unprivileged user</b>
    <br>
    All packages can be build without having root access to the system.
<p>
<li><b>Dependencies for build and runtime</b>
    <br>
    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 targets. It's all there.
<p>
<li><b>Run-command facility</b>
    <br>
    A powerful run-command facility unifies the startup and shutdown as well as
    the periodic (cron) scripting across all platforms.  Every package has all
    necessary shell commands for actions related to run, stop, restart and
    reload daemons in a single file. Commands for periodic execution are
    placed there as well.
</ul>
@


1.10
log
@more facts for managers
@
text
@@


1.9
log
@update, correct and spell check facts
@
text
@d18 8
d42 1
a42 1
    than once on a single machine squeezing out what everything the device can
d53 1
a53 1
    CPUs.  On any system the behavior of OpenPKG is the same so engineers
@


1.8
log
@correct spelling of "privileges"
@
text
@d44 3
a46 3
    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
d70 1
a70 1
    includes the content you expect without any damage or suprises inside.
d76 1
a76 1
    last filesystem check did not damage your executeables.
d98 1
a98 1
    matter of CPU horsepower provided you have the source RPMs.
d104 1
a104 1
    tweaks and quirks out of many packages. Assume network daemons will
d110 4
a113 3
    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)
d117 3
a119 2
    Package installations yield useful preconfigurations which allow immediate
    exploration or usage of an application.
d124 3
a126 3
    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
d134 2
a135 2
    permissons of the file you just accidently touched have been. OpenPKG has
    been desingend to provide as many useful informations as query results as
d141 1
a141 1
    restart or reload daemons. Best of all, it works consistant across all
d161 1
a161 1
    the limits, have exhausted any documention or suspect you found a bug you
d172 2
a173 2
    Source package include information for build-dependencies and binary
    packages include information for runtime- (aka install-) dependencies.
d179 1
a179 1
    compiler options to install targes. It's all there.
@


1.7
log
@flush everything prepared for OpenPKG 1.2
@
text
@d86 1
a86 1
<li><b>Support for unpriviledged user</b>
d164 1
a164 1
<li><b>Support for unpriviledged user</b>
@


1.6
log
@consequently use run DASH command facility
@
text
@d14 1
a14 1
<h2>IT managers</h2>
d19 1
a19 1
    <p>
d26 1
a26 1
    <p>
d32 1
a32 1
    <p>
d38 1
a38 1
    <p>
d43 1
a43 1
    <p>
d52 1
a52 1
    <p>
d61 1
a61 1
<h2>System administrators and engineers</h2>
d66 1
a66 1
    <p>
d73 1
a73 1
    <p>
d79 1
a79 1
    <p>
d87 1
a87 1
    <p>
d93 1
a93 1
    <p>
d101 1
a101 1
    <p>
d109 1
a109 1
    <p>
d115 1
a115 1
    <p>
d120 1
a120 1
    <p>
d128 1
a128 1
    <p>
d137 1
a137 1
    <p>
d144 1
a144 1
<h2>Software package developers</h2>
d149 1
a149 1
    <p>
d157 1
a157 1
    <p>
d165 1
a165 1
    <p>
d169 1
a169 1
    <p>
d174 1
a174 1
    <p>
d180 1
a180 1
    <p>
@


1.5
log
@important negation
@
text
@d136 1
a136 1
<li><b>Runcommand facility</b>
d138 1
a138 1
    The runcommand facility makes it easy to enable or disable, run, stop,
d179 1
a179 1
<li><b>Runcommand facility</b>
d181 1
a181 1
    A powerful runcommand facility unifies the startup and shutdown as well as
@


1.4
log
@facts and features - complete
@
text
@d106 1
a106 1
    to their own to the common system <i>var</i> area.
@


1.3
log
@fix markup and use a little bit indentation
@
text
@d8 4
a11 4
These are facts about and features of OpenPKG concerning IT <a
href="#manager">managers</a> and software package system <a
href="#admin">administrators</a> and engineers, <a
href="#developer">developers</a>.
d24 1
a24 1

d126 15
d155 1
d178 8
a186 8


<hr>
<h2>FIXME</h2>

<li>powerful queries
<li>runcommands with start, stop and cron

@


1.2
log
@facts and features - integrated more information
@
text
@d13 1
a13 1
<p><a name="manager">
d15 2
d18 40
a57 28
<li>Open source software
<p>OpenPKG is open source software. You don't pay any license fees still receive
a high quality application created by enthusiastic developers which are
experienced system administrators and know what they're doing.
<li>High quality consistent installation
<p>Your engineers need no experience in package porting. They just install and
concentrate on their primary task of configuring the applications. This makes
installations consistent and more reliable.
<li>Multiple instances
<p>Need virtual servers? OpenPKG is good for you! It can be installed more
than once on a single machine squeezing out what everything the device can
offer.
<li>Built-in porting knowledge
<p>Application packages were build by experienced developers with portability
in mind. Take advantage of that free service.
<li>Cross platform
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 significantly reduces
the complexities normally resulting from dissimilar systems. Have your
engineers do application configuration rather than wasting time finding the
differences between systems.
<li>Minimum OS dependencies
<p>A OpenPKG installation has minimum dependencies to the underlying operating
system.  In fact, OpenPKG ignores most packages bundled with the OS.  Withdraw
any items from your customer meetings discussion list that favor one operating
system over the other because of vendor supplied or omitted packages. You're
free now.
d60 1
a60 1
<p><a name="admin">
d62 2
d65 61
a125 44
<li>Signed packages
<p>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.
<li>Package integrity verification
<p>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.
<li>Self contained Packages
<p>A OpenPKG package contains either source and instructions to create or
binaries to install an application. If the build or install process depends on
other packages, OpenPKG will tell you about these dependencies and halt the
process until you resolve the dependencies installing related OpenPKG
packages. You don't have to touch the base operating system ever.
<li>Support for unpriviledged user
<p>Unless a package explicitly requires root privileges, i.e. a network daemon listing on
a UDP/TCP port below 1024, a user can place a private instance of OpenPKG in
any writable location like his home directory.
<li>Arbitrary prefix
<p>Although our binary packages are usually build for the hardcoded /cw 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.
<li>Multiple instances
<p>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 properly
listen to configured not wildcard addresses and applications log to their own
to the common system <i>var</i> area.
<li>Minimal OS intrusion
<p>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)
<li>Useful preconfiguration
<p>Package installations yield useful preconfigurations which allow immediate
exploration or usage of an application.
<li>Uninstallable packages
<p>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 OpenPKG
enforces.
d128 1
a128 1
<p><a name="developer">
d130 2
d133 29
a161 20
<li>Support for entire package lifecycle
<p>With OpenPKG you create packages from original tar-balls. You specify
instructions how to fetch original sources and patches, commands to bundle
everything together into a source RPM and list how to build a binary RPM. All
instructions are placed in a single <C>.spec</C> file which is more or less a
shell script.
<li>Open source software
<p>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 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.
<li>Support for unpriviledged user
<p>All packages can be build without having root access to the system.
<li>Dependencies for build and runtime
<p>Source package include information for build-dependencies and binary packages
include information for runtime- (aka install-) dependencies.
<li>Clean and compact package specifications
<p>The one single <C>.spec</C> 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.
d165 2
a167 2

<hr><h1>FIXME</h1>
@


1.1
log
@facts and features - first cut
@
text
@d31 13
d80 13
d110 8
a117 1
All packages can be build without having root access to the system.
a123 4
<li>minimum dependencies
<li>cross platform CPU OS
<li>clean and compact package specifications
<li>consistent full uninstallable packages
a124 1
<li>dependencies for build and runtime
a125 2
<li>minimal OS intrusion
<li>useful preconfiguration
@