From: swedebugia@riseup.net
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: help-guix@gnu.org, help-guix-bounces+swedebugia=riseup.net@gnu.org
Subject: Re: question re. installing software & init system
Date: Fri, 01 Jan 2016 20:09:14 +0100 [thread overview]
Message-ID: <487782a0a9db50b07c2dfcefdbaf0307@riseup.net> (raw)
In-Reply-To: <CAJ=RwfYQn=Fox3LuvMQ7jQESR3YoJTUiW5268rLN4w1OmTLuFw@mail.gmail.com>
On 2016-01-01 19:23, Thompson, David wrote:
> On Fri, Jan 1, 2016 at 12:52 PM, Miles Fidelman
> <mfidelman@meetinghouse.net> wrote:
snip
>> Does GuixSD respect the LSB, and in particular /usr/local/.... ?
>
> No. We don't use LSB, nor do we conform to the FHS, because they
> conflict with functional, stateless system management. Of course, you
> could 'mkdir -p /usr/local' on a GuixSD system and do whatever you'd
> like. In Guix, all software builds are kept in /gnu/store, and each
> user on the system maintains one or more "profiles" that reference
> some subset of the software available in the store. This gives each
> user the freedom to use the software of their choosing, without
> worrying about global conflicts with the system or other users. Thus,
> /usr is obsoleted.
I would like to improve the doc with a section which grafically and
details explain where GuixSD differs from other systems people are used
to.
Here is a start:
GuixSD implements symlinks on a wide scale to succeed in being
functional and transactional.
/bin obsolete (contains only 1 file sh which symlinks to the /gnu/store
(see below)
/boot contains grub without symlinks
/dev as usual
/etc mostly symlinks to files in /gnu/store or /run/current except for
group, passwd, shadow and a few others
/gnu only contains the store which is READONLY to all other processes
than guix-daemon
/home as usual with the differences introduces to make unpriveledged
package management stored in .guix-profile
/mnt as usual
/proc as usual
/usr does not exist unless you create it
/root as usual and contains the system profile?
/run special to GuixSD - it contains a farm of symlinks according to the
operating system description installed by the administrator of the
system (requires root acces to change)
/sys no idea :p
/tmp as usual - guix-daemon uses this extensively when building
derivation so ensure that you have >10 GB if you are going to build
large packages as for example libreoffice
/var as usual - guix-daemon uses this to create the temporary
build-chroots and a bunch of other stuff changed during runtime.
Was this clear enough?
cheers
swedebugia
prev parent reply other threads:[~2016-01-01 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 17:26 question re. installing software & init system Miles Fidelman
2015-12-31 22:41 ` Thompson, David
2016-01-01 17:52 ` Miles Fidelman
2016-01-01 18:23 ` Thompson, David
2016-01-01 19:09 ` swedebugia [this message]
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=487782a0a9db50b07c2dfcefdbaf0307@riseup.net \
--to=swedebugia@riseup.net \
--cc=dthompson2@worcester.edu \
--cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
--cc=help-guix@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.
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).