-
Mike Hibler authored
vservers can be configured with experimental interfaces. Think duct tape and baling wire here... * commmon/bootvnodes: did some code refactoring in anticipation of something that was never needed. Oh well, it looks purdy anyway! * common/libsetup.pm: LINUXJAILED() predicate to indentify local Linux vserver setups. getlocalevserver() to return the IP/hostname of the "local" event server. * common/rc.{linktest,linkagent,progagent,trace,trafgen}: use the getlocalevserver() function for use with -s options (Linux vserver based vnodes cannot bind to localhost to talk to the pnode pubsubd) * common/config/rc.ifconfig: run this for Linux vservers, put out iface map for veths as well as physical interfaces * common/delaysetup: add -j vnodeid option, will need this at some point * linux/liblocsetup.pm: veth (actually etun) setup for Linux vserver vnodes * linux/mkvserver.pl: first cut at getting interfaces configured in vservers, do all the necessary etun/br plumbing (NOT a pretty sight...) * linux/vserver/rc.invserver (moved here from linux/rc.invserver): run linktest in local vservers (though it won't run yet due to NFS problems in vservers) * linux/vserver/vserver-cnet.sh: statically configure the control net in a vserver, no DHCP here! * linux/vserver/vserver-{init,rc}.sh: two parts of the Funky Interface Setup Dance that run inside the vserver
25a29bbb