Date: Thu, 9 Jul 2020 17:43:33 -0700 From: Doug Hardie <bc979@lafn.org> To: Mark Johnston <markj@FreeBSD.org> Cc: freebsd-net@freebsd.org, Michael Tuexen <tuexen@freebsd.org> Subject: Re: making SCTP loadable and removing it from GENERIC Message-ID: <444BE513-EE05-4F3C-89C4-5EBFFCBC7819@mail.sermon-archive.info> In-Reply-To: <20200709232400.GA83392@raichu> References: <20200709151300.GC8947@raichu> <63F4446F-DECF-4DE8-99CA-EC8755A5D4A1@mail.sermon-archive.info> <20200709201044.GG8947@raichu> <3DC5AC46-604E-4CB4-93EC-6421ED575DBB@mail.sermon-archive.info> <20200709232400.GA83392@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9 July 2020, at 16:24, Mark Johnston <markj@FreeBSD.org> wrote: > > On Thu, Jul 09, 2020 at 02:15:40PM -0700, Doug Hardie wrote: >>> On 9 July 2020, at 13:10, Mark Johnston <markj@freebsd.org> wrote: >>> Hopefully "protocol not supported" is a sufficiently descriptive error >>> message. >> >> Actually, the users of these systems would have no clue about that message. All they would figure out is that the system is down and they can't do their job and bitch to the CEO. I am going to assume that that error will be produced by the socket call and I have added code to check for it and email me if it occurs. I believe that the only viable approach for us is the rc.conf solution as some of these systems are rhapsberry pi 3s which I understand don't use the loader.conf file. > > My RPi3 boots via loader.efi, which reads loader.conf. Thanks. I did not know that. I don't have a RPi to test yet. All of the ones are in production at other locations. -- Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444BE513-EE05-4F3C-89C4-5EBFFCBC7819>