[lxc-devel] [critical] "Default" configuration may destroy host system

Andrian Nord nightnord at gmail.com
Wed Nov 25 13:38:49 UTC 2009


On Wed, Nov 25, 2009 at 08:20:01AM +0100, Dietmar Maurer wrote:
> I also think that is a good idea. The lxc library should not deal with config parsing at all - that's just a waste of time. Instead just provide a very simply parser like we already have. If someone want to do more complex things (includes, variable) he can write his own parser then.

I'm agreed, that 'library' and 'ui' should be separated, and 'library'
shouldn't mess with config files or anything like that absolutely,
primitive or not.

Just a few thoughts:
1) current lxc project is liblxc 'library' _and_ lxc-utilities
2) At current state ("heavy development") there is no much sense in
strict separation into two different projects, imho.

So, this talk, and this patches are about ui and utilities, I don't see
any point why this utilities have to be as primitive as possible. As for
me, they should provide efficient command line configuration interface.
Efficient means that there should be no need in wrappers or console
scripts in most of common setups. Webui, network-controlled daemons and
others probably could be a different project (but could be mainlined
also, see git as example).




More information about the lxc-devel mailing list