That's what we then will have to do...
Jan Beulich wrote:
Yes, if only one of these can be loaded, then this should perhaps be configurable respectively, that is with modules off only one of the two should be selectable. And yes, given that these two can't be loaded together according to what you say, this would be perfectly acceptable. Thanks, Jan
Hubertus Franke <[EMAIL PROTECTED]> 01.10.04 17:31:21 >>>
Yes, that now makes sense. Is that a hard requirement for you to have ?
We always went from the perspective that these would always be loaded
as modules.
Furthermore, you can only have one classification engine (RBCE or CRBCE) attached to the CKRM core at any given time. So I question whether it even makes sense to have these build into the core kernel.
So, if you really want the RBCE linked into the kernel with MODULES off we could add a switch to disable one or the other.
Would that be acceptable from your point of view !
-- Hubertus
Jan Beulich wrote:
All I try to do is build a kernel with CONFIG_MODULES=n. This, with
all
the various CKRM pieces enabled, results in numerous duplicate
symbol
errors when linking vmlinux. Jan
Hubertus Franke <[EMAIL PROTECTED]> 01.10.04 14:56:18 >>>
Through the config options, you can select the RBCE. If relayfs is present you will in addition be allowed to create
CRBCE.
This is definitely working for quite some time.
Can you better describe what the problem is and what you are trying
to
do.
Jan Beulich wrote:
According to Andi the below is a known problem. Has it been fixed already? Thanks, Jan
Andi Kleen <[EMAIL PROTECTED]> 01.10.04 10:45:27 >>>
On Fri, Oct 01, 2004 at 09:42:49AM +0200, Jan Beulich wrote:
Trying to verify build correctness of an entirely unrelated change
I
had
to realize that kernel/ckrm/rbce/ does not build in this mode,
because
of the duplicate compilation of rbcemod.c (once by itself, once
through
inclusion from crbcemod.c, but then with different flags so that
one
can't simply exclude one of the two source files in this build
mode).
Since I have no idea where this is being maintained (inside or
outside
of our company) I thought I first post this here.
Known problem (I hit it during betas). But fixing it properly
will require some reorganization and we don't support self compiled
kernels anyways, so ...
Best is if you talk to the IBM CKRM people directly. They might fix it upstream then and we can pick it up with SLES10.
-Andi
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
Use IT products in your business? Tell us what you think of them.
Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
