On Thu, 21 Jan 1999, Jonathan Marsden wrote:
> Any RPM experts out there care to comment on this, and on how to
> prevent RPM (or was it Linuxconf... I'm confused now!) from sticking
> error messages and OK prompts on the console (text mode console I
> presume) when noone is logged in there and rpm is run from some other
> pty? It does sound like, um, less-than-optimal behaviour :-)
THe problem comes from the call to "linuxconf --setmod" in the upgrade
process. The RPM do little scans to find out if some packages are
installed and enable the corresponding modules. For example, if you have a
file /etc/named.conf or /etc/named.boot, it will enable the dnsconf
module.
Unfortunatly, Linuxconf does this "linuxconf --setmod" command this way
-startup and load all currently enabled modules
-process the command line options.
The problem comes from the fact (documented in the change log) that module
compiled for earlier version of linuxconf are not binary compatible
(source compatible only).
The problem shows up for those who have installed independantly packaged
modules such as managerpm. For example, you were running linuxconf 1.13r9
with managerpm. Fine. Then you upgrade to 1.13r12. During to upgrade
process, you have a new linuxconf binary and an incompatible managerpm
module. So each time the linuxconf rpm is doing its "linuxconf --setmod",
an error message is generated by the module loader.
The solution to this problem will be to process the --setmod and
--unsetmod options early at startup, before loading the module. This will
cure the problem.
This problem did not show up previously because module were binary
compatible.
I will work to clean up this situation. Sorry!
---------------------------------------------------------
Jacques Gelinas <[EMAIL PROTECTED]>
Check out Linuxconf at http://www.solucorp.qc.ca/linuxconf
New modules: mgettyconf, managerpm
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
