Hide Forgot
In samba-2.0.5a-1.i386.rpm and/or samba-client-2.0.5a-1.i386.rpm, there are two links that are mis-named: /etc/init.d/rc3.d/K35smb /etc/init.d/rc5.d/K35smb These links both point to the file /etc/rc.d/init.d/smb, which is correct. However, the NAMES of the links are incorrect. Instead of beginning with "K", they should both begin with "S" to cause samba to be started for runlevels 3 and 5. This bug completely prevents the automatic startup of samba on all systems which have been updated with the above-listed RPMs. This is disastrous for users who don't understand the runlevel mechanism. The simple fix is as follows. After installing the above-listed RPMs, log in as root and type the following commands: cd /etc/init.d/rc3.d mv K35smb S35smb cd /etc/init.d/rc5.d mv K35smb S35smb This will start samba back up. Also, there should be a note to the user that installing updates to samba causes the /etc/smb.conf file to be replaced. The file is saved in /etc/smb.conf.rpmsave, so the old settings can be copied from the old file to the new. However, most users are inept in this area and would prefer that the installation procedure take care of this for them. The end-user reality dictates that any config file that is replaced by an installation must have its settings preserved in the new file (at least the most important settings).
Samba is no longer started by default. If the user wants to start it, they can configure it with chkconfig/ntsysv/tksysv. The smb.conf behavior is the behavior that RPM has always had. It does not attempt to merge configuration files; that way madness lies.