Re: [Cooker] mkinitrd-3.1.6-18mdk (what ever happened to it?)

[Guillaume Cottenceau]

Borsenkow Andrej <[EMAIL PROTECTED]> writes:

> Move find into /bin? It is basic (and useful) enough to be available
> early.

That's an easy way, right :-). It's 50 kbytes. We probably can
afford this.



-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/

RE: [Cooker] mkinitrd-3.1.6-18mdk (what ever happened to it?)

[Borsenkow Andrej]

> 
> Because the "find" is now made by shell globbing which is rather
> slow.
> 
> I'll have to find a better way to do the "find".
> 

Move find into /bin? It is basic (and useful) enough to be available
early.

-andrej

Re: [Cooker] mkinitrd-3.1.6-18mdk (what ever happened to it?)

[Guillaume Cottenceau]

Oden Eriksson <[EMAIL PROTECTED]> writes:

> Hi again.
> 
> A while back I was very pleased with the mkinitrd script because it was so 
> much faster than in Mandrake 7.2, now something has happened to it and 
> there's suddenly not much difference in execution time. The use of diet libc 
> speeded up this process a great deal.
> 
> Somewhere in the evolution of mkinitrd it only took a couple of seconds to 
> make a ramdisk, now it takes at least ten seconds (up to a minute if there's 
> a softlink to the source...). Why is that?

Because the "find" is now made by shell globbing which is rather
slow.

I'll have to find a better way to do the "find".

> I still have the same hardware.
> 
> Is it all in the sh_find function? It seems to scan through the directories 
> over and over and yet over again. It makes no sence to me...

-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/