Hi Dan, I don't see where this is selected, but it looks for me like sis was using the busybox.standard.config file before, while now it uses the busybox.no_modules.config. It would be logical, as we use the far more up-to-date module-init-tools instead of busybox for the module utilities now. This was necessary for enabling SIS to build on RHEL3 and other distros with 2.4 kernels (those were producing wrong module dependencies in the boel_binaries). So only the busybox config files have to be fixed.
Regards, Erich On Sunday 17 July 2005 20:06, Daniel Widyono wrote: > I'm confused, but perhaps I have an erroneous assumption. My assumption is > that it worked at 3167 (which it does for me), and it doesn't at 3189 (I have > yet to try, too busy right now). > > There are no differences between 3167 and 3189 with the > initrd_source/patches/busybox* patch files, nor with the selection of patches > in busybox.rul. > > Bernard, can you confirm when it last 'worked' for you (e.g. you did not > receive the error messages regarding logger and nc)? > > Regards, > Dan W. > > > The issue comes from the differences between the busybox configuration > > files: > > initrd_source/patches/busybox.no_modutils.config and > > busybox.standard.config. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
