[Vserver] strange vserver utils messages
hi, at some commands within the vserver context i get Unknown HZ value! (47255) Assume 100. ps, top are examples. I`m running vserver utils 0.26 and vserver 1.16 on 2.4.22 Greetings Oliver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: Re: [Vserver] is there any getting started with vserver documentation anywhere?
On Saturday, November 29, 2003 11:02 PM NZT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello Simon, Is there a list of things to remove prior to building the skel, and after? If so where can I get it, I continue to have problem with thing trying to start, like the can't initalize iptable - can't find etc/fstab, after I edited it in the skel...? /etc/rc.d stuff all needs to be modified quite a bit to work with vservers. I could look at adding some of the needed changes to the build-skel functionality in Vskel, only trouble is it tends to be a little distribution specific. I suggest you look in /etc/rc.d/init.d (in the skel) and delete all init scripts for things you don't need - including iptables. Then look in /etc/rc.d/rc3.d and remove the links to those same scripts (or you can use chkconfig to do this the 'tidy' way). Let me know if you still have trouble... -Simon ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Kernel Patching Questions
1. include/linux/sys.h: vanilla 2.4.21 had #define NR_syscalls 270 but RHEL 2.4.21 has #define NR_syscalls 271 So should I make NR_syscalls now 274 or 275? 2. include/linux/sched.h: any ideas what to do with this hunk (following)? There's nothing even vaguely like it that I can see. *** *** 956,961 out_of_line_bug(); write_lock_irq(tasklist_lock); nr_threads--; unhash_pid(p); REMOVE_LINKS(p); list_del(p-thread_group); --- 968,975 out_of_line_bug(); write_lock_irq(tasklist_lock); nr_threads--; + if (p-s_info) + p-s_info-nr_threads--; unhash_pid(p); REMOVE_LINKS(p); list_del(p-thread_group); 3. forget_original_parent in exit.c seems to have changed completely - looks like the vanilla 2.4.21 used a read_lock while the RH one uses list_for_each_safe which I assume locks as it goes. But that means there's nowhere left to put the additional bit from the vserver patch (not sure what it does exactly, it tries to find a new parent for vchild_reaper I think). Boy I'm tired, that's way too much kernel hacking in one day for me. 10 rejects down, 20 to go... Any help appreciated. BTW, there are 266 patches applied inside the RHEL3 kernel SRPM... Grr. Have a good day =) Chuck ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Incremental patches?
On Sun, Nov 30, 2003 at 04:05:50AM -0500, al3x wrote: Hello everybody. Can I suggest incremental kernel patches? It's pretty easy to create but saves the hell lot of time for applying to modified kernels - personally I have to manually straighten some problems with grsecurity patch. This way transition from development patches to release will be more smooth. Unless there is some reason for not doing this. hmm, no problem with that, what incrementals do you have in mind? vs1.00 - vs1.1.6 or just vs1.1.0- vs1.1.1 ... or just between stable releases? it's not a big deal, just let me know, Herbert -- Alex Klymov mailto:[EMAIL PROTECTED] ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [RFC] iproute2 setup for 2 gateways ...
On Sun, Nov 30, 2003 at 03:10:36PM +1100, Alec Thomas wrote: Hi Herbert, Basically I see two options, to solve this without too much confusion and/or magic a) we 'define' that the first IP assigned to a vserver, is the one to be used for 'outgoing' connects, regardless of the routing setup (or at least as fallback, if using 0.0.0.0 fails) b) we add a 'source' address to the vserver config, which by default, is 0.0.0.0 and can be assigned some other ip (probably restricted to IPs from the config array) I vote for b), because I think that having smart defaults with configurability is the best way. i'm for b) too bye Ste ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
