|
From: Heiko Z. <he...@zu...> - 2004-06-27 17:11:23
|
Roland Pabel wrote: > On Sunday 27 June 2004 17:02, Heiko Zuerker wrote: > >>Roland Pabel wrote: >> >>>On Saturday 26 June 2004 21:59, Heiko Zuerker wrote: >>> >>>>Roland Pabel wrote: >>>> >>>>>On Saturday 26 June 2004 15:47, Heiko Zuerker wrote: >>>>> >>>>>>Roland Pabel wrote: >>>>>> >>>>>>>On Saturday 26 June 2004 12:31, Roland Pabel wrote: >>>>>>> >>>>>>>>On Saturday 26 June 2004 10:13, Roland Pabel wrote: >>>>>>>> >>>>>>>>>On Friday 25 June 2004 15:19, Bruce Smith wrote: >>> >>>[...] >>> >>> >>>>That's not good... >>>>Can you create a modules.dep with the module-init-tools depmod and check >>>>if it works ? >>>>If yes, then we have to add some checks about the running kernel. >>> >>>Looks like it's all right after all. I forgot that "depmod -an" dumps >>>all /lib/modules/<>/modules.* files in one file. Concatenated all those >>>files are exactly the same size as the dumped version. >>>The missing option for depmod to work is "-F $CDDIR/boot/System.map". I >>>copied that map file to /boot/ which doesn't make depmod happy ... >>>maybe we should replace the lfssystem's depmod by a script which calls >>>the freshly compiled depmod with the correct options ? or disable it by >>>copying /bin/true over it... >> >>We need a working depmod in the system, so let's move it to be compiled >>earlier in the build process and install it into the lfssystem. > > you need more than that, you need to transparently have depmod called like > this: > depmod <whatever> => depmod $@ -F $CDDIR/boot/System.map $KERNELVERSION > and handle -F arguments and kernel version if given > > >>Are you going to create a patch? > > can do, but won't be before tuesday That's OK, I'm doing other stuff anyway and we're waiting for 2.4.27 for the next DL beta. Heiko |