linuxconf 1.16 changes log

linuxconf 1.16 changes log

previous versions: 1.15r3.1
Change log index
1.16 is not that different from 1.15r3. Minor enhancements. See the topic about Red-Hat 6.0 though.

Enhancements

fsconf --updatequota option

the --updatequota option has been added to /sbin/fsconf. It walks all user account and apply configure disk quotas. This function is useful when you add user account manually (without Linuxconf). For example if you use useradd to create a bunch of accounts, those won't have suitable disk quota settings. By doing

       /sbin/fsconf --updatequota

you apply the various defaults (global and group) to these accounts. If you only create new accounts using Linuxconf, then you do not need to use this.

pppdialin: no default local IP

The pppdialin lets you configure the local IP, either in the default configuration, or selectively in each account. If you fail to specify a default pppdialin will select the IP number of the eth0 adaptor. In some special case, you want the client to allocate both IP number (local and remote). You can now specify "none" as the local IP. There is a help list showing that. When you enter none, the /usr/lib/linuxconf/lib/ppplogin script will assume that the client is supplying the local IP.

Red-Hat 6.0 compatibility

Prior to 1.16, my own RPM could not installed properly on rh6.0. The problem was in the packaging, not in the source, as there is very little difference between the Linuxconf supplied by Red Hat and mine (well, 1.14r4 is getting old now :-) ).

There were 2 issues with packaging. The first is that my RPM is built to install on several distribution and it was confused on 6.0. It was installing Linuxconf on 6.0 the same way it was installing on Red-Hat 4.x. Problem.

The second problem made the first much more ... visible, to say the least. In Red Hat Linuxconf 1.14r4, they did a correct enhancement to the RPM. They simply defined /etc/conf.linuxconf as a configuration file. They did it properly, using the noreplace feature.

Unfortunately, my own RPM do not do this. So when you upgrade to say 1.15r3, rpm do the following:

  • 1.14r4 does have a config file /etc/conf.linuxconf
  • 1.15r3 does not have one
  • /etc/conf.linuxconf is not needed anymore, erase it. Hum. No this is a config file, so keep it, but rename it to /etc/conf.linuxconf.rpmsave to show that it is not needed anymore.

So after the upgrade to 1.15r3, you end up with no /etc/conf.linuxconf. If you rename /etc/conf.linuxconf.rpmsave to /etc/conf.linuxconf, things may go better. Failure to do that cause Linuxconf to fail (segfault). Not good.

1.16 now include this config file directive, so upgrading from original redhat 1.14r4 package will go well. Upgrading from my own older package will produce a warning that a the file /etc/conf.linuxconf.rpmnew was created. Rpm does this because it see that the previous Linuxconf package did not have a /etc/conf.linuxconf file, but the new one has one. The noreplace directive tells rpm to keep the current one in place. It creates the rpmnew version to show you that a new file was added to the package, but could not replace an old file on the system.

Anyway, sorry for a long explanation. What does this means to all you rpm users around, and non-redhat rpm users. It means that

  • You can upgrade to 1.16 without worrying.
  • You can't downgrade, unless you manually rename /etc/conf.linuxconf.rpmsave to /etc/conf.linuxconf after the upgrade. If you forget, Linuxconf will tell you (It will segfault).

    Note that this downgrade limitation (problem) will cure all by itself. the problem arises when going from a package which miss and RPM directive about /etc/conf.linuxconf. So downgrading from 1.16r4 to 1.16r3 won't be a problem.

Sorry, I did not find a way out of this. I hope I am not scaring you too much.

samba: security = user, server or share

The security mode could not be configured from Linuxconf. I have added a field for that in the default configuration, so you can pick one of the 3 values: user server share.