From: Joshua Branson <jbranso@fastmail.com>
To: guix-devel@gnu.org
Subject: Re: Help understand some guix concepts
Date: Mon, 01 Jan 2018 12:49:54 -0800 [thread overview]
Message-ID: <1514839794.3690147.1221084920.0FA74B19@webmail.messagingengine.com> (raw)
In-Reply-To: <CAL7_Mo9+T40hD_z-8=dSRecOHgzhHezzgLwM_2Y097oXiBxfbQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
By no means am I a developer, but I can try to explain some things...
A profile is a collection of packages. Each user on the system has a
profile of his packages. So Jerry has a profile of Emacs 24, Iceweasel
50, etc. Jill also uses the system, but she has packages Tetris 5.4,
Emacs 23, etc. Jerry's packages and Jill's packages are independent of
one another and cause no conflicts.
There is also a system profile. This is the collection of packages that
boots your system. For example if Jerry uses gnome, usually his profile
will not contain the gnome program. Instead gnome is found under the
system profile.
The root filesystem is everything under / right?
chroot is a way of letting applications thing that they are running with
full root privileges when they are not.
A container restricts what an application can access. Firefox for
example should only be able to access your Downloads directory. It
should not be able to read your gpg keys. One can run Firefox in a
container to limit the things that Firefox can access.
docker I believe is a way of running a web application. Web application
development is getting really hard these days. Your application can
have js dependencies, python dependencies, etc. Each language has its
own package manager, and if one packages gets updated your web
application can refuse to work. Docker just freezes everything so that
it works. Then you run that frozen image.
lxc? No idea.
On Mon, Jan 1, 2018, at 11:31 AM, Amirouche Boubekki wrote:
> Héllo,
>
> It's a long time I did not read the manual. So I read he manual this
> afternoon.>
> I have to say that I don't really understand some guix concepts and
> how they map to the rest of the world.>
> Can someone try to explain to me how the following concepts are
> related to each other:>
> Environments, profiles, gc roots, root filesystem, chroot, containers,
> docker and lxc>
> TIA
[-- Attachment #2: Type: text/html, Size: 3276 bytes --]
next prev parent reply other threads:[~2018-01-01 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 19:31 Help understand some guix concepts Amirouche Boubekki
2018-01-01 20:49 ` Joshua Branson [this message]
2018-01-01 21:04 ` Martin Castillo
2018-01-02 17:10 ` Martin Castillo
2018-01-01 21:39 ` Amirouche Boubekki
2018-01-09 12:41 ` Ludovic Courtès
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=1514839794.3690147.1221084920.0FA74B19@webmail.messagingengine.com \
--to=jbranso@fastmail.com \
--cc=guix-devel@gnu.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.
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).