[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openpkg-cvs
Subject:    [CVS] OpenPKG: openpkg-web/ flyer.html
From:       "Ralf S. Engelschall" <rse () openpkg ! org>
Date:       2004-06-30 14:07:37
Message-ID: 20040630140737.03BA42FF08A () mail ! openpkg ! org
[Download RAW message or body]

  OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /e/openpkg/cvs                   Email:  rse@openpkg.org
  Module: openpkg-web                      Date:   30-Jun-2004 16:07:37
  Branch: HEAD                             Handle: -NONE-

  Added files:
    openpkg-web             flyer.html

  Log:
    add new flyer

  Summary:
    Revision    Changes     Path
    1.1         +307 -0     openpkg-web/flyer.html
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-web/flyer.html
  ============================================================================
  $ cvs diff -u -r0 -r1.1 flyer.html
  --- /dev/null	2004-06-30 16:07:37.000000000 +0200
  +++ flyer.html	2004-06-30 16:07:37.000000000 +0200
  @@ -0,0 +1,307 @@
  +<html>
  +  <head>
  +    <style type="text/css"><!--
  +    BODY,DIV,SPAN,
  +    TABLE,TR,TD,TH,P,
  +    FONT,UL,OL,LI
  +    FORM,INPUT,
  +    BLOCKQUOTE,A,I,B,EM { font-family: helvetica,lucida,arial,sans-serif; }
  +    TT,CODE,SAMP,PRE { font-family: courier,courier-new,terminal,fixed,monospace; \
font-size: 100%; }  +    PRE A { font-family: \
courier,courier-new,terminal,fixed,monospace; text-decoration: none; font-weight: \
bold; }  +    PRE B { font-family: courier,courier-new,terminal,fixed,monospace; \
font-weight: bold; }  +    A { text-decoration: none; font-weight: bold; }
  +    A:link { text-decoration: none; font-weight: bold; color: #a09080; }
  +    A:visited { text-decoration: none; font-weight: bold; color: #a09080; }
  +    H1 { text-align: center; }
  +    H2 { text-align: center; }
  +    BODY {
  +        background-color: #ffffff;
  +        background-repeat: repeat;
  +        background-position: left top;
  +        margin: 0px;
  +    }
  +    UL {
  +        padding-left: 15px;
  +    }
  +    LI {
  +        list-style-type: square;
  +        margin:     0px;
  +        margin-top: 0px;
  +    }
  +    #head0 { background-color: #cccccc; color: #000000; }
  +    #head1 { background-color: #000000; color: #ffffff; }
  +    #head2 { background-color: #000000; color: #ffffff; }
  +    #head3 { background-color: #000000; color: #ffffff; }
  +    #col1  { background-color: #f0f0f0; color: #000000; }
  +    #col2  { background-color: #e5e0d0; color: #000000; }
  +    #col3  { background-color: #ffffff; color: #000000; }
  +    #logo    { margin-right: 60px; }
  +    #brand   { margin-top: 65px; font-family: \
tahoma,helvetica,lucida,arial,sans-serif; font-weight: normal; font-size: 200%; }  +  \
#title   { font-family: tahoma,helvetica,lucida,arial,sans-serif; font-weight: bold; \
font-size: 300%; }  +    div.head { font-family: helvetica,lucida,arial,sans-serif; \
font-weight: bold; font-size: 200%; }  +    table#more {
  +        border: 1px solid #cccccc;
  +        padding: 10px;
  +        background: #f5f5f5;
  +    }
  +    table#more h1 {
  +        font-family: helvetica,lucida,arial,sans-serif; font-weight: bold; \
font-size: 160%;  +    }
  +    table#more a {
  +        color: #000000;
  +    }
  +    --></style>
  +    <title>Facts and Features</title>
  +  </head>
  +  <body>
  +
  +<table cellspacing=0 cellpadding=10>
  +<tr>
  +<td colspan=3 align=center id=head0>
  +
  +<table><tr><td>
  +<img src="openpkg.gif" id=logo>
  +</td>
  +<td>
  +<div id=brand>Cross-Platform Unix Software Packaging</div>
  +<div id=title>Facts and Features</div>
  +</td></tr></table>
  +
  +</td>
  +</tr>
  +
  +<tr>
  +<td width=30% valign=top align=center id=head1>
  +
  +<a name="manager">
  +<div class=head>IT Managers</div>
  +</a>
  +
  +</td>
  +<td width=40% align=center id=head2>
  +
  +<a name="admin">
  +<div class=head>System Administrators</div>
  +</a>
  +
  +</td>
  +<td width=30% align=center id=head3>
  +
  +<a name="developer">
  +<div class=head>Package Developers</div>
  +</a>
  +
  +</td>
  +</tr>
  +<tr>
  +<td width=30% id=col1 valign=top>
  +
  +<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>
  +<center>
  +  <img src="box-med-2.0.png">
  +</center>
  +
  +<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>
  +
  +</td>
  +<td width=40% valign=top id=col2>
  +
  +<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 not to 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>
  +
  +</td>
  +<td width=30% valign=top id=col3>
  +
  +<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>
  +<center>
  +  <img src="doc/articles/sysadmin/article.logo.png">
  +</center>
  +<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>
  +
  +<p>
  +<center>
  +  <table id=more><tr><td>
  +  <h1>More Information</h1>
  +  <p>
  +  Summary Slideset:<br>
  +  <a href="doc/slideset/openpkg/"><img
  +  src="doc/slideset/openpkg/slide-001-t.png" alt="Slideset" border=1></a>
  +  <p>
  +  Project Website:<br>
  +  <a href="http://www.openpkg.org/">http://www.openpkg.org/<br>
  +  </td></tr></table>
  +</center>
  +
  +</td>
  +</tr>
  +</table>
  +
  +</body>
  +</html>
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     openpkg-cvs@openpkg.org


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic