Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-06-01 Thread Rodney W. Grimes
> rai...@ultra-secure.de wrote: > > > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > > department who is technically responsible for the service gets around > > redoing that service. > > >From my understanding from reading the bug (though it's not entirely clear > in this

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-31 Thread Jamie Landeg-Jones
rai...@ultra-secure.de wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. >From my understanding from reading the bug (though it's not entirely clear in this thread), this

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-28 Thread Xin LI
On Mon, May 27, 2019 at 7:08 AM wrote: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. > > The patch attached for the bug is for disabling these options by > default, following a few reasons which I'm going

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 8:23 PM Enji Cooper wrote: > > On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > >> >> > On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: >> > >> > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> >> Hi Rainier, >>

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Enji Cooper
> On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper > wrote: > > > On May 27, 2019, at 08:27, rai...@ultra-secure.de > > wrote: > > > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >>

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Warner Losh
On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > > > On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: > > > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >> Hi Rainier, > >> On Mon, May 27, 2019 at 7:47 AM wrote: > >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Enji Cooper
> On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: > > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> Hi Rainier, >> On Mon, May 27, 2019 at 7:47 AM wrote: >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >>> department who is technically responsible for the service

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread rainer
Am 2019-05-27 17:05, schrieb Conrad Meyer: Hi Rainier, On Mon, May 27, 2019 at 7:47 AM wrote: I have a 32bit FreeBSD 6 binary that I'll need for a bit until the department who is technically responsible for the service gets around redoing that service. Even if this proposal is approved, it

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Konstantin Belousov
On Mon, May 27, 2019 at 03:55:21PM +0200, voida...@420blaze.it wrote: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. What problem are you trying to solve ? > > The patch attached for the bug is for

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Conrad Meyer
Hi Rainier, On Mon, May 27, 2019 at 7:47 AM wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. Even if this proposal is approved, it would only affect 13+. You could still

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread rainer
Am 2019-05-27 15:55, schrieb voida...@420blaze.it: Hello, I wanted to discuss about bug 231768 a bit: it is about keeping COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. The patch attached for the bug is for disabling these options by default, following a few reasons which I'm