OpenPKG CVS Repository
  http://www.openpkg.org/cvsweb/cvsweb.cgi
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Michael Schloh
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-web                      Date:   28-Aug-2002 19:11:42
  Branch: HEAD                             Handle: 2002082818114100

  Modified files:
    openpkg-web/press       PR-002-openpkg-1.1.txt

  Log:
    Some last late corrections.

  Summary:
    Revision    Changes     Path
    1.15        +9  -8      openpkg-web/press/PR-002-openpkg-1.1.txt
  ____________________________________________________________________________

  Index: openpkg-web/press/PR-002-openpkg-1.1.txt
  ============================================================
  $ cvs diff -u -r1.14 -r1.15 PR-002-openpkg-1.1.txt
  --- openpkg-web/press/PR-002-openpkg-1.1.txt  28 Aug 2002 17:09:19 -0000      1.14
  +++ openpkg-web/press/PR-002-openpkg-1.1.txt  28 Aug 2002 17:11:41 -0000      1.15
  @@ -32,13 +32,13 @@
   Previous versions included only the musr/mgrp (manager) and nusr/ngrp
   (nobody) users and groups. OpenPKG 1.1 adds on the susr/sgrp (superuser)
   and rusr/rgrp (restricted user) users and groups. Software can make use
  -of these additional users to better abstract security-sensitive code
  -from generic functionality. OpenPKG 1.1 also encapsulates its software
  -base even more by integrating a 'sane' build environment into each
  -OpenPKG instance. This denies access to system components not residing
  -in OpenPKG's well defined scope, and avoids inconsistency between
  -seemingly identical instances. Also useful in testing, an administrator
  -can now expect reproducible results after each package build.
  +of these additions to better abstract security-sensitive code from
  +generic functionality. OpenPKG 1.1 also encapsulates its software base
  +even more by integrating a 'sane' build environment into each OpenPKG
  +instance. This denies access to system components not residing in
  +OpenPKG's well defined scope, and avoids inconsistency between seemingly
  +identical instances. Also useful in testing, an administrator can now
  +expect reproducible results after each package build.
   
   To relieve cautious administrators, OpenPKG 1.1 software packages do
   not alter system files anymore (like kernel parameters or /etc/shells).
  @@ -49,7 +49,8 @@
   its own instance. As always, the only evidence of an OpenPKG
   introduction are three system entry points (one or two run-command
   scripts, the crontab, and user/group additions). These changes are
  -made only during bootstrapping a new OpenPKG instance.
  +made only during bootstrapping a new OpenPKG instance, and all such
  +changes are completely undone upon uninstallation of OpenPKG.
   
   During activation, all daemon packages inside an OpenPKG instance now
   pay attention to special enable switches. This new feature allows an
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to