Skip to contentSkip to conversation

OpenVZ tools

PATCH New Cristi Magherusan 2 participants 3 messages Jun 15, 2009 – Jul 2, 2009

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 OpenVZ tools

Hello,

The attached patch creates a Virtualization item in the configuration menu, adds support for the OpenVZ tools vzctl and vzquota, adds the /dev/vzctl device in the device list file(commented out by default), and fixes the kernel patching procedure that caused compilation failures when applying the OpenVZ patches.

For anyone who wants to test this:
In order to get it work for real, you need to compile a kernel patched with OpenVZ support. I can provide a .config file with patches built-in if asked.

By the way, wouldn't it be nicer to have a devlists.sh file which would contain "if" clauses in order to create devices according to the configuration, and the file could be executed to create the real devlist file. This way we could ensure the device needed by a tool is there, and missing when the tool is not compiled.

For example, devlist.sh could contain:
if $(BR2_PACKAGE_VZCTL) then
echo "/dev/vzctl c 600 0 0 126 0 0 0 -"
fi

And we could run "sh devlist.sh > devlist.txt" in order to create the real devlist file.

Regards,
Cristi

Signed-off by: Cristi Magherusan <[email protected]>

Signature · 17 lines
Ing. Cristi M?gheru?an, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro  +40264 401247
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot-openvz.patch
Type: text/x-patch
Size: 5118 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090615/5d4d408e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090615/5d4d408e/attachment.pgp>
#1 lore raw

PATCH 1/1 OpenVZ tools

Quoted 6 lines · Cristi Magherusan

By the way, wouldn't it be nicer to have a devlists.sh file which would contain "if" clauses in order to create devices according to the configuration, and the file could be executed to create the real devlist file. This way we could ensure the device needed by a tool is there, and missing when the tool is not compiled.

I'd rather have the devices needed contained either in the package makefile or a configuration file in the package directory.

if(defs) like you suggest would soon become a mess.

Thomas.

#2 lore raw

PATCH 1/1 OpenVZ tools

Quoted 8 lines · Thomas Lundquist
Quoted 6 lines · Cristi Magherusan

By the way, wouldn't it be nicer to have a devlists.sh file which would contain "if" clauses in order to create devices according to the configuration, and the file could be executed to create the real devlist file. This way we could ensure the device needed by a tool is there, and missing when the tool is not compiled.

Quoted 4 lines

I'd rather have the devices needed contained either in the package makefile or a configuration file in the package directory.

if(defs) like you suggest would soon become a mess.

I admit this.

Then we could enhance the build system so that the package directories contain devlist.txt files that may be used along with the main device list file.

Is this acceptable?

Regards,
Cristi

Signature · 10 lines
Ing. Cristi M?gheru?an, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro  +40264 401247
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090702/6d7482a3/attachment.pgp>