release/2.1.6.1

3 files changed, 108 insertions, 0 deletions

diff --git a/release/sysinstall/help/anonftp.hlp b/release/sysinstall/help/anonftp.hlp
new file mode 100644
index 000000000000..e90985e235fe
--- /dev/null
+++ b/release/sysinstall/help/anonftp.hlp
@@ -0,0 +1,19 @@
+This screen allows you to configure the anonymous FTP user.
+
+The following configuration values are editable:
+
+UID:     The user ID you wish to assign to the anonymous FTP user.
+         All files uploaded will be owned by this ID.
+
+Group:   Which group you wish the anonymous FTP user to be in.
+
+Comment: String describing this user in /etc/passwd
+
+
+FTP Root Directory:
+
+        Where files available for anonymous FTP will be kept.
+
+Upload subdirectory:
+
+        Where files uploaded by anonymous FTP users will go.
diff --git a/release/sysinstall/help/apache.hlp b/release/sysinstall/help/apache.hlp
new file mode 100644
index 000000000000..3880dddb2ba6
--- /dev/null
+++ b/release/sysinstall/help/apache.hlp
@@ -0,0 +1,51 @@
+There are two sets of options that the Apache HTTP Server needs.
+
+The first set covers how it operates. These are as follows:
+
+        The "HostName" field is the name of this host, as it is
+        reported to each client connection. Normally, the fully
+        qualified domain name of the host running the server is
+        returned.  If you want this set to something else, however,
+        (usually "www.my.domain") then this can be entered here.
+
+        Additionally, the server needs to know how many connections
+        are allowed at one time - this is the "Max Connections"
+        field. If more than this number of clients attempt to connect
+        at once, the additional connections will be refused. This is
+        used to limit how much system load will be imposed by the HTTP
+        server.
+
+        The "Email Address" field is the address of the person (or
+        system alias) who is the administrator for this web site.  In
+        addition to being used by the Apache Server itself, it is also
+        put at the bottom of the sample web page that is created.
+
+        Finally, the "Default User" and "Default Group" fields specify
+        what user id and group id should be used by the server for
+        remote connections.  Local connections are kept as the UID and
+        GID of the local process.
+
+The second set of options determine what information is made available
+to each client:
+
+        The "Document Root Path" is the top of the tree of documents
+        that are made avaliable. For example, if the value is
+        "/usr/web", then the URL "http://www.foo.com/doc.html" would
+        translate as "/usr/web/doc.html".
+
+        Similarly, the "User Directory" is the location in each user's
+        home directory where their public web documents are
+        stored. Thus if the value if this is "Public", then the URL
+        "http://www.foo.com/~joe/doc" would translate to the path
+        "~joe/Public/doc".
+
+        Finally, if the URL points to a directory, there is always a
+        "Default Document" that Apache will use. This field holds the
+        name (not the path) of this document. By default, Apache uses
+        the file "index.html". However, some sites may be more used to
+        using the file "welcome.html".
+
+There are a number of other options that can be configured with
+Apache, such as path aliases, masquerading as multiple hosts, server
+child process parameters, and so forth. For more information on these,
+consult the Apache man pages at http://www.apache.org.
diff --git a/release/sysinstall/help/upgrade.hlp b/release/sysinstall/help/upgrade.hlp
new file mode 100644
index 000000000000..283db98080c4
--- /dev/null
+++ b/release/sysinstall/help/upgrade.hlp
@@ -0,0 +1,38 @@
+Welcome to the 2.1.5 (or 2.0.5) -> 2.1.6 upgrade procedure!
+
+It must first be said that this upgrade DOES NOT take a particularly
+sophisticated approach to the upgrade problem, it being more a
+question of providing what seemed "good enough" at the time.  A truly
+polished upgrade that deals properly with the broad spectrum of
+installed 2.0.5 / 2.1 systems would be nice to have, but until that
+gets written what you get is this - the brute-force approach!
+
+What this upgrade will attempt to do is best summarized thusly:
+
+  1.  fsck and mount all file systems chosen in the label editor.
+  2.  Ask for a location to preserve your /etc directory into and do so.
+  3.  Extract all selected distributions on top of your existing system.
+  4.  Copy certain obvious files back from the preserved /etc, leaving the
+      rest of the /etc file merge up to the user.
+  5.  Drop user in a shell so that they may perform that merge before
+      rebooting into the new system.
+
+And that's it!  This "upgrade" is not going to hold your hand in all
+major respects, it's simply provided to make one PART of the upgrade
+easier.
+
+IMPORTANT NOTE: What this upgrade procedure may also do, in fact, is
+completely destroy your system (though much more quickly than you
+would have been able to destroy it yourself). It is simply impossible
+to guarantee that this procedure's crude form of upgrade automation
+will work in all cases and if you do this upgrade without proper
+BACKUPS for any important data then you really must like living life
+close to the edge, that's all we can say!
+
+NOTE to 2.0 users: We're sorry, but the "slice" changes that were
+added in FreeBSD 2.0.5 made automated upgrades pretty difficult due to
+the fact that a complete reinstall is pretty much called for.  Things
+may still *work* after a 2.1 upgrade, but you will also no doubt
+receive many warnings at boot time about non-aligned slices and such;
+we really do recommend a fresh installation for 2.0 systems!  (But
+back up your user data first :-).