From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Subject: Re: lxc userspace tools 0.3.0 released
Date: Thu, 16 Oct 2008 16:10:38 +0200 [thread overview]
Message-ID: <48F74B5E.9060909@fr.ibm.com> (raw)
In-Reply-To: <20081016133006.GQ27881-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Daniel P. Berrange wrote:
> On Thu, Oct 16, 2008 at 02:55:23PM +0200, Cedric Le Goater wrote:
>>> Just to clarify to avoid confusion. There is a LXC project inside the
>>> libvirt and there is the lxc userspace tools (liblxc). We are talking
>>> about the liblxc.
>> I wouldn't say there is a "LXC project inside the libvirt" but rather
>> there is a libvirt driver emulating a virtual machine using namespaces.
>> This driver is called lxc for some reason I don't know and this is very
>> unfortunate IMO.
>
> It is called LXC because it implements "LinuX Containers". When we first
> released this LXC driver in libvirt this lxc userspace tools package didn't
> exist so there was no naming clash.
Libvirt being a VM/container middleware, shouldn't we change lxc-driver
to use liblxc ?
prev parent reply other threads:[~2008-10-16 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:39 lxc userspace tools 0.3.0 released Daniel Lezcano
[not found] ` <48F4AF2E.3000204-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-14 17:00 ` Cedric Le Goater
2008-10-16 8:10 ` [Devel] " Dmitry Mishin
[not found] ` <200810161210.48149.dim-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-10-16 9:06 ` Daniel Lezcano
[not found] ` <48F70425.5090606-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-16 10:57 ` Dmitry Mishin
[not found] ` <200810161457.45686.dim-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-10-16 12:28 ` Daniel Lezcano
[not found] ` <48F73358.80208-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-17 8:08 ` Dmitry Mishin
[not found] ` <200810171208.51783.dim-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-10-17 20:42 ` Daniel Lezcano
[not found] ` <48F8F8BE.7080509-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-20 8:42 ` Dmitry Mishin
[not found] ` <200810201242.47995.dim-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-10-20 9:52 ` Daniel Lezcano
2008-10-16 8:22 ` Alexey Eremenko
[not found] ` <7fac565a0810160122n7afa6e71l929be8cb08ba05c6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-16 9:50 ` Daniel Lezcano
[not found] ` <48F70E53.9070002-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-16 9:56 ` Alexey Eremenko
[not found] ` <7fac565a0810160256mc3de8b5raf4bab31470b051a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-16 10:35 ` Daniel Lezcano
2008-10-16 12:55 ` Cedric Le Goater
[not found] ` <48F739BB.4070201-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-16 13:30 ` Daniel P. Berrange
[not found] ` <20081016133006.GQ27881-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-10-16 14:10 ` Daniel Lezcano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F74B5E.9060909@fr.ibm.com \
--to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox