[Buildroot] [Patch] OpenVZ tools

[Buildroot] [Patch] OpenVZ tools

[Cristi Magherusan]

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 <cristi.magherusan@net.utcluj.ro>

-- 
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>

[Buildroot] [Patch] OpenVZ tools

[Thomas Lundquist]

On Mon, Jun 15, 2009 at 11:29:35PM +0300, Cristi Magherusan wrote:
> 
> 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.

[Buildroot] [Patch] OpenVZ tools

[Cristi Magherusan]

On Fri, 2009-06-19 at 12:12 +0200, Thomas Lundquist wrote:
> On Mon, Jun 15, 2009 at 11:29:35PM +0300, Cristi Magherusan wrote:
> > 
> > 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.
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
-- 
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>