[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: not running depmod at boot time

"Gustavo Franco" <gustavorfranco@gmail.com> writes:

> On 5/25/06, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:
>> Josselin Mouette <joss@debian.org> writes:
>> > Le mardi 23 mai 2006 à 20:52 +0200, Marco d'Itri a écrit :
>> >> So, does anybody mind if I remove depmod from the module-init-tools init
>> >> script?
>> >
>> > Please go ahead. Anything relying on it is buggy anyway.
>> > --
>> >  .''`.           Josselin Mouette        /\./\
>> > : :' :           josselin.mouette@ens-lyon.org
>> > `. `'                        joss@debian.org
>> >   `-  Debian GNU/Linux -- The power of freedom
>> How about having module-init-tools run depmod when needed and have all
>> other packages rely on that? That way it would run at most once.
> If i understood correctly, you're asking for keep a X seconds delay at
> each boot just to work around buggy non-supported stuff, aren't you? I
> suggest add the comment in NEWS.Debian and probably point it in the
> Etch release notes too.
> regards,
> -- stratus

No, Im asking to have _one_ delay at a defined point instead of X
packages having a delay because they might have to run depmod manualy.

And the delay will be small on any modern system. True it will take a
few seconds to run but then the module inodes are in cache and the
discover run that loads all the modules will be that much quicker. How
much time is actualy lost for a complete boot?


Reply to: