Joey Hess wrote:
Marco d'Itri wrote:
If we can agree that it's not needed anymore (i.e. mandate by policy
that packages need to run depmod on their own) then I will be happy to
remove it from the m-i-t init script.
A while back Debian would only run depmod on boot if it
Marco d'Itri wrote:
I think because depmod --quick is supposed to be about as fast as find.
YM as fast as test -nt? Doesn't seem to be on a dry cache.
--
see shy jo
signature.asc
Description: Digital signature
On May 19, Joey Hess [EMAIL PROTECTED] wrote:
Marco d'Itri wrote:
I think because depmod --quick is supposed to be about as fast as find.
YM as fast as test -nt? Doesn't seem to be on a dry cache.
No, I really meant as fast as find. Which other test do you suggest?
--
ciao,
Marco
On Thu, May 18, 2006 at 07:21:33PM -0300, Margarita Manterola wrote:
Continuing on the goal of optimizing boot time, quite a number of
seconds (specially in old machines) can be saved by not running depmod
at boot time.
Currently it is run by these packages' postinst:
Wouldn't it be a good
Continuing on the goal of optimizing boot time, quite a number of
seconds (specially in old machines) can be saved by not running depmod
at boot time.
Currently it is run by these packages' postinst:
* kernel/linux-image-*
* module-init-tools
* powermgt-base
* zaptel
* lirc
* toshutils
*
On May 19, Margarita Manterola [EMAIL PROTECTED] wrote:
Continuing on the goal of optimizing boot time, quite a number of
seconds (specially in old machines) can be saved by not running depmod
at boot time.
If we can agree that it's not needed anymore (i.e. mandate by policy
that packages need
On Thu, May 18, 2006 at 07:21:33PM -0300, Margarita Manterola [EMAIL
PROTECTED] wrote:
Continuing on the goal of optimizing boot time, quite a number of
seconds (specially in old machines) can be saved by not running depmod
at boot time.
(...)
It looks like it's quite safe to stop running
Marco d'Itri wrote:
If we can agree that it's not needed anymore (i.e. mandate by policy
that packages need to run depmod on their own) then I will be happy to
remove it from the m-i-t init script.
A while back Debian would only run depmod on boot if it had not been run
before since the last
On Thu, May 18, 2006 at 07:21:33PM -0300, Margarita Manterola wrote:
Continuing on the goal of optimizing boot time, quite a number of
seconds (specially in old machines) can be saved by not running depmod
at boot time.
Currently it is run by these packages' postinst:
* [long list]
It
Margarita Manterola wrote:
Currently it is run by these packages' postinst:
* kernel/linux-image-*
This takes care to run depmod -F system.map version,
which should make the depmod work even though that kernel isn't running yet.
* pwc-modules-*
* ndiswrapper-modules-*
*
Jeroen van Wolffelaar wrote:
I think one of the issues here is that it depends on what kernel you
currently use, and iirc there can be a situation where one does not
want to run depmod at installation time, or when that might give wrong
results.
FWIW, d-i currently runs depmod at image build
On May 19, Joey Hess [EMAIL PROTECTED] wrote:
A while back Debian would only run depmod on boot if it had not been run
before since the last kernel upgrade. Could you refresh my memory about
why that optimisation was dropped?
I think because depmod --quick is supposed to be about as fast as
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
I think one of the issues here is that it depends on what kernel you
currently use, and iirc there can be a situation where one does not
want to run depmod at installation time, or when that might give wrong
results.
That used to be the case
13 matches
Mail list logo
