Andrew Morton wrote: >Boszormenyi Zoltan wrote: > > >>Hi, >> >>I am testing it now with your two extra patches. >>I started vmware but I don't notice it now. Everything is snappy. >>The system is a RH9 with upgrades. The latest errata kernel still >>stops for seconds sometimes and vmware (and rsync between two drives >>for that matter) makes a noticable performance impact. With .70-mm2, >>I can still work on other things and not wait for other things to >>finish first. >> >> > >OK, thanks. > > > >>However there are problems: Basically, the autoload fails. >>My eth0/eth1 (both use 8139too) are down. >>The iptables modules do not load so the iptables service is failing. >>When I modprobe the needed modules, the things start working. >> >> > >Make sure that you've correctly enabled the "Kernel Module Loader" in the >"Loadable Mudule Support" menu. > From my .config, you can see it was enabled. >And read the readme file in mudule-init-tools carefully. You need to build >the /etc/modprobe.conf file with all the aliases in it. It takes a bit of >fiddling, but demand-modloading does work. > OK, I read it's FAQ, and the answer for the first question helped. Attached is a small patch against RH9 /etc/rc.d/rc.sysinit. This solved most of my problems. >>E.g. named can be started after I modprobe capabilities. I brought up >>named for example because the kernel logs messages for this one: >> >>process `rndc' is using obsolete setsockopt SO_BSDCOMPAT >>process `named' is using obsolete setsockopt SO_BSDCOMPAT >> >> > >That's OK. It's just the kernel spamming the application developers ;) > OK. :-) However, "modprobe capability" is still not automatic. What is the alias line for capability? I can't figure it out myself. Perhaps it's not supported configuring capability (aka CONFIG_SECURITY_CAPABILITIES) as a module? It's definitely allowed... >This is a bug in rpm. It can be worked around with: > > alias rpm='LD_ASSUME_KERNEL=2.2.5 rpm' > > Thanks for the answers. Best regards, Zoltán