From: Jack Hill <jackhill@jackhill.us>
To: Ognen Duzlevski <maketo@sdf.org>
Cc: guile-user@gnu.org
Subject: Re: GNU Shepherd 0.9.0 released
Date: Fri, 8 Apr 2022 10:19:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2204081016530.16670@marsh.hcoop.net> (raw)
In-Reply-To: <86r167r8kf.fsf@sdf.org>
On Fri, 8 Apr 2022, Ognen Duzlevski wrote:
>
> Tim Van den Langenbergh <tmt_vdl@gmx.com> writes:
>
>> Ognen Duzlevski <maketo@sdf.org> writes:
>>
>>> Ludovic Courtès <ludo@gnu.org> writes:
>>>
>>>> [[PGP Signed Part:Undecided]]
>>>> We are pleased to announce the GNU Shepherd version 0.8.1. This release
>>>> represents 49 commits by 3 people, bringing a new concurrent,
>>>> event-driven core, improved logging, and on-demand service startup.
>>>
>>> Does Shepherd only run on Linux?
>>>
>>> It is intended for use on GNU/Hurd, but it is supposed to work on every
>>> POSIX-like system where Guile is available. In particular, it has been
>>> tested on GNU/Linux.
>>
>> So if you prefer to run the Hurd rather than Linux, it should work fine.
>
> Tim, thanks!
>
> I run FreeBSD and it uses kqueue instead of epoll so even if Guile
> technically runs on FreeBSD, fibers do not.
>
> I don't mind submitting a patch to make this happen.
Some pointers you might find helpful:
When Ludo’ originally announced this work⁰, this limitation was known,
but, fortunately, work is already underway to bring fibers to other
platforms via libevent¹.
0: https://lists.gnu.org/archive/html/guix-devel/2022-03/msg00125.html
1: https://github.com/wingo/fibers/pull/53
Best,
Jack
next prev parent reply other threads:[~2022-04-08 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 21:25 GNU Shepherd 0.9.0 released Ludovic Courtès
2022-04-06 23:18 ` Zhu Zihao
2022-04-07 1:54 ` Ognen Duzlevski
2022-04-08 11:31 ` Tim Van den Langenbergh
2022-04-08 13:45 ` Ognen Duzlevski
2022-04-08 14:19 ` Jack Hill [this message]
2022-04-07 4:12 ` Liliana Marie Prikler
2022-04-07 14:11 ` Brian Cully
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2204081016530.16670@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guile-user@gnu.org \
--cc=maketo@sdf.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).