1)  Samba adds the "swat" service to /etc/inetd.conf without checking if
the inetd package (netkit-base) is installed.  This gives the user the
false impression that "swat" should be working.

Samba should have netkit-base as a dependency.  Anyone not wanting
netkit-base, and therefore the swat service, can use --nodeps to override.


2)  LinuxConf adds the "linuxconf" service to /etc/inetd.conf without
checking if the inetd package (netkit-base) is installed.  This gives the
user the false impression that "linuxconf" should be working.

LinuxConf should have netkit-base as a dependency.  Anyone not wanting
netkit-base, and therefore the "linuxconf" service, can use --nodeps to
override.


3)  The inetd package (netkit-base) installs without merging changes with
the existing /etc/inetd.conf.  If it does not find one, it creates it with
the default services.  If it finds one, it creates an inetd.rpmsave.  If
for some reason LinuxConf or Samba are installed before netkit-base, the
only two services that will be active are "linuxconf" and "swat", because
netkit-base will see an existing inetd.conf and not overwrite it.  This
means that telnet and FTP are not working.

The inetd package (netkit-base) should do some inet.conf checking upon
installation, rather than the "all or nothing" approach.


Note)  This was noticed in Red Hat 6.1.

I do not have permission to use the person's name who found this.  If she
wants credit, I'm more than happy to give it to her.  She did find it, I
just verified it and reported it.

Don Head
Linux Mentor
Wave Technologies, Inc.
dhead