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

2002-01-17 Thread 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/




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

2002-01-17 Thread 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?)

2002-01-17 Thread 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/




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

2002-01-16 Thread Oden Eriksson

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?

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...

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Oden Eriksson, Deserve-IT Networks/HFE Systems, Jokkmokk, Sweden.
| Mandrake Linux release 8.2 (Cooker) for i586
| Current uptime with kernel 2.4.17-5mdksmp: 1 day 55 minutes
| cpu0 @ 799.53 bm, fan 4560 rpm, temp +30°C
| cpu1 @ 801.17 bm, fan 4530 rpm, temp +30.5°C