On Thu, Dec 14, 2006 at 09:17:29AM -0800, Matt Anger (manger) wrote: > I'm pretty sure you have to disable legacy kernel api.
how do you get to such a conclusion? > I think its been broken for a while and removed completely > in the new 2.2/2.3 releases. while it will be removed for 2.3.x, and is already removed to some extend for 2.2.x, it is still part of 2.1.x and it compiles and works perfectly fine, if you have any .configs where this is not true, please let us know, as it is considered a bug ... > Matt > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, December 14, 2006 2:27 AM > To: vserver@list.linux-vserver.org > Subject: [Vserver] patch-vs-2.1.1.7.diff nok ? > > Hello > > I try patch-vs-2.1.1.7.diff : error during compil but i don't know if > it's > due to patch.... > > CC kernel/power/process.o > CC kernel/power/console.o > CC kernel/power/pm.o > kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared > at > kernel/power/pm.c:64) > kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared > at > kernel/power/pm.c:64) > kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared > at > kernel/power/pm.c:180) > kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared > at > kernel/power/pm.c:180) that is normal, most of the power management has been deprecated in recent kernels, and the maintainers do not care much to fix it up ... you'll get the same warnings on mainline > malloc: ../bash/make_cmd.c:89: assertion botched > malloc: block on free list clobbered so, that looks like some tool wasn't able to allocate (or free) memory properly, which somewhat points to a broken toolchain ... > Stopping myself...make[2]: *** [kernel/power/pm.o] Erreur 134 > make[1]: *** [kernel/power] Erreur 2 > make: *** [kernel] Erreur 2 > > > I just activate the following options in VSERVER : > > [*] Enable Legacy Kernel API > [*] Enable dynamic context IDs > [*] Enable Legacy Networking Kernel API > [*] Enable Proc Security that is, like all other configurations, a perfectly fine one ... HTC, Herbert > Patrick > > _______________________________________________ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver > _______________________________________________ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver