supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: Scott Colby <scott@scolby.com>
Cc: Alex Efros via supervision <supervision@list.skarnet.org>
Subject: Re: Supervision on the BSD's
Date: Mon, 11 Apr 2022 12:18:09 -0500	[thread overview]
Message-ID: <20220411171809.4xkfwdwdyqiwyi6b@mail.imca-cat.org> (raw)
In-Reply-To: <0c1d24f1-fa0e-4c00-a94f-3173110b3800@www.fastmail.com>

On 04/09, Scott Colby wrote:
> Finally, if you wanted to create a router that you could (metaphorically)
> put in a closet and forget about for 5 years, what approach would
> you take? My initial thought was OpenBSD + s6, but I worry now that
> there could be an impedance mismatch between these systems.
> 
> Any thoughts people have on this will be greatly appreciated.

Hi, Scott!

Re putting it in a closet and forgetting about it for five years, one
thing to note is that according to

  https://www.openbsd.org/errata70.html

OpenBSD's stable branch is supported for one year, so if you were
tracking that, you'd have to upgrade every year.

NetBSD's stable branch is supported for longer than one year based on

  https://www.netbsd.org/releases/formal.html#history

but they don't say exactly how long.  The trend to me looks like
at least three years.  They currently support their 8 and 9 stable
branches which were released on July 17, 2018, and February 14, 2020,
respectively.

FreeBSD's stable branch is supported for five years according to

  https://www.freebsd.org/security/#sup

And of course there are other BSDs that I haven't listed.

Regards,

Lewis

      parent reply	other threads:[~2022-04-11 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  5:38 Scott Colby
2022-04-09  7:57 ` Alexis
2022-04-09 11:36 ` Ramarro Marrone
2022-04-10 18:56   ` Oliver Schad
2022-04-09 13:43 ` Laurent Bercot
2022-04-11 17:18 ` J. Lewis Muir [this message]

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=20220411171809.4xkfwdwdyqiwyi6b@mail.imca-cat.org \
    --to=jlmuir@imca-cat.org \
    --cc=scott@scolby.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).