[lxc-devel] Get rid of lxc-create and lxc-destroy?

[Dwight Schauer]

I don't want to be concerned with what gets put into the /var/lib/lxc
subdirectory.

Whenever I need to reconfigure a container I stop and destroy it
(which is very fast), edit the original config file, and recreate and
restart the container.

If what Michael Holzt is suggesting turns lxc-start into what is
currently lxc-create/lxc-start, and lxc-stop into what is currently
lxc-stop/lxc-destroy, then I'd ask for this as well.

Otherwise I'd prefer that it stays the way it is, with separate
lxc-create/lxc-start and lxc-stop/lxc-destroy.

Dwight

On Thu, Jan 7, 2010 at 8:04 AM, Michael Holzt <lxc at my.fqdn.org> wrote:
> Can we get rid of lxc-create and lxc-destroy? Currently the only thing
> lxc-create does is create /var/lib/lxc/<containername> and copy the config
> file into it. This seems like a unnecessary step.
>
> I propose to remove both binaries. Instead lxc-start (and lxc-execute) will
> search for the config in /etc/lxc/<containername>.conf or could be provided
> with the path to the config file on command line.
>
> It seems that /var/lib/lxc/<containername> currently only holds the config
> and nothing else, so we can probably get rid of that directory as well.
>
>
>
> Regards,
> Michael
>
> --
> It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Lxc-devel mailing list
> Lxc-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-devel
>