Updating to lenny from etch

Posted by / 23-Aug-2020 22:07

Open VZ per-container disk quota is supported only for ext2/ext3 filesystems; therefore it makes sense to use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

If you are using Debian Lenny, this step in no longer required.

You may also wish to check the information on the Debian wiki.IPTABLES="ip_tables ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_LOG ipt_conntrack ipt_helper ipt_state iptable_nat ip_nat_ftp ip_nat_irc ipt_TOS" After installing the Open VZ kernel, user tools and a minimal OS template to create a first container and do some basic operations in Open VZ environment.Read the download:doc/Open VZ-Users-Guide.pdf, browse this wiki.I still have the etch install untouched onthe previous drive, which has allowed me to do some testing. A user brought this to myattention, and at this point we have only tested one script (multipletimes, different days)- 47 min 35 sec So, the kernel compile is a a little slower on lenny.During the upgrade there was an error of some sort about updating thefollowing packages:r-base-corer-cran-kernsmoothr-cran-mgevr-cran-cluster I deleted those packages and continued with the upgrade.

updating to lenny from etch-54updating to lenny from etch-82updating to lenny from etch-86

Iptables modules required by the container must be specified in the general file or the vz file of the container.