Re: not running depmod at boot time
- To: debian-devel@lists.debian.org
- Subject: Re: not running depmod at boot time
- From: Jörg Sommer <joerg@alea.gnuu.de>
- Date: Sun, 4 Jun 2006 16:52:38 +0000 (UTC)
- Message-id: <[🔎] slrne863um.sot.joerg@alea.gnuu.de>
- References: <20060523185210.GA32518@wonderland.linux.it> <1148471091.13559.4.camel@utena.localnet> <87wtcat70r.fsf@informatik.uni-tuebingen.de> <5fabd6fd0605251942s49c66dfr1102b4fec599683b@mail.gmail.com> <873bexyp7x.fsf@informatik.uni-tuebingen.de> <20060526170119.GA25417@wonderland.linux.it> <877j48crb7.fsf@informatik.uni-tuebingen.de> <20060527092932.GC4141@wonderland.linux.it> <20060527195158.GA22922@rotes76.wohnheim.uni-kl.de> <slrne7hmeq.3fi.joerg@alea.gnuu.de> <20060529081605.GA10607@rotes76.wohnheim.uni-kl.de>
Hallo Eduard,
Eduard Bloch <edi@gmx.de> wrote:
> #include <hallo.h>
> * Jörg Sommer [Sat, May 27 2006, 10:59:39PM]:
>
>> > No, they don't. At least my packages call it only if `uname -r` ==
>> > target version. When you drop the depmod run, and someone installs a new
>> > kernel together with accompanying module packages and only THEN reboots,
>> > the modules.dep* files won't be updated.
>>
>> Why the kernel does not run depmod? Either the modules package or the
>> kernel package is the last one. Marco had explained in one of his mails
>> how to run depmod for a kernel version != `uname -r`. Why this does not
>> work for you?
>>
>> Good night, Jörg.
>
> Causality?!
I've suggested that the kernel package and your packages run depmod in
the postinst script. Then the modules.dep* files be up to date after
every package installation. Or I'm wrong?
Regards, Jörg.
--
A red sign on the door of a physics professor: 'If this sign is blue,
you're going too fast.'
Reply to: