INSTRUCTIONS ON UPGRADING FROM A NON-RPM VERSION OF LINUXCONF
-------------------------------------------------------------

The Old Way
  
Versions of Linuxconf prior to 1.9r25 depended on a boot method using the
concept of a "drop-in" for starting services.  This is a very effective
way of starting and stopping daemons, in which Linuxconf has more control,
and can check to see if the daemon is still running. This, however,
eliminated the standard SysV style of booting that most RedHat users were
accustomed to. This also meant installing a new RPM required making a new
drop-in to start the daemon. Linuxconf replaced the standard /etc/inittab
file to accomplish this boot method, and also made a /etc/rc.d/rc.M file
to handle booting. 

The New Way

Starting with version 1.9r25 of Linuxconf, a new boot method was devised.
The standard SysV boot style was now included, and also gave you the
option of using the drop-in method of starting daemons. Linuxconf now does
not need to replace the /etc/inittab file, and does not need the
/etc/rc.d/rc.M file. 

You now have the best of both worlds. When you install a new RPM that
contains an entry for standard SysV boot, there is no other configuration
needed. If, however, you need the flexibilty and power of the drop-in
method of starting a daemon, it is there. 

Automagic Upgrade From The "Tarball" Linuxconf

This RPM version of Linuxconf detects that you were running an older
version of Linuxconf, and takes the steps necesary to upgrade you to the
newer SysV compliant boot method in the RPM version of Linuxconf. This RPM
will replace your /etc/inittab with a standard RedHat 4.2 inittab, it will
also remove the /etc/rc.d/rc.M file. You need to understand the
implications of changing to the new style of booting before upgrading. 

What Gets Started At Boot Time?

After upgrading to the new style boot, your system will go to the boot
method that RedHat used when it was installed.  Files placed in the
/etc/rc.d/rc(runlevel).d/ directory will be executed at boot time. Also,
any drop-ins you have enabled will be started at boot time. If you have a
drop-in for a daemon that is now started from the rc(runlevel).d
directory, an error will result. It is vital that, after running the
upgrade script you run Linuxconf, go to Control File and Systems -> Edit
Linuxconf's Addons and disable any daemons that will now be started with
the SysV boot method. Most RPM's put startup information into the
rc(runlevel).d directories, so most SysAdmins will simply disable all
drop-ins. 

What Gets Changed When I Upgrade?

The /install directory is removed from your system. The /etc/inittab is
replaced with a stock RedHat 4.2 inittab file (This also works fine with
3.x and any 4.x system).  The /etc/rc.d/rc.M file is removed. Any *.old
files that were put there by old Linuxconf installs are moved to the
proper place for RPM uninstalls. 

I Installed The "Unofficial" RPM version of Linuxconf

This script will detect that, and clean up that install as well. The
1.9r22 "unofficial" RPM basically just untarred the original binary
distribution of Linuxconf, and did not take into account any custom
uninstall for RPM'ed Linuxconf. 

Questions, Comments?

This script is by Dale Lovelace <dale@CentralVa.Net>, so don't go blaming
Jacques if it breaks something :-) Email me if you have any questions, or
comments for a better script, or Linuxconf RPM in general. 
 
PLEASE NOTE: The information in this file applies, for the most
part, to RedHat RPM Installs only!
