On Fridayen den 9 November 2001 16.05, Guillaume Cottenceau wrote: > Oden Eriksson <[EMAIL PROTECTED]> writes: > > > Fast? When executing at bootup, you mean? I didn't notice that. Maybe > > > because of dietlibc?... > > > > At boot? Does it run at boot I dare to ask... > > Well it's "executed" at boot when it loads modules, mounts the rootfs, > etc.
Executed?, it's not that it's extracted into ram by another software, but really _executed_ by its own? This is a part I would really like to learn more about, but I don't know where to look... > > No, I mean when creating the old plain initrd, like "mkinird -v -f > > /boot/initrd.img kernel_ver". I keep all sorts of init ramdisk just in > > case, my lilo.conf is filled with stuff:) > > Ok I see. I don't know why it's faster. Probably because it creates a FS > which is 3 times smaller. I don't know either, but it's very nice compared to how it were before. Thanks. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Oden Eriksson, Deserve-IT Networks, Jokkmokk, Sweden. | Mandrake Linux release 8.2 (Cooker) for i586 | Current uptime with kernel 2.4.13-4mdksmp: 2:55 | cpu0 @ 814.28 bm, fan 4166 rpm, temp +30.0�C | cpu1 @ 815.92 bm, fan 4066 rpm, temp +29�C
