On 10 May 2016 at 08:32, Glen Barber wrote:
> On Tue, May 10, 2016 at 08:25:22AM +0200, Thomas Zander wrote:
>> On 10 May 2016 at 08:18, O. Hartmann wrote:
>>
>> > I haven't figured out so far how far this goes. Lucky for those having
>> > recent /etc/ backups. A pity FreeBSD doens't backup this
On Tue, May 10, 2016 at 02:38:36PM +0800, Marcelo Araujo wrote:
> 2016-05-10 14:32 GMT+08:00 Glen Barber :
>
> > On Tue, May 10, 2016 at 08:25:22AM +0200, Thomas Zander wrote:
> > > On 10 May 2016 at 08:18, O. Hartmann
> > wrote:
> > >
> > > > I haven't figured out so far how far this goes. Lucky
2016-05-10 14:32 GMT+08:00 Glen Barber :
> On Tue, May 10, 2016 at 08:25:22AM +0200, Thomas Zander wrote:
> > On 10 May 2016 at 08:18, O. Hartmann
> wrote:
> >
> > > I haven't figured out so far how far this goes. Lucky for those having
> > > recent /etc/ backups. A pity FreeBSD doens't backup th
On Tue, May 10, 2016 at 08:31:46AM +0200, O. Hartmann wrote:
> On Tue, 10 May 2016 06:24:36 + Glen Barber wrote:
> > The change (incorrectly) invoked the 'distribution' target, so anything
> > that gets "touched" by that will likely be affected.
>
> In my case, it is *EVERY* file located in /
On Tue, May 10, 2016 at 08:25:22AM +0200, Thomas Zander wrote:
> On 10 May 2016 at 08:18, O. Hartmann wrote:
>
> > I haven't figured out so far how far this goes. Lucky for those having
> > recent /etc/ backups. A pity FreeBSD doens't backup this by default.
>
> After having shot myself in the f
On Tue, 10 May 2016 06:24:36 +
Glen Barber wrote:
> On Tue, May 10, 2016 at 08:18:44AM +0200, O. Hartmann wrote:
> > On Tue, 10 May 2016 05:53:41 +
> > Glen Barber wrote:
> >
> > > Thanks to O. Hartmann promptly reporting this, it was discovered that
> > > 'installworld' on revisions
On 10 May 2016 at 08:18, O. Hartmann wrote:
> I haven't figured out so far how far this goes. Lucky for those having
> recent /etc/ backups. A pity FreeBSD doens't backup this by default.
After having shot myself in the foot some time ago, "zfs snapshot" has
become a part of my standard upgrade
On Tue, May 10, 2016 at 08:18:44AM +0200, O. Hartmann wrote:
> On Tue, 10 May 2016 05:53:41 +
> Glen Barber wrote:
>
> > Thanks to O. Hartmann promptly reporting this, it was discovered that
> > 'installworld' on revisions r299292-r299317 will silently replace
> > /etc/passwd, /etc/master.pas
On Tue, 10 May 2016 05:53:41 +
Glen Barber wrote:
> 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
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 /etc/mail/a
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 /var/b
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
> 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
>>> specific to powerpc64. It turns out to be due to r298004: the CCB
>>> a
* 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 cam_periph_devctl_notify() never gets freed. The patc
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
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 behaviour
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?
>
>
> Correct. At least,
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 something
I've used quite a bit
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
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 list trimmed a bit
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 20
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 susp
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 boot
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:
> /usr/src/sys/modules/cxgbe/iw_cxgbe/../../../dev/cxgbe/tom/t
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 subseq
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?
___
freebsd-current@f
26 matches
Mail list logo
