Chris, thanks for your explanation. Is it for the same reason that "services" (those part of /etc/rc.d) are not restarted when they are updated? Op zaterdag 19 januari 2002 00:03, schreef Christopher Mahmood:
* Richard Bos (allabos@freeler.nl) [020118 14:55]:
I don't understand why the mk_initrd and lilo sequence are not part of the post installation scripts of the RPMs, since those steps must be taken, anyway.
Because there's no way for a post-install script to know whether /etc/rc.config:INITRD_MODULES. SInce the initrd isn't isn't
Is this the complete phrase you intended to send. It seems your interesting explanation about /etc/rc.config:INITRD_MODULES is not finished.
Doh. "Because there's no way for a post-install script to know whether /etc/rc.config:INITRD_MODULES is correct." Thanks.
Ah ha. Does the user/administrator know ... ;)
Why wouldn't the rpm post script be able to process the /etc/rc.config file or to call mk_initrd??
Sure, mk_initrd already does source rc.config to get INITRD_MODULES. I mean, if you really want to do it all with one carriage return rpm -Uvh new_kernel.rpm && mk_initrd && lilo && init 6
It's not that I want it to be on 1 line, but when updating 50 packages it would be nice that mk_initrd/lilo are called when needed. Same will be valid for restarting services. This is especially true when doing a bulk update at many machines. It is of course possible to develop a wrapper around rpm, that does al this, isn't it. BTW: is /sbin/SuSEconfig --module executed by the rpm post script, or must this always be done afterwards by the user? -- Richard Bos For those without home the journey is endless