From: "Ludovic Courtès" <ludo@gnu.org>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 60112@debbugs.gnu.org
Subject: [bug#60112] [PATCH] website: Add post about guix shell fhs option.
Date: Mon, 26 Dec 2022 00:58:35 +0100 [thread overview]
Message-ID: <87lemvujbo.fsf@gnu.org> (raw)
In-Reply-To: <877cyrlsep.fsf@protonmail.com> (John Kehayias's message of "Fri, 16 Dec 2022 07:27:47 +0000")
Hi John,
I’m seeing this only now, apologies! (I thought the discussion was
continuing in the guix-devel thread, my bad. :-/)
John Kehayias <john.kehayias@protonmail.com> skribis:
> From e13d5a92a98680bf0d0b30fbd124a5e7725f7475 Mon Sep 17 00:00:00 2001
> From: John Kehayias <john.kehayias@protonmail.com>
> Date: Fri, 16 Dec 2022 02:22:17 -0500
> Subject: [PATCH] website: Add post about guix shell fhs option.
>
> * website/posts/guix-shell-fhs.md: New file.
> website/static/blog/img/guix-shell-fhs.gif: New file.
Overall looks great to me and pretty much ready to go. Minor
suggestions.
> +++ b/website/posts/guix-shell-fhs.md
> @@ -0,0 +1,140 @@
> +title: FHS Comes to Guix Containers
Should we spell “FHS” out?
> +GNU Guix is different from most other GNU/Linux distributions and perhaps nowhere is that more obvious than the organization of the filesystem: Guix does not conform to the [Filesystem Hierarchy Standard](https://refspecs.linuxfoundation.org/fhs.shtml) (FHS). In practical terms, this means there is no global `/lib` containing libraries, `/bin` containing binaries,<sup><a id="fnr.1" class="footref" href="#fn.1" role="doc-backlink">1</a></sup> and so on. This is very much at the core of how Guix works and some of the convenient features, like per-user installation of programs (different versions, for instance) and a declarative system configuration where the system is determined from a configuration file.
Haunt uses Guile-Commonmark, and I don’t think we can use inline HTML
nor footnotes actually. A bit of a bummer, but maybe you can
approximate that with:
`/bin` containing binaries¹, …
and at the bottom:
¹ Blah.
It might be worth mentioning somewhere that the feature is included in
the just-released 1.4.0 now.
> +Here is a very simple example:
> +
> + $ guix shell --container --emulate-fhs coreutils -- ls /bin | head
> + [
> + b2sum
> + base32
> + base64
> + basename
> + basenc
> + cat
> + catchsegv
> + chcon
> + chgrp
Example examples in triple backquotes (i.e., ```), without extra
indentation.
> +[![img](guix-shell-fhs.gif "Or, if you like to see it more in motion, here's a gif.")](guix-shell-fhs.gif)
The syntax is:
![Alt text.](/static/blog/img/…)
Note that the alt text is not shown unless one disables pictures or
hovers over the picture. So “Or, if you like […]” should probably be
written above the image.
You can test the web site with:
guix shell
and then:
export GUIX_WEB_SITE_LOCAL=y
haunt build
haunt serve
Should we publish it after Jan. 1st, since people are more likely to
miss it during the holiday season?
Thanks!
Ludo’.
next prev parent reply other threads:[~2022-12-25 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 7:27 [bug#60112] [PATCH] website: Add post about guix shell fhs option John Kehayias via Guix-patches via
2022-12-25 23:58 ` Ludovic Courtès [this message]
2023-01-03 22:54 ` Ludovic Courtès
2023-01-03 23:07 ` John Kehayias via Guix-patches via
2023-01-04 10:31 ` Ludovic Courtès
2023-01-04 17:43 ` [bug#60112] [PATCH v2] " John Kehayias via Guix-patches via
2023-01-04 18:23 ` [bug#60112] [PATCH v3] " John Kehayias via Guix-patches via
2023-01-06 12:49 ` [bug#60112] [PATCH] " Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 23:39 Drafting a Guix blog post on the FHS container Jim Newsome
2023-01-04 17:47 ` John Kehayias
2023-01-04 18:18 ` [bug#60112] " jman via Guix-patches via
2023-01-05 21:00 ` [bug#60112] [PATCH] website: Add post about guix shell fhs option Ludovic Courtès
2023-01-05 21:03 ` John Kehayias via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lemvujbo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60112@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.