From: Steve George <steve@futurile.net>
To: guix-devel@gnu.org, help-guix@gnu.org
Subject: Guix Social today - Bootstrapping RISC-V talk by Ekaitz
Date: Tue, 17 Sep 2024 07:58:48 +0100 [thread overview]
Message-ID: <jhzfn6opq7zyyxlrhenuj2hjg5xam64o4gnkijvjdgojakmnxv@fjjqajnmdt6w> (raw)
Hi all,
The next Guix Social is today, Tuesday, with a talk by Ekaitz Zarraga on bootstrapping RISC-V. Times:
17:00 UTC, 18:00 BST (London), 19:00 CEST (Paris), 13:00 EDT (New York)
Link to join:
https://meet.jit.si/london-guix-meetup
The bootstrapping problem is that many OS's can't build themselves from source. Somewhere in the chain there is a compiler binary that was created at a previous point in history. The impact on security and trust is that we can't assure ourselves that the platform hasn't been backdoored [0]. Ekaitz and many others have been working on bringing up RISC-V with a full source bootstrap for the last couple of years. In this talk he'll introduce RISC-V, the bootstrap problem and talk about the journey to a full source bootstrap in Guix.
If you'd like to be notified about **future meetups** you can subscribe to the Wiki or to the Meet-up:
https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
https://www.meetup.com/guix-london/events/303448758/
Hope to see you there!
Steve / Futurile
[0] https://guix.gnu.org/blog/2019/guix-reduces-bootstrap-seed-by-50/
next reply other threads:[~2024-09-17 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 6:58 Steve George [this message]
2024-09-20 17:14 ` Guix Social today - Bootstrapping RISC-V talk by Ekaitz Steve George
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=jhzfn6opq7zyyxlrhenuj2hjg5xam64o4gnkijvjdgojakmnxv@fjjqajnmdt6w \
--to=steve@futurile.net \
--cc=guix-devel@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).