On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50 CEST
2020 amd64), /usr/src at revision 364907, installkernel fails now due
to an error as shown below. For the record, "options ZFS" ist
statically in the kernel config file.
Also deleting /usr/obj and restarting buildworld and bu
Can you show more of the log?
When you installkernel you should see:
mkdir -p /boot/kernel
install -p -m 555 -o root -g wheel kernel /boot/kernel/
mkdir -p /usr/lib/debug/boot/kernel
install -p -m 555 -o root -g wheel kernel.debug /usr/lib/debug/boot/kernel/
Did these succeed? Do these dirs exist
On Fri, 28 Aug 2020 12:31:21 +0200
Mateusz Guzik wrote:
> Can you show more of the log?
>
> When you installkernel you should see:
> mkdir -p /boot/kernel
> install -p -m 555 -o root -g wheel kernel /boot/kernel/
These lines are seen right after the beginning of "make installkernel".
> mkdir -
On 8/28/20, Hartmann, O. wrote:
> On Fri, 28 Aug 2020 12:31:21 +0200
> Mateusz Guzik wrote:
>
>> Can you show more of the log?
>>
>> When you installkernel you should see:
>> mkdir -p /boot/kernel
>> install -p -m 555 -o root -g wheel kernel /boot/kernel/
>
> These lines are seen right after the
Hi!
I run FreeBSD 13.0-CURRENT #0 r363772 as router in small office with two
network interface: sk0 and sk1.
sk0 connected to 2 providers (main and backup) via VLAN and natd, sk1
connected to office network via VLAN.
I had to use VLAN due to cabling issues.
As soon as the user runs the speedt
On 2020-08-28 08:02, S.N. Trigub wrote:
> Hi!
>
> I run FreeBSD 13.0-CURRENT #0 r363772 as router in small office with two
> network interface: sk0 and sk1.
> sk0 connected to 2 providers (main and backup) via VLAN and natd, sk1
> connected to office network via VLAN.
> I had to use VLAN due to ca
I just want to add a "me to" here.
With a recent upgrade of CURRENT on my laptop, these error messages started
popping up.
Possibly not really harming anything under the hood though.
Dries
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of
Greetings,
I'd like to retire the spkr driver. It was a cute hack before sound cards
were ubiquitous, but it's not been kept up to date, and it's not clear that
it still works It is still Giant locked, and though it's not a huge
effort to do the locking I literally have no way to test it that
> On 28 Aug 2020, at 17:25, Warner Losh wrote:
>
> Greetings,
Hi
> I'd like to retire the spkr driver. It was a cute hack before sound cards
> were ubiquitous, but it's not been kept up to date, and it's not clear that
> it still works It is still Giant locked, and though it's not a huge
>
On Thu, Aug 27, 2020 at 10:37 PM Yuri Pankov wrote:
>
> Matthew Macy wrote:
> > On Thu, Aug 27, 2020 at 6:34 PM Yuri Pankov wrote:
> >>
> >> Yet another issue I'm seeing after last update (currently running
> >> r364870), hit it 2 times today:
> >>
> >> Fatal trap 12: page fault while in kernel m
On 2020-08-28 09:25, Warner Losh wrote:
Greetings,
I'd like to retire the spkr driver. It was a cute hack before sound cards
were ubiquitous, but it's not been kept up to date, and it's not clear that
it still works It is still Giant locked, and though it's not a huge
effort to do the lockin
On Fri, Aug 28, 2020 at 01:32:06PM -0400, Michael Butler wrote:
> Is there any documentation around the changes to the release build
> system from SVN to GIT?
>
> I currently keep a mirrored SVN repo and the revised release scripts
> seem not to have that as a build option. Can I still use this or
On Fri, Aug 28, 2020 at 05:43:07PM +, Glen Barber wrote:
> On Fri, Aug 28, 2020 at 01:32:06PM -0400, Michael Butler wrote:
> > Is there any documentation around the changes to the release build
> > system from SVN to GIT?
> >
> > I currently keep a mirrored SVN repo and the revised release scr
Hi!
> I'd like to retire the spkr driver. It was a cute hack before sound cards
> were ubiquitous, but it's not been kept up to date, and it's not clear that
> it still works It is still Giant locked, and though it's not a huge
> effort to do the locking I literally have no way to test it that
On Fri, 28 Aug 2020 14:02:46 +0200, S.N. Trigub
wrote:
Hi!
I run FreeBSD 13.0-CURRENT #0 r363772 as router in small office with two
network interface: sk0 and sk1.
sk0 connected to 2 providers (main and backup) via VLAN and natd, sk1
connected to office network via VLAN.
I had to use VL
Hi,
> On 28 Aug 2020, at 19:47, Kurt Jaeger wrote:
>
> Hi!
>
>> I'd like to retire the spkr driver. It was a cute hack before sound cards
>> were ubiquitous, but it's not been kept up to date, and it's not clear that
>> it still works It is still Giant locked, and though it's not a huge
>>
Try updating. I think this may have been fixed in
https://github.com/openzfs/zfs/pull/10823 which was MFVed this
morning.
On Fri, Aug 28, 2020 at 9:49 AM Matthew Macy wrote:
>
> On Thu, Aug 27, 2020 at 10:37 PM Yuri Pankov wrote:
> >
> > Matthew Macy wrote:
> > > On Thu, Aug 27, 2020 at 6:34 PM
Is there any documentation around the changes to the release build
system from SVN to GIT?
I currently keep a mirrored SVN repo and the revised release scripts
seem not to have that as a build option. Can I still use this or do I
need to throw it all out and start over?
With one target machine be
Hi,
I’ve been seeing on both i386 and arm64 builds where I tested that
loading modules from loader will then fail by the kernel link in certain
situations. I’ve created an i386 example where I do load a few
modules from loader to show what I think the problem is.
You may notice in the examp
Poul-Henning Kamp wrote:
>Rick Macklem writes:
>> For the NFS over TLS work, I have a need for an Internet OID.
>> (I understand that IETF assigns ones for things like SNMP under
>> 1.3.6.1.4.1...)
>
>See:
>
>/usr/share/snmp/mibs/FREEBSD-MIB.txt
Is https://reviews.freebsd.org/D26225
suffici
Rick Macklem writes:
> Poul-Henning Kamp wrote:
> Is https://reviews.freebsd.org/D26225
> sufficient to allow me to use 1.3.6.1.4.1.2238.1.1.1 for a user@domain
> name in this otherName component of subjAltName in the X.509 cert?
> (I didn't list the UserName as the first item of the subt
21 matches
Mail list logo
