Re: [Users] More on making an OpenVZ template
* Sam Trenholme strenholme.use...@gmail.com wrote: Debian's policies wouldn't be a big deal, except that some Debian users have this really annoying habit of bugging upstream about a bug which has already been fixed upstream, just not applied to the appropriate Debian software repository. There is a Debian bug tracking system to file bug reports or feature requests, and Debian users are probably best using this system; if the package maintainer says it's an upstream issue, then it is time to contact upstream about the issue. Is there an separate repository containing new packages ? If not, we should just create one. cu -- -- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 -- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme -- ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] More on making an OpenVZ template
On 08/20/2011 12:18 AM, Sam Trenholme wrote: I am continuing the work of making a tiny OpenVZ template. One discovery I have is that, for the OpenVZ tools to work, not only is it mandatory for the system to have the Bash shell, but also that /bin/sh has to be a symlink to Bash. This is because the vzctl program prepends the contents of the Bash-only /etc/vz/dists/scripts/functions script to any script used by the container to configure the system, and there does not appear to be any way to configure a container to not use this Bash-only script. In other words, any OpenVZ template without /bin/sh being an alias for Bash can not be configured via the vzctl tools (nor the corresponding Proxmox/SolusVM/whataever tools that call vzctl). This in mind, the next release of TinyVZ will include the Bash shell. I actually prefer Bash over Busybox's ash shell; I *really* miss the !$ and !* shortcuts, as well as the history command, when using this minimal shell. This is one way of doing things. The other way would be to rectify the '/etc/dists/scripts/functions' to not be dependent on bash. I am currently looking at it, so far I only found that it uses the 'function' keyword which is bashism. With that removed, it looks like it is working fine in either dash or busybox sh. I have committed the patch: http://git.openvz.org/?p=vzctl;a=commit;h=f83b28435f582f2f74fb3267b89b061a551b32e2 And then a few more (to check it works in Debian without /bin/bash): http://git.openvz.org/?p=vzctl;a=commit;h=a86beacde8c1fba4002eaf5bf48a535e7d46ffc0 http://git.openvz.org/?p=vzctl;a=commit;h=382f306cd0865bb4bcafc4f7a4b5cfe2f809296c Since this is an open source project I am not getting paid for, I have no timeline of when I will make another TinyVZ release, nor do I guarantee I will even make such a release. Working on TinyVZ has taught me a lot about OpenVZ and hopefully is something that is useful. - Sam ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] More on making an OpenVZ template
On Sun, Aug 21, 2011 at 4:10 PM, Kir Kolyshkin k...@openvz.org wrote: On 08/20/2011 12:18 AM, Sam Trenholme wrote: I am continuing the work of making a tiny OpenVZ template. One discovery I have is that, for the OpenVZ tools to work, not only is it mandatory for the system to have the Bash shell, but also that /bin/sh has to be a symlink to Bash. This is because the vzctl program prepends the contents of the Bash-only /etc/vz/dists/scripts/functions script to any script used by the container to configure the system, and there does not appear to be any way to configure a container to not use this Bash-only script. In other words, any OpenVZ template without /bin/sh being an alias for Bash can not be configured via the vzctl tools (nor the corresponding Proxmox/SolusVM/whataever tools that call vzctl). This in mind, the next release of TinyVZ will include the Bash shell. I actually prefer Bash over Busybox's ash shell; I *really* miss the !$ and !* shortcuts, as well as the history command, when using this minimal shell. This is one way of doing things. The other way would be to rectify the '/etc/dists/scripts/functions' to not be dependent on bash. I am currently looking at it, so far I only found that it uses the 'function' keyword which is bashism. With that removed, it looks like it is working fine in either dash or busybox sh. I have committed the patch: http://git.openvz.org/?p=vzctl;a=commit;h=f83b28435f582f2f74fb3267b89b061a551b32e2 And then a few more (to check it works in Debian without /bin/bash): http://git.openvz.org/?p=vzctl;a=commit;h=a86beacde8c1fba4002eaf5bf48a535e7d46ffc0 http://git.openvz.org/?p=vzctl;a=commit;h=382f306cd0865bb4bcafc4f7a4b5cfe2f809296c I have compiled it, and I can report it works, I have remove the bash binary I got from tinyvz, and now it enters well in openwrt rootfs (I have tested with the original vzctl 3.0.24 where it fails to enter if there is no /bin/bash): == root@mybox /root/zoobab/openwrt-openvz [46]# ./vzctl --version vzctl version 3.0.28.3-70.git.382f306 root@mybox /root/zoobab/openwrt-openvz [40]# ./vzctl enter 889 entered into CT 889 BusyBox v1.15.3 (2011-07-14 17:03:04 CEST) built-in shell (ash) Enter 'help' for a list of built-in commands. ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M Backfire (10.03.1-RC5, r27608) -- * 1/3 shot KahluaIn a shot glass, layer Kahlua * 1/3 shot Bailey's on the bottom, then Bailey's, * 1/3 shot Vodka then Vodka. --- root@OpenWrt:/# == -- Benjamin Henrion bhenrion at ffii.org FFII Brussels - +32-484-566109 - +32-2-4148403 In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] More on making an OpenVZ template
I am using the one of debian squeeze: As a side note, one of my long-standing annoyance with Debian's software policies is that, once a given release is frozen, Debian will not update a software package unless there is a CVE-worth security bug in it. Other bugs will not get fixed. Not even if the fix is minor. They certainly will not keep current with a release in any bugfix-only branch of the software provided upstream. I can understand this software policy; open-source development is, by nature, undisciplined and a lot of developers are not very good at only fixing bugs without adding other potential bug-inducing features. Debian's policies wouldn't be a big deal, except that some Debian users have this really annoying habit of bugging upstream about a bug which has already been fixed upstream, just not applied to the appropriate Debian software repository. There is a Debian bug tracking system to file bug reports or feature requests, and Debian users are probably best using this system; if the package maintainer says it's an upstream issue, then it is time to contact upstream about the issue. - Sam ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] More on making an OpenVZ template
On Fri, Aug 19, 2011 at 10:18 PM, Sam Trenholme strenholme.use...@gmail.com wrote: I am continuing the work of making a tiny OpenVZ template. One discovery I have is that, for the OpenVZ tools to work, not only is it mandatory for the system to have the Bash shell, but also that /bin/sh has to be a symlink to Bash. This is because the vzctl program prepends the contents of the Bash-only /etc/vz/dists/scripts/functions script to any script used by the container to configure the system, and there does not appear to be any way to configure a container to not use this Bash-only script. In other words, any OpenVZ template without /bin/sh being an alias for Bash can not be configured via the vzctl tools (nor the corresponding Proxmox/SolusVM/whataever tools that call vzctl). This in mind, the next release of TinyVZ will include the Bash shell. I actually prefer Bash over Busybox's ash shell; I *really* miss the !$ and !* shortcuts, as well as the history command, when using this minimal shell. Since this is an open source project I am not getting paid for, I have no timeline of when I will make another TinyVZ release, nor do I guarantee I will even make such a release. Working on TinyVZ has taught me a lot about OpenVZ and hopefully is something that is useful. This is a very useful for me, I was about to spend time on an openwrt container, which does not use bash at all. Where in the source code of vzctl do you see this requirement? -- Benjamin Henrion bhenrion at ffii.org FFII Brussels - +32-484-566109 - +32-2-4148403 In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
