OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Ralf S. Engelschall
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 19-Sep-2002 11:28:29
Branch: HEAD Handle: 2002091910282800
Modified files:
openpkg-doc/articles/sysadmin
article.txt
Log:
take over corrections send to SysAdmin
Summary:
Revision Changes Path
1.130 +8 -8 openpkg-doc/articles/sysadmin/article.txt
____________________________________________________________________________
Index: openpkg-doc/articles/sysadmin/article.txt
============================================================
$ cvs diff -u -r1.129 -r1.130 article.txt
--- openpkg-doc/articles/sysadmin/article.txt 19 Sep 2002 08:02:12 -0000 1.129
+++ openpkg-doc/articles/sysadmin/article.txt 19 Sep 2002 09:28:28 -0000 1.130
@@ -162,8 +162,8 @@
system support and tools to unpack and compile itself. In the best case,
the script will search the C<$PATH> for the development tools C<tar>,
C<make> and C<cc> and use them in its processing. If any of these tools
-are not present, an alternative approach exists in which the binary
-version of the shell script is used instead.
+are missing, an alternative approach exists in which a shell script
+containing binaries provides the missing tools.
The first step in bootstrapping involves dedicating a unique
file system prefix to the instance along with user and
@@ -255,7 +255,7 @@
before saving a new default in its place. This ensures that changes to a
default configuration can be recovered and reapplied so that an upgraded
package runs correctly. Should a new default configuration file replace
-an old one that retains its original (but old) RPM default, RPM renames
+an old one that retains its original (but old) RPM default, RPM will rename
it with the extension C<.rpmorig>.
To make this delightful mechanism work properly, the configuration files
@@ -269,7 +269,7 @@
its information. The command C<rpm -qi >I<pkg-name> summarizes a single
installed package, while C<rpm -qa> lists the names of all installed
packages. C<rpm -qlv >I<pkg-name> lists all the files associated with a
-package and C<rpm -qf>I<prefix>/I<path>/I<to>/I<file> reveals to which
+package and C<rpm -qf >I<prefix>/I<path>/I<to>/I<file> reveals to which
package the given file belongs. You can even check a package's integrity
using C<rpm -V >I<pkg-name> to verify which files have been tampered
with or somehow munged. For more details on this refer to Table_3.
@@ -281,7 +281,7 @@
RSYNC, the server was started using the command C</usr/opkg/etc/rc
rsync start>. The workhorse behind this simple statement is
the powerful OpenPKG run-command facility, executed with
-I<prefix>C</etc/rc>. Run commands for every package are conveniently
+I<prefix>C</etc/rc>. Run-commands for every package are conveniently
named I<prefix>C</etc/rc.d/rc.>I<pkg-name>. What each of them offers
is the functionality of several shell script segments encapsulated in
a single file. The sections of a run-command file are identified by
@@ -339,7 +339,7 @@
be quite useful when installing a package just to get a client piece.
Should the server piece not be of interest, then a simple variable
shuts it off completely. Similarly, to disable the automatic startup
-of all daemons in a hierarchy, just add a C<openpkg_ignall="yes"> to
+of all daemons in a hierarchy, just add a C<openpkg_runall="no"> to
I<prefix>C</etc/rc.conf>. In this case, daemons can still be started
manually. This feature may be of interest to system administrators
wanting control over daemons with finer granularity.
@@ -415,7 +415,7 @@
This allows safe (no development system intrusion) and precise (no
trashed or missing files) packaging. Such security and precision
is achieved by consistently using the C<BuildRoot> feature of RPM
-for all packages. In short, this means that when rolling a binary
+for I<all> packages. In short, this means that when rolling a binary
package the software is redirected to install into a shadow area
(I<prefix>C</RPM/TMP/>I<pkg-name>C<-root/>I<prefix>). The package is
then made from the shadow area just as if it were located in the real
@@ -498,7 +498,7 @@
in a publicly readable central CVS repository, which can be browsed
anonymously by conventional C<cvs> commands or through the website
for added convenience. Additionally, all developer commits to this
-repository are tracked and summarized with postings to a public mailing
+repository are tracked and summarized with postings to public mailing
lists and public newsgroups. People can easily follow all developments
by subscribing to the list or reading the newsgroup.
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
