rpm packaging guideline question: differentiating between live/chroot installs?

[Jesse Keating]

On Thu, 2006-06-22 at 18:55 -0700, Jane Dogalt wrote:
> So what about the case of an update to kernel module?  Is it then the
> responsibility of the installer (be it a script or a human) to rmmod
> the old
> module, (or close the app which closes the device which(?) autounloads
> the
> module), so that the next time the module is needed, the new module is
> autoloaded?
> 

Correct.  Make it available but don't auto switch to it.  Think of the
case of graphics modules.  They get put in place and the next time the
user unloads X and then loads it again, the new module will get used.

-- 
Jesse Keating RHCE      (geek.j2solutions.net)
Fedora Legacy Team      (www.fedoralegacy.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20060623/31679005/attachment.sig>