From: Marius via <help-guix@gnu.org>
To: Edouard Klein <edou@rdklein.fr>
Cc: help-guix@gnu.org
Subject: Re: Guix learning exercices
Date: Thu, 21 Nov 2024 18:20:35 +0000 [thread overview]
Message-ID: <AC02C166-3E22-4A6C-BE39-C41E208425D3@disroot.org> (raw)
In-Reply-To: <59D1033D-FCAF-4F51-8CD7-F6CC5FCAF578@rdklein.fr>
Wow, Thank You so much.
For me the most confusing parts are how to deal with the store. How builds are translated into derivations, how derivations are applied. I do not get if G-exp are scheme description of derivations or of builds or in between?
Then the whole bootstrapping process from void is complicated for me, it's like the egg and chicken problem. So in other distros the bootstrapping is precompiled for what I know, and that's it.
But I really want to learn how the bootstrapping is done in Guix the hacker way. I really want to remove the magic veil of low level parts. Below bootstrapping I'm trying to learn how kernel implementations do (I'm learning with XINU OS and beagleboard black). I'm trying to learn by pinching from boths ends. The bootstrapping is like the interface between the two worlds.
Thank you for your hard work and attention.
Best regards,
Marius.
El 21 de noviembre de 2024 17:39:08 UTC, Edouard Klein <edou@rdklein.fr> escribió:
>I'm not aware of anything like this existing, but I am in the process of writing a series of challenges, with the completion of each earning the chanllenger a badge, I will post an email in this thread when this effort pans out.
>
>If you can say more about the kind of things you find confusing, that would be of help.
>
>
>
>Le 21 novembre 2024 18:11:42 GMT+01:00, Marius via <help-guix@gnu.org> a écrit :
>>Good evening,
>>
>>
>>I was wondering if there are any exercices online or not, in order to learn Guix in a "practical" way. I've read all the Guix Reference Manual but with the lack of real exercises that challenge me to actually get hands on I fear that I will quickly forget the "theoretical" knowledge. Plus I'm also interested in learning all the small implementation details. I came to Guix because other distros felt to obscure on what was my OS doing, obscurity by "hardcoded" stuff. And Guix does not feel obscure but rather confusing with so much things to deal with. Maybe there is material out there that teaches and exercices Guix development from bot to top or at least some kind of hands on tutorials (like git-tutorial).
>>
>>
>>Thank you,
>>Marius.
next prev parent reply other threads:[~2024-11-21 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 17:11 Guix learning exercices Marius via
2024-11-21 17:55 ` Michael Dahlberg
2024-11-21 18:00 ` Josh Marshall
[not found] ` <59D1033D-FCAF-4F51-8CD7-F6CC5FCAF578@rdklein.fr>
2024-11-21 18:20 ` Marius via [this message]
2024-11-21 19:41 ` Dev@icepic
[not found] ` <pCiIhh1OYLyNDBMR5pyo_i94TmEM9rMMIl2szT_ODeGjlZBoqaX3bJ9IjeIPcjn70hY70oIv3HUflrOShQ0LoBSExoAtVtHy5t8vZjR4nXg=@recursoft.org>
2024-11-21 18:41 ` Marius 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
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=AC02C166-3E22-4A6C-BE39-C41E208425D3@disroot.org \
--to=help-guix@gnu.org \
--cc=edou@rdklein.fr \
--cc=mariusgr@disroot.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).