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 18:44:48
Branch: HEAD Handle: 2002082817444800
Modified files:
openpkg-web/press PR-002-openpkg-1.1.txt
Log:
Small corrections, improvements, and polishing.
Summary:
Revision Changes Path
1.10 +57 -51 openpkg-web/press/PR-002-openpkg-1.1.txt
____________________________________________________________________________
Index: openpkg-web/press/PR-002-openpkg-1.1.txt
============================================================
$ cvs diff -u -r1.9 -r1.10 PR-002-openpkg-1.1.txt
--- openpkg-web/press/PR-002-openpkg-1.1.txt 28 Aug 2002 16:34:50 -0000 1.9
+++ openpkg-web/press/PR-002-openpkg-1.1.txt 28 Aug 2002 16:44:48 -0000 1.10
@@ -14,58 +14,64 @@
additional system layer on top of the operating system. With OpenPKG, a
new and unique method of software deployment is taking form.
-Compared with earlier releases, OpenPKG 1.1 offers even
-more. Previously with 167 packages, the official OpenPKG repository has grown
-by 64% to include 274 software packages. Preexisting packages are in top form
-after upgrades to newer versions. Packages are also now divided into CORE, BASE,
-and PLUS categories for more accurate security assessment.
-
-Administrators have asked for more portability, and OpenPKG has responded by
-increasing its supported platform requirements by 100%. Previously
-on only three platforms, OpenPKG users now enjoy official support on FreeBSD 4.6,
-RedHat 7.2, Debian 2.2, Debian 3.0, Solaris 8, and Solaris 9.
-
-Security research and testing has resulted in more flexible user accounting,
-with finer granularity and control. Previous versions included only the
-musr/mgrp (manager) and nusr/ngrp (nobody) users and groups. OpenPKG 1.1
-additionally offers 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.
-
-To relieve cautious administrators, OpenPKG 1.1 software packages do not alter
-system files anymore (like kernel parameters or /etc/shells). In cases where
-such alteration is needed, OpenPKG recommends changes that the administrator
-must manually undertake. Such recommendation is avoided however, and OpenPKG
-takes this course only when it cannot provide the needed functionality inside
-the borders of 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.
-
-During activation, all daemon packages inside an OpenPKG instance now pay
-attention to their corresponding enable switches. This allows an administrator
-to merely deactivate a daemon by setting a switch variable, whereas previously
-a daemon package had to be completely deinstalled. To avoid the precarious
-editing of an OpenPKG specification file, a '--define' option is now available
-during package build time. This feature allows an administrator to install
-software with optional features, and build custom binary packages. The results
-of normal RPM queries (rpm -qi or rpm -qpi) include descriptions of any
-optional features that a package offers.
-
-Generic proxy packages are supported by OpenPKG 1.1, and allow an
-administrator to reduce a system's complexity through abstraction. Should
-software in several OpenPKG instances depend on a general base package, it can
-now be installed only once in an arbitrary OpenPKG instance. Dependents can
-refer to such foreign base packages through natively installed proxies,
-created with the OpenPKG command 'rpm --makeproxy'.
+Compared with earlier releases, OpenPKG 1.1 offers even more.
+Previously with 167 packages, the official OpenPKG repository has
+grown by 64% to include 274 software packages. Preexisting packages
+are in top form after upgrades to newer versions. Packages are also
+now divided into CORE, BASE, and PLUS categories for more accurate
+security assessment.
+
+Administrators have asked for more portability, and OpenPKG has
+responded by increasing its supported platform requirements by 100%.
+Previously on only three platforms, OpenPKG users now enjoy official
+support on FreeBSD 4.6, RedHat 7.2, Debian 2.2, Debian 3.0, Solaris 8,
+and Solaris 9.
+
+Improvements in OpenPKG's inherently strong security model now provide
+more flexible user accounting, with finer granularity and control.
+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.
+
+To relieve cautious administrators, OpenPKG 1.1 software packages do
+not alter system files anymore (like kernel parameters or /etc/shells).
+In cases where such alteration is needed, OpenPKG recommends changes
+that the administrator must manually undertake. Even such
+recommendation is avoided however, and OpenPKG takes this course only
+when it cannot provide the needed functionality inside the borders of
+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.
+
+During activation, all daemon packages inside an OpenPKG instance now
+pay attention to special enable switches. This new feature allows an
+administrator to deactivate a daemon by merely setting a switch
+variable to 'yes' or 'no', whereas previously a daemon package had to
+be completely uninstalled. To avoid the precarious editing of an
+OpenPKG specification file, a '--define' option is now available
+during package build time. This new feature allows an administrator
+to install software with optional arguments, and thereby build custom
+binary packages. The results of normal RPM queries (rpm -qi or rpm -qpi)
+include descriptions of any optional features that a package offers.
+
+Generic proxy packages are first supported in OpenPKG 1.1, and allow
+an administrator to reduce system complexity through abstraction.
+Should software in several OpenPKG instances depend on a general base
+package, it can now be installed only once in an arbitrary OpenPKG
+instance. Dependents can refer to such foreign base packages through
+natively installed proxies, created with the OpenPKG command 'rpm
+--makeproxy'.
-To support third party RPM software, OpenPKG 1.1 installs RPM libraries and
-headers during bootstrapping.
+To support third party RPM software, OpenPKG 1.1 installs RPM
+libraries and headers during bootstrapping.
HIGHLIGHTS OF OPENPKG
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
