From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>,
guix-devel-bounces+amirouche=hypermove.net@gnu.org
Subject: Re: Roadmap for Guix 1.0
Date: Wed, 29 Aug 2018 18:05:50 +0200 [thread overview]
Message-ID: <CAL7_Mo9dhAzxypE9jmrXSeoRh1hQ9D4KBNxVmY4UfRNC3M=gPA@mail.gmail.com> (raw)
In-Reply-To: <87a7phtrbw.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
Le lun. 20 août 2018 à 09:45, Ricardo Wurmus <rekado@elephly.net> a écrit :
>
> Amirouche Boubekki <amirouche@hypermove.net> writes:
>
> >> I’ve pushed to guix/maintenance.git a list of things that IMO we should
> >> do or might want to do for 1.0, with the understanding that 1.0 should
> >> happen in 2018 (or early 2019 at the latest!). :-)
> >>
> >>
> https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/1.0.org
> >>
> >
> > I see no mention of containers. What is the status and goal about that
> > subject?
>
> What feature regarding containers would you like to know more about?
>
Thanks for your reply. I use containers (via LXC) as lightweight Virtual
Machines
as such I can emulate my use of LXC with guix already using a VM.
The difference I see between guix containers and LXC is that in LXC the
container
has its own network device and an IP. What I usually do with LXC:
a) start the lxc container
b) ssh into it and
proceed as if I was in a Xen Virtuam Machine.
Have nice day!
>
> “guix environment”, for example, supports isolation through container
>
[-- Attachment #2: Type: text/html, Size: 1957 bytes --]
next prev parent reply other threads:[~2018-08-29 16:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 15:18 Roadmap for Guix 1.0 Ludovic Courtès
2018-07-30 1:23 ` Pjotr Prins
2018-07-30 9:02 ` Nils Gillmann
2018-07-30 12:47 ` Pierre Neidhardt
2018-08-19 11:06 ` LVM support Ludovic Courtès
2018-08-29 16:12 ` Roadmap for Guix 1.0 Amirouche Boubekki
2018-08-30 11:46 ` Pierre Neidhardt
2018-08-30 12:04 ` Ludovic Courtès
2018-08-30 12:57 ` Ricardo Wurmus
2018-08-30 14:20 ` Tobias Geerinckx-Rice
2018-08-30 15:17 ` Nils Gillmann
2018-08-30 19:13 ` George Clemmer
2018-08-30 20:12 ` Gábor Boskovits
2018-08-31 14:25 ` George Clemmer
2018-08-31 15:45 ` Vincent Legoll
2018-08-31 15:54 ` Amirouche Boubekki
2018-09-01 7:36 ` rchar01
2018-09-01 9:27 ` Pjotr Prins
2018-09-01 10:09 ` Nils Gillmann
2018-08-30 15:36 ` George Clemmer
2018-08-30 17:11 ` Hartmut Goebel
2018-08-30 18:17 ` Jan Nieuwenhuizen
2018-08-30 21:45 ` Taylan Kammer
2018-07-30 5:08 ` Chris Marusich
2018-07-30 7:33 ` Pierre Neidhardt
2018-08-19 11:19 ` Ludovic Courtès
2018-08-19 11:11 ` Ludovic Courtès
2018-08-20 1:12 ` Chris Marusich
2018-08-30 19:34 ` Ricardo Wurmus
2018-08-19 21:52 ` Amirouche Boubekki
2018-08-20 7:44 ` Ricardo Wurmus
2018-08-29 16:05 ` Amirouche Boubekki [this message]
2018-09-04 22:55 ` fis trivial
2018-09-04 23:09 ` Adam Van Ymeren
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL7_Mo9dhAzxypE9jmrXSeoRh1hQ9D4KBNxVmY4UfRNC3M=gPA@mail.gmail.com' \
--to=amirouche.boubekki@gmail.com \
--cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).