HEADS-UP: installworld on r299292 through r299317 will replace master.passwd, passwd, and group files

Thanks to O. Hartmann promptly reporting this, it was discovered that 'installworld' on revisions r299292-r299317 will silently replace /etc/passwd, /etc/master.passwd, and /etc/group with the defaults. It is possible there are other files affected. One file I can think of off-hand is

Re: WARNING: [r299313] make installworld overwrites master.passwd and group!

On Tue, May 10, 2016 at 07:15:57AM +0200, O. Hartmann wrote: > On a most recent buildworld with make installworld/installkernel I faced the > fact that all the entries in /etc/master.passwd and /etc/group were reset to > the initial/vanilla values. Luckily, I was able to fetch backups > from

WARNING: [r299313] make installworld overwrites master.passwd and group!

On a most recent buildworld with make installworld/installkernel I faced the fact that all the entries in /etc/master.passwd and /etc/group were reset to the initial/vanilla values. Luckily, I was able to fetch backups from /var/backups. I do not know which essential config files additionally got

Re: wired memory leak at r298785

> On May 9, 2016, at 4:30 PM, Wolfgang Zenker wrote: > > * Scott Long [160503 16:27]: >>> On May 3, 2016, at 12:20 AM, Mark Johnston wrote: >>> [..] >>> This was causing problems on one of my amd64 systems, so it's not >>>

Re: wired memory leak at r298785

* Scott Long [160503 16:27]: >> On May 3, 2016, at 12:20 AM, Mark Johnston wrote: >> [..] >> This was causing problems on one of my amd64 systems, so it's not >> specific to powerpc64. It turns out to be due to r298004: the CCB >> allocated in

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Mon, May 09, 2016 at 12:43:42PM -0700, John Baldwin wrote: > ... > > I suppose there's probably some way to arrange things so the KERNCONF > > specification in /etc/src.conf has one value during "buildkernel" and a > > different value during "inistallkernel" -- but ... seriously...??!? > > One

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Monday, May 09, 2016 11:45:44 AM David Wolfskill wrote: > On Mon, May 09, 2016 at 11:05:55AM -0700, John Baldwin wrote: > > On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > > > [Recipient list trimmed a bit -- dhw] > > ... > > > > 2 kernels get installed? Even if the old

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Mon, May 09, 2016 at 11:46:02AM -0700, Freddie Cash wrote: > On Mon, May 9, 2016 at 11:40 AM, Ultima wrote: > > > If multiple kernels are being installed like this, eg KERNCONF="FOO BAR", > > which of the two would be default during boot? FOO because it came first? > >

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Mon, May 9, 2016 at 11:40 AM, Ultima wrote: > If multiple kernels are being installed like this, eg KERNCONF="FOO BAR", > which of the two would be default during boot? FOO because it came first? ​Correct. At least, that's the way it's worked in the past, and

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Mon, May 09, 2016 at 11:05:55AM -0700, John Baldwin wrote: > On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > > [Recipient list trimmed a bit -- dhw] > ... > > > 2 kernels get installed? Even if the old behaviour was to only install 1 > > > kernel, if you are listing 2 kernels in

Re: NO_INSTALLEXTRAKERNELS and PkgBase

If multiple kernels are being installed like this, eg KERNCONF="FOO BAR", which of the two would be default during boot? FOO because it came first? On Mon, May 9, 2016 at 2:05 PM, John Baldwin wrote: > On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > > [Recipient

Re: NO_INSTALLEXTRAKERNELS and PkgBase

On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > [Recipient list trimmed a bit -- dhw] > > I'm speaking up here because IIRC, I whined to Gleb at what I perceived > to be a POLA violation a while back > > On Sat, May 07, 2016 at 09:59:06AM +0200, Ben Woods wrote: > > On 7 May

Re: i915kms broken at some commit between r296485 and r297692?

On 05/09/16 18:10, Hans Petter Selasky wrote: On 05/09/16 04:34, Sergey Manucharian wrote: I'm running FreeBSD 11.0-CURRENT r292595 on ThinkPad T430 (i7-3520M, Intel video 4000). Today I tried to update to a fresher version. Something has been broken somewhere between r296485 and r297692, I

Re: i915kms broken at some commit between r296485 and r297692?

On 05/09/16 04:34, Sergey Manucharian wrote: I'm running FreeBSD 11.0-CURRENT r292595 on ThinkPad T430 (i7-3520M, Intel video 4000). Today I tried to update to a fresher version. Something has been broken somewhere between r296485 and r297692, I suspect namely i915kms - it won't boot: at the

Re: r299215: buildkernel fails due to error: declaration of 'struct cpl_set_tcb_rpl' (cxgbe)

On Sat, 7 May 2016 12:55:32 +0200 "O. Hartmann" wrote: > On CURRENT (r 299215), buildkernel fails due to an error in cxgbe: > > [...] > In file included > from /usr/src/sys/modules/cxgbe/iw_cxgbe/../../../dev/cxgbe/iw_cxgbe/cm.c:62: >

Re: NO_INSTALLEXTRAKERNELS and PkgBase

I don't really know what to quote here, but the documentation is not clear. There ought to be something in UPDATING. Issue is building and installing more than one kernel. I tried once, and it didn't work right. I had to go back to one kernel at a time and NO_MODULES=yes on second and

plockstat

Is plockstat supposed to work on FreeBSD? I'm running FreeBSD-current and when I try it, I get: plockstat: failed to compile program: probe description plockstat65047:::rw-block does not match any probes Any ideas what to try next? ___