From: tokiclover <tokiclover@gmail.com>
To: supervision@list.skarnet.org
Subject: [ANNOUNCE] supervision-0.14.7 stable release
Date: Wed, 16 Jan 2019 11:32:04 +0100 [thread overview]
Message-ID: <20190116103203.GA4540@gmail.com> (raw)
Hi,
Here comes a new[1] stable release with fixes of v0.14.x.
It was hard to make udev and LVM(2) play nicely because:
- LVM would always stall waiting for devices to be processed by udev;
- and udev is unreliable when it comes to timeout when handling devices;
so using udevadm(8) to wait udev to be ready is simply a joke. It's only
a question workarounds... I did many of them. I am really tired of
these $*#! and I will leave them if upstream break them... again.
I was busy and could not stabilize a few things in time a few months ago
when I tried to. There were a few bugs here and there; and udev+LVM is
just too much for rootfs. I should have spent tons and tons of time got
something working.
Finaly, there is something workable with udev+LVM for rootfs.
I am working on new release with an complete init-system and service
manager. I am basically working on a init(8) with new superivision apps.
Stay tuned for the new major version.
[0]: https://gitlab.com/tokiclover/supervision
[1]: https://gitlab.com/tokiclover/supervision/tags
reply other threads:[~2019-01-16 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190116103203.GA4540@gmail.com \
--to=tokiclover@gmail.com \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).