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:17:44
Branch: HEAD Handle: 2002082817174400
Modified files:
openpkg-web/press PR-002-openpkg-1.1.txt
Log:
Added press release body text.
Summary:
Revision Changes Path
1.8 +51 -41 openpkg-web/press/PR-002-openpkg-1.1.txt
____________________________________________________________________________
Index: openpkg-web/press/PR-002-openpkg-1.1.txt
============================================================
$ cvs diff -u -r1.7 -r1.8 PR-002-openpkg-1.1.txt
--- openpkg-web/press/PR-002-openpkg-1.1.txt 28 Aug 2002 14:20:05 -0000 1.7
+++ openpkg-web/press/PR-002-openpkg-1.1.txt 28 Aug 2002 16:17:44 -0000 1.8
@@ -14,48 +14,58 @@
additional system layer on top of the operating system. With OpenPKG, a
new and unique method of software deployment is taking form.
-------------------------------------------------------------------------------
+Apart from the advantages of earlier OpenPKG releases, OpenPKG 1.1 offers even
+more. Previously with 167 packages, the official OpenPKG repostitory 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 assesment.
+
+Administrators have asked for more portability, and OpenPKG has responded by
+increasing its supported platform requirements by 100%. Previously
+on only three platforms, OpenPKG now enjoys 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 funcionality. 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 reproducable 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 buildtime. This allows an administrator to install software
+with optional features, and build precustomized 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'.
-The release 1.1...
-...
-
- o more and upgraded packages: 167 -> 274 (CORE:21 BASE:150 PLUS:103)
-
- o more supported platforms: 3 -> 6
- FreeBSD 4.4 -> FreeBSD 4.6
- - -> RedHat 7.2
- Debian GNU/Linux 2.2 -> Debian GNU/Linux 2.2
- - -> Debian GNU/Linux 3.0
- Solaris 8 -> Solaris 8
- - -> Solaris 9
-
- o use of 4 user accounts for finer security granularity
- - fsusr/fsgrp -> musr/mgrp - manager
- - npusr/npgrp -> nusr/ngrp - nobody
- - (new) susr/sgrp - superuser
- - (new) rusr/rgrp - restricted user
-
- o no packages (except for openpkg selbst) alter system files
- - no (more) editing of /etc/shells (bash, tcsh, pdksh, ksh, zsh)
- - kernel parameters remain unchanged
- - info/ warning/ error is printed and must be resolved manually
-
- o openpkg bootstrap package contains RPM libraries/headers
- (to support RPM frontends)
-
- o RPM proxy package support (rpm --makeproxy)
-
- o sane build environment: security and robustness
- - truly encapsulates functionality, for reproducable results
-
- o full package cleanups:
- - all daemons (have run-commands) can be disabled (instead of deinstalled)
- - no more package specfile editing: uses RPM --define switch switched to
with_xxxx for optional feature enabling
- - available options in comments, query using -qpi
- - used options in comments, query using -qi (poor man's documentation)
-...
-
-------------------------------------------------------------------------------
+To support RPM frontends, 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]
