Re: [lxc-users] container/config: why "lxc." in front of config option names?

2014-02-01 Thread Michael H. Warfield
On Sat, 2014-02-01 at 12:59 +0100, Harald Dunkel wrote: > Hi folks, > The "lxc." in the config option names seems to be constant, so I wonder > what it is good for? It allows us to extend the configuration file for other scripts and such. For a long while I've used it for autoboot options, befo

Re: [lxc-users] Router inside LXC with "lxc.network.type = phys" to the WAN-port

2014-02-01 Thread Thomas Huber
Am 31.01.2014 um 20:28 schrieb Leonid Isaev : > On Fri, 31 Jan 2014 12:26:30 +0100 > Thomas Huber wrote: > >> [...] >> >> I see your point and thats why I´m asking. >> The Idea was not only to protect the host but also the other running >> service / VMs: > > Right. > >> - KVM with Window20

Re: [lxc-users] container/config: why "lxc." in front of config option names?

2014-02-01 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/01/14 13:33, Stéphane Graber wrote: > > This was done so hooks and other tools related to LXC may share the config > file. > > LXC will consider any option that doesn't start with "lxc." as valid whereas > any unknown "lxc.*" option will be

Re: [lxc-users] container/config: why "lxc." in front of config option names?

2014-02-01 Thread Stéphane Graber
On Sat, Feb 01, 2014 at 12:59:50PM +0100, Harald Dunkel wrote: > Hi folks, > > The "lxc." in the config option names seems to be constant, so I wonder > what it is good for? > > Its hard to search for "lxc.". Please excuse if this has been asked > before. This was done so hooks and other tools r

[lxc-users] container/config: why "lxc." in front of config option names?

2014-02-01 Thread Harald Dunkel
Hi folks, The "lxc." in the config option names seems to be constant, so I wonder what it is good for? Its hard to search for "lxc.". Please excuse if this has been asked before. Regards Harri ___ lxc-users mailing list lxc-users@lists.linuxcontainers