Date: Tue, 24 Sep 2024 14:45:17 -0400 From: Chris Ross <cross+freebsd@distal.com> To: Matthias Fechner <idefix@fechner.net> Cc: Helge Oldach <freebsd@oldach.net>, freebsd-ports@freebsd.org Subject: Re: isc-dhcpd rc.d failure Message-ID: <0CF8FBC1-2029-47BB-BB26-89BBFF44DB0F@distal.com> In-Reply-To: <44c6f9c7-fc74-486a-b404-cbda7de834ac@fechner.net> References: <202409240711.48O7BLc6095170@nuc.oldach.net> <5D593C65-8BBA-4583-B9DD-9ABEA512714D@distal.com> <44c6f9c7-fc74-486a-b404-cbda7de834ac@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 24, 2024, at 07:56, Matthias Fechner <idefix@fechner.net> = wrote: >=20 > you are aware, that dhcpd is EOL since end of 2022: > https://www.isc.org/dhcp/ >=20 > and was replaced by kea? >=20 > Not sure if it makes sense to put much effort into it. The upstream being EOL=E2=80=99d doesn=E2=80=99t, IMO, affect the = support we have in ports. Unless we=E2=80=99re EOL=E2=80=99ing the port, then we should fix the = problem in our script that we install with the port. - Chris=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0CF8FBC1-2029-47BB-BB26-89BBFF44DB0F>