From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add systemd.
Date: Sun, 01 Apr 2018 13:01:28 -0400 [thread overview]
Message-ID: <87woxqdfo7.fsf@netris.org> (raw)
In-Reply-To: <87lge7f5ws.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 01 Apr 2018 14:49:23 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello Marius,
>
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> As discussed at FOSDEM, it is clear that The Shepherd does not have what
>> it takes to boot a modern Linux system. While it works today, adding
>> bootloader, DNS server, NTP client, syslog, udev, seat management,
>> dishwasher, hardware database, network management and other essential
>> PID 1 features is going to take too much effort and duplicate work.
>
> To be honest, while the Shepherd has been a fun hack, I’ve been more and
> more feeling that yeah, it wouldn’t cut it in the long term (it’s also
> become clearer Scheme as convenient as C when it comes to systems
> programming and things like dealing with dependency graphs.)
>
> Thanks a lot for taking this step!
Does this mean that our Hurd port is to be abandoned, or is the plan to
maintain a fork of systemd that supports the Hurd?
Mark
next prev parent reply other threads:[~2018-04-01 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 12:22 [PATCH] gnu: Add systemd Marius Bakke
2018-04-01 12:49 ` Ludovic Courtès
2018-04-01 17:01 ` Mark H Weaver [this message]
2018-04-01 20:07 ` Chris Marusich
2018-04-01 20:18 ` Marius Bakke
2018-04-02 21:36 ` Ludovic Courtès
2018-04-03 22:33 ` Joshua Branson
2018-04-04 0:44 ` Leo Famulari
2018-04-04 8:41 ` Ludovic Courtès
2018-04-06 18:57 ` Marius Bakke
2018-04-01 12:52 ` Nils Gillmann
2018-04-01 13:03 ` Martin Castillo
2018-04-01 14:04 ` Efraim Flashner
2018-04-01 14:19 ` Nils Gillmann
2018-04-01 20:11 ` Marius Bakke
2018-04-01 20:30 ` Nils Gillmann
2018-04-01 14:23 ` Jan Nieuwenhuizen
2018-04-01 21:55 ` Björn Höfling
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=87woxqdfo7.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).