From: Vagrant Cascadian <vagrant@debian.org>
To: Brice Waegeneire <brice@waegenei.re>, guix-devel@gnu.org
Subject: Re: [GSOC 2020] Booting via network
Date: Mon, 30 Mar 2020 16:16:25 -0700 [thread overview]
Message-ID: <877dz1fn7a.fsf@ponder> (raw)
In-Reply-To: <2a1045c19652dfa74ed3735a860cb88d@waegenei.re>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On 2020-03-30, Brice Waegeneire wrote:
> I know it's quite late to submit a GSOC proposal but here it's.
> I would like to work on the project suggested by Danny to
> add PXE support to Guix. Which has been requested several
> times on IRC and in the ML. This would get us a step closer
> to provisioning bare bone machines directly from Guix.
I was just thinking Guix needed network boot support yesterday! Happy to
hear you're looking into it...
I've been the LTSP maintainer in Debian for almost 15 years, so have a
good amount of experience with network booting. LTSP was rewritten from
scratch last year and there might be elements of it useful to you:
https://ltsp.org
None of it is scheme code, but there are possibly some useful ideas in
there you could make use of. One of the big changes is making extensive
use of iPXE, though that might need some further auditing to meet the
FSDG (Free Software Distribution Guidelines?) for inclusion into Guix.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-03-30 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 21:44 [GSOC 2020] Booting via network Brice Waegeneire
2020-03-30 22:10 ` Vincent Legoll
2020-04-15 18:57 ` Brice Waegeneire
2020-04-15 20:09 ` Vincent Legoll
2020-03-30 23:16 ` Vagrant Cascadian [this message]
2020-04-10 13:44 ` iPXE network booting (was Re: [GSOC 2020] Booting via network) Giovanni Biscuolo
2020-04-12 18:01 ` Vincent Legoll
2020-04-15 19:33 ` Brice Waegeneire
2020-04-15 19:10 ` [GSOC 2020] Booting via network Brice Waegeneire
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=877dz1fn7a.fsf@ponder \
--to=vagrant@debian.org \
--cc=brice@waegenei.re \
--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 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.