Reinhard Katzmann <[EMAIL PROTECTED]> writes:
[...] > It works, but I don't think it's correct: > > mkdir -p $MNTIMAGE/sbin > mkdir -p $MNTIMAGE/etc > mkdir -p $MNTIMAGE/dev > mkdir -p $MNTIMAGE/loopfs > mkdir -p $MNTIMAGE/proc > mkdir -p $MNTIMAGE/sysroot > ln -s bin $MNTIMAGE/sbin > > The result is: (ls -l bin sbin) > bin: > insgesamt 36 > -rwxr-xr-x 1 root root 24220 Jan 7 09:55 insmod* > -rwxr-xr-x 1 root root 11128 Jan 7 09:55 nash* > > sbin: > insgesamt 0 > lrwxrwxrwx 1 root root 3 Jan 7 10:11 bin -> bin > lrwxrwxrwx 1 root root 9 Jan 7 09:55 modprobe -> /bin/nash > > Either the sbin mkdir should be removed or the link command. Right. > > > - mkinitrd does not check the the kernel config (/boot/config-2.4.17-xyz) > > > correctly, modules are added from the kernel source tree (!) > > > which are inside the kernel (for me this was ext3, ide-mod, ide-probe-mod, > > > ide-disk). If I don't add them to IGNOREMODS insmoding will (of course) > > > fail when booting the kernel. > > > > I don't follow you. Modules are taken from /lib/modules/$kernver > > so what's the problem? > > No they are not. For example I have ext3 in my kernel like this: > CONFIG_EXT3_FS=y Unfortunately there is no trustable way to detect if a filesystem is compiled in a kernel so we don't "support" kernels for which fs'es (other than ext2) are compiled in. > When I invoke mkinitrd and look at the result, in /lib you find the following > file (initrd image): > lib: > insgesamt 83 > drwxr-xr-x 2 root root 1024 Jan 7 10:16 ./ > drwxr-xr-x 10 root root 1024 Jan 7 10:16 ../ > -rw-r--r-- 1 root root 81514 Jan 5 19:18 ext3.o > > locate ext3.o > /usr/src/linux-2.4.17-1mdk/fs/ext3/.ext3.o.flags > /usr/src/linux-2.4.17-1mdk/fs/ext3/ext3.o > > ll /usr/src/linux-2.4.17-1mdk/fs/ext3/ext3.o > -rw-r--r-- 1 root root 81514 Jan 5 19:18 >/usr/src/linux-2.4.17-1mdk/fs/ext3/ext3.o Lines 108 and 116 of mkinitrd should prevent this from happen. Can you trace the problem more precisely ? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
