Re: CVE-2016-7434 NTP

2016-12-12 Thread Michelle Sullivan
Dimitry Andric wrote: On 08 Dec 2016, at 06:08, Michelle Sullivan wrote: Are we going to get a patch for CVE-2016-7434 on FreeBSD 9.3? On Nov 22, in r309009, Xin Li merged ntp 4.2.8p9, which fixes this issue, to stable/9: https://svnweb.freebsd.org/changeset/base/309009

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Kevin Oberman
On Mon, Dec 12, 2016 at 1:16 AM, tech-lists wrote: > On 12/12/2016 09:07, Thomas Mueller wrote: > >> My question is, do you build modules redundantly, or just once? >> I don't want to build the same modules more than once. >> > > For me - redundantly, I guess. It's not like

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Herbert J. Skuhra
tech-lists skrev: > > Hi, > > Yep I'm sure. The only extra I've added is for > nvidia-driver. Everything else is a "without" directive. My > /etc/src.conf looks like this: > > # less src.conf > PORTS_MODULES=x11/nvidia-driver > [...] > This is the error I get when I try to build kernel and

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Herbert J. Skuhra
Kevin Oberman skrev: > > On Mon, Dec 12, 2016 at 1:16 AM, tech-lists wrote: >> On 12/12/2016 09:07, Thomas Mueller wrote: >> >>> My question is, do you build modules redundantly, or just once? >>> I don't want to build the same modules more than once. >>> >> >> For me -

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Herbert J. Skuhra
Kevin Oberman skrev: > > Clearly the documentation is a bit behind the times. For some time people > have used KERNCONF to build multiple kernels, but that was a lucky things > that was not officially supported. It just happened to work. Then, with > 11.0, it no longer did in many cases sue to

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread tech-lists
On 12/12/2016 09:07, Thomas Mueller wrote: My question is, do you build modules redundantly, or just once? I don't want to build the same modules more than once. For me - redundantly, I guess. It's not like it takes a lot of time or space on the compiling machine, and I ensure that everything

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Thomas Mueller
> BUILDKERNELS=PUMPKIN GENERIC > > to your /etc/src.conf and removing the KERNCONF line from /etc/make.conf > > before you run it again. KERNCONF goes on the "make buildkernel" command, > > not into /etc/make.conf, but should not be necessary at all if /etc/src.conf > > contains the list of

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

2016-12-12 Thread Kevin Oberman
On Mon, Dec 12, 2016 at 4:20 PM, Herbert J. Skuhra wrote: > Kevin Oberman skrev: > > > > Clearly the documentation is a bit behind the times. For some time people > > have used KERNCONF to build multiple kernels, but that was a lucky things > > that was not officially

Re: Is System V IPC namespace still shared across jails?

2016-12-12 Thread Christian Schwarz
With the new jail parameters, new namespaces for SysV IPC are possible on FreeBSD 11. For those ezjail users, add something like this to the jail's config after creating it using 'ezjail-admin create': export jail_postgres_parameters="sysvmsg=new sysvsem=new sysvshm=new" Cheers, Christian

Is System V IPC namespace still shared across jails?

2016-12-12 Thread Mark Martinec
Regarding installation of PostgreSQL in a FreeBSD jail, the web hold plenty of warnings/advice that each postgres instance should have a unique UID, otherwise they stumble across each other's feet: | allow.sysvipc | A process within the jail has access to System V IPC primitives. In the |