OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-adm Date: 29-Aug-2002 12:08:07
Branch: HEAD Handle: 2002082911080600
Modified files:
openpkg-adm upgrade.txt
Log:
PAM and removed packages
Summary:
Revision Changes Path
1.7 +41 -18 openpkg-adm/upgrade.txt
____________________________________________________________________________
Index: openpkg-adm/upgrade.txt
============================================================
$ cvs diff -u -r1.6 -r1.7 upgrade.txt
--- openpkg-adm/upgrade.txt 29 Aug 2002 09:20:06 -0000 1.6
+++ openpkg-adm/upgrade.txt 29 Aug 2002 10:08:06 -0000 1.7
@@ -8,29 +8,38 @@
Upgrade from OpenPKG 1.0 to OpenPKG 1.1
=======================================
- o Additional accounts:
+ o Additional user accounts
- Additional user accounts will be added to the system. The new UIDs
+ OpenPKG 1.1 adds additional user accounts to the system. The new UIDs
are not used by the bootstrap itself and can be changed by manually
configuring the system files immediately after the upgrade. Do not
modify them after any dependent packages were installed (i.e. postfix
and sendmail) as these packages might compile UIDs into the binary.
- o rsync rc.conf Variables:
+ o Removed Packages
+
+ OpenPKG 1.1 does not include autogen, guile, imapd and sfio. They
+ have been put into EVAL or JUNK classes and are only available as
+ CURRENT packages which can be downloaded as source RPMs from
+ ftp://ftp.openpkg.org/CURRENT/SRC/.
+
+ o Inconsistent rc.conf variables in rsync
- Previously the rsync package used (inconsistently) rc.conf variables
- with prefix "rsyncd_". This was now corrected to be "rsync_". You
- have to manually change your existing rc.conf entries.
-
- o bind v8/v9:
-
- In OpenPKG 1.1 the "bind" package is based on BIND 9 so the
- package is named "bind-9.x.x-1.1.x". The old OpenPKG 1.0 package
- "bind-8.x.x-1.0.0" became "bind8-8.x.x-1.1.0". This means you have
- to deinstall "bind" and install from scratch "bind8" if you want to
- stick with BIND 8. Make sure you backup <prefix>/etc/bind/ first.
+ Previously the rsync package inconsistently used rc.conf variables
+ with prefix "rsyncd_". This was now corrected to be "rsync_". The
+ entries in rc.conf have to be corrected manually.
+
+ o BIND8 vs BIND9
+
+ In OpenPKG 1.1 the "bind" package is based on BIND9 where OpenPKG
+ 1.0 used BIND8. The old package was renamed to "bind8" to support
+ installations which depend on BIND8. Because the package name
+ changed, RPM treats it as two different packages. The configuration
+ of the old package must be backed up manually, then the old package
+ needs to be removed. Finally the new "bind8" package must be
+ installed and configuration recovered manually.
- o PAM:
+ o PAM
In OpenPKG 1.0 some daemon packages by default had PAM support
enabled. Unfortunately PAM makes trouble in a cross-platform
@@ -39,9 +48,23 @@
through a --define "with_pam yes" during build-time. This now
requires the "pam" glue package to be installed first. This "pam"
package now takes over the task of re-configuring the /etc/pam.d/ or
- /etc/pam.conf in a consistent way.
+ /etc/pam.conf in a consistent way. The following table compares
+ PAM support between this and the previous OpenPKG release.
+
+ OpenPKG 1.0 OpenPKG 1.1 PAM support in OpenPKG 1.1
+ --------------------------------------------------------------------
+ apache apache %with_mod_auth_pam
+ imapd n/a package removed
+ openldap openldap no PAM support
+ openssh openssh %with_pam
+ proftpd proftpd %with_pam
+ pureftpd pureftpd %with_pam
+ qpopper qpopper %with_pam
+ samba samba %with_pam
+ n/a sasl %with_pam; new package
+ sudo sudo %with_pam
- o Bootstrapping and C Compiler:
+ o Bootstrapping and C Compiler
For machines which do not have any C compiler at all (Solaris!), you
usually have to install a gcc via binary somewhere. If it is outside
@@ -49,7 +72,7 @@
from finding and using it. To tell OpenPKG about this "cc" you have to
add an ~/.rpmmacros with "%with_cc /path/to/this/bootstrap/cc".
- o Shared Libraries:
+ o Shared Libraries
OpenPKG still has the policy of not using shared libraries for
cross-platform reasons. Nevertheless by accident some OpenPKG 1.0
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
