From: Boszormenyi Zoltan <zboszor@freemail.hu>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70-mm2
Date: Fri, 30 May 2003 11:48:15 +0200 [thread overview]
Message-ID: <3ED728DF.8030203@freemail.hu> (raw)
In-Reply-To: <20030530012710.57cca756.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
Andrew Morton wrote:
>Boszormenyi Zoltan <zboszor@freemail.hu> 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
[-- Attachment #2: rc.sysinit.patch --]
[-- Type: text/plain, Size: 348 bytes --]
--- rc.sysinit~ 2003-05-30 10:45:01.000000000 +0200
+++ rc.sysinit 2003-05-30 10:45:01.000000000 +0200
@@ -357,7 +357,7 @@
IN_INITLOG=
fi
-if ! LC_ALL=C grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/ksyms ]; then
+if ! LC_ALL=C grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/modules ]; then
USEMODULES=y
fi
next prev parent reply other threads:[~2003-05-30 9:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 7:43 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30 8:27 ` 2.5.70-mm2 Andrew Morton
2003-05-30 8:44 ` 2.5.70-mm2 Christoph Hellwig
2003-05-30 8:59 ` 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30 9:48 ` Boszormenyi Zoltan [this message]
2003-05-30 10:12 ` 2.5.70-mm2 Boszormenyi Zoltan
2003-05-30 10:33 ` 2.5.70-mm2 Boszormenyi Zoltan
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 19:08 2.5.70-mm2 Downing, Thomas
2003-05-29 16:48 2.5.70-mm2 Downing, Thomas
2003-05-29 17:36 ` 2.5.70-mm2 Andrew Morton
2003-05-29 18:45 ` 2.5.70-mm2 Felipe Alfaro Solana
2003-05-29 21:22 ` 2.5.70-mm2 John Stoffel
2003-05-29 21:35 ` 2.5.70-mm2 Andrew Morton
2003-05-29 20:08 ` 2.5.70-mm2 Paul Larson
2003-05-29 8:29 2.5.70-mm2 Andrew Morton
2003-05-29 8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:05 ` 2.5.70-mm2 John Stoffel
2003-05-30 20:30 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:56 ` 2.5.70-mm2 John Stoffel
2003-05-30 22:36 ` 2.5.70-mm2 Mingming Cao
2003-05-29 21:52 ` 2.5.70-mm2 Badari Pulavarty
2003-05-30 11:17 ` 2.5.70-mm2 Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ED728DF.8030203@freemail.hu \
--to=zboszor@freemail.hu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox