On Fri, Dec 04, 2015 at 10:06:11AM +0100, Aurelien Jarno wrote:
> The minimum required version in the glibc is something configurable at
> build time (to some extents, the absolute minimum is 2.6.32 for glibc
> 2.21). This configure how much compatibility glue is used to workaround
> the missing sy
> "AJ" == Aurelien Jarno writes:
AJ> If you consider Debian "stable" as too archaic, I am missing words to
AJ> qualify a 2.6.32 kernel released in 2009. Prehistoric maybe?
Indeed, but we don't have any choice there.
And it isn't Linus' 2.6.32, its openvz's port of rh's port of 2.6.32.
So it
On 7 December 2015 at 14:50, Marco d'Itri wrote:
> On Dec 07, Aurelien Jarno wrote:
>
>> Have there also backported recent glibc or systemd to these systems and
>> do they support such a configuration? This is what we are talking about
>> here.
> The *hosts* still use Centos 6, but so far more re
On Dec 07, Aurelien Jarno wrote:
> Have there also backported recent glibc or systemd to these systems and
> do they support such a configuration? This is what we are talking about
> here.
The *hosts* still use Centos 6, but so far more recent guests releases,
even using systemd, are working fin
On 2015-12-05 08:33, Marco d'Itri wrote:
> On Dec 03, James Cloos wrote:
>
> > Most openvz run on kernels based on 2.6.32, often with significant
> > updates. These platforms are an important segment, given how affordable
> > they are. And Debian "stable" is often too archaic for many needs whi
On Dec 03, James Cloos wrote:
> Most openvz run on kernels based on 2.6.32, often with significant
> updates. These platforms are an important segment, given how affordable
> they are. And Debian "stable" is often too archaic for many needs which
> fit nicely on a small inexpensive server.
>
>
On Fri, 2015-12-04 at 14:04 -0800, Steve Langasek wrote:
> Hi Aurélien,
>
> On Fri, Dec 04, 2015 at 10:06:11AM +0100, Aurelien Jarno wrote:
> > On 2015-12-03 17:33, James Cloos wrote:
> > > The latest glibc update breaks most sid installs on (typically leased)
> > > openvz platforms because it req
Hi Aurélien,
On Fri, Dec 04, 2015 at 10:06:11AM +0100, Aurelien Jarno wrote:
> On 2015-12-03 17:33, James Cloos wrote:
> > The latest glibc update breaks most sid installs on (typically leased)
> > openvz platforms because it requires a newer kernel version that most
> > openvz vendors advertize.
Le 04/12/2015 07:06, Paul Wise a écrit :
> On Fri, Dec 4, 2015 at 6:33 AM, James Cloos wrote:
>
>> The latest glibc update breaks most sid installs on (typically leased)
>> openvz platforms because it requires a newer kernel version that most
>> openvz vendors advertize.
>
> Is it possible for th
On 2015-12-03 17:33, James Cloos wrote:
> The latest glibc update breaks most sid installs on (typically leased)
> openvz platforms because it requires a newer kernel version that most
> openvz vendors advertize.
>
> Most openvz run on kernels based on 2.6.32, often with significant
> updates. Th
> Is it possible for these vendors to switch to a newer version of Linux?
A new version of OpenVZ based on the RHEL 7 kernel (3.10) is being
developed but isn't expected soon unfortunately. This led the Proxmox
team to replace OpenVZ with LXC for its containers.
Emmanuel Bourg
On Fri, Dec 4, 2015 at 6:33 AM, James Cloos wrote:
> The latest glibc update breaks most sid installs on (typically leased)
> openvz platforms because it requires a newer kernel version that most
> openvz vendors advertize.
Is it possible for these vendors to switch to a newer version of Linux?
12 matches
Mail list logo
