Wotcha Gang!
In my travels through the arm64 GENERIC config file I came across the option
‘INTRNG’, and wondered what it was:
INTeRrupt Next Generation?
INTeger Random Number Generator?
IN TRaiNinG?
INTerrupt Random Number Generator?
INdependent TRaiNinG?
So, please put me out of my misery, wha
On Thu, Feb 22, 2018 at 8:34 PM, O. Hartmann wrote:
> Mateusz provided me with this patch, which solved the issue:
>
> Index: sys/kern/vfs_bio.c
> ===
> --- sys/kern/vfs_bio.c (revision 329832)
> +++ sys/kern/vfs_bio.c (working cop
Am Thu, 22 Feb 2018 19:56:26 +0100
"O. Hartmann" schrieb:
> Am Thu, 22 Feb 2018 10:53:46 -0700
> Ian Lepore schrieb:
>
> > On Thu, 2018-02-22 at 18:41 +0100, O. Hartmann wrote:
> > > Am Wed, 21 Feb 2018 20:05:24 +0100
> > > "O. Hartmann" schrieb:
> > >
> > > >
> > > > On CURRENT ( 12.0
Am Thu, 22 Feb 2018 10:53:46 -0700
Ian Lepore schrieb:
> On Thu, 2018-02-22 at 18:41 +0100, O. Hartmann wrote:
> > Am Wed, 21 Feb 2018 20:05:24 +0100
> > "O. Hartmann" schrieb:
> >
> > >
> > > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue
> > > Feb 20 23:06:15 CET
> > > 20
On Thu, 2018-02-22 at 18:41 +0100, O. Hartmann wrote:
> Am Wed, 21 Feb 2018 20:05:24 +0100
> "O. Hartmann" schrieb:
>
> >
> > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue
> > Feb 20 23:06:15 CET
> > 2018 amd64) I'm honored by this nice bug when calling top:
> >
> > top: sysc
On Thu, Feb 22, 2018 at 6:41 PM, O. Hartmann wrote:
> Am Wed, 21 Feb 2018 20:05:24 +0100
> "O. Hartmann" schrieb:
>
> > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue Feb 20
> 23:06:15 CET
> > 2018 amd64) I'm honored by this nice bug when calling top:
> >
> > top: sysctl(vfs.bu
Am Wed, 21 Feb 2018 20:05:24 +0100
"O. Hartmann" schrieb:
> On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue Feb 20
> 23:06:15 CET
> 2018 amd64) I'm honored by this nice bug when calling top:
>
> top: sysctl(vfs.bufspace...) expected 8, got 4
>
>
> Regards,
>
> oh
I still ca
On Thu, Feb 22, 2018 at 8:39 AM, Alan Somers wrote:
> I have two FreeBSD 12-CURRENT amd64 systems that both refuse to install
> any new packages. "pkg update -f" doesn't help. When I try, I get a
> confusing error like this.
>
> $ sudo pkg update -f
> Updating FreeBSD repository catalogue...
>
I have two FreeBSD 12-CURRENT amd64 systems that both refuse to install any
new packages. "pkg update -f" doesn't help. When I try, I get a confusing
error like this.
$ sudo pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B 0.9kB/s00:01
Fetching packag
On Thu, 22 Feb 2018 09:26:20 +0100
Gary Jennejohn wrote:
> On Thu, 22 Feb 2018 08:37:07 +0100
> "O. Hartmann" wrote:
>
> > On Tue, 20 Feb 2018 12:39:53 +0100
> > Gary Jennejohn wrote:
> >
> > > On Mon, 19 Feb 2018 14:18:15 -0800
> > > "Chris H" wrote:
> > >
> > > > I'm seeing a number
> On Thu, 22 Feb 2018 08:37:07 +0100
> "O. Hartmann" wrote:
>
> > On Tue, 20 Feb 2018 12:39:53 +0100
> > Gary Jennejohn wrote:
> >
> > > On Mon, 19 Feb 2018 14:18:15 -0800
> > > "Chris H" wrote:
> > >
> > > > I'm seeing a number of messages like the following:
> > > > kernel: failed: cg 5,
On Thu, Feb 22, 2018 at 03:10:17AM -0800, Jack L. wrote:
maybe try a clean buildworld, update /usr/src to the latest version, rm -rf
/usr/obj, then make buildworld && make installworld && make kernel and see
if that fixes the issue?
Is there a documented way of say booting to memstick, starting
On Thu, 22 Feb 2018, at 03:51, Le Baron d’Merde wrote:
> Dear Fellows,
>
> Nothing new and probably will not be implemented, specially by me who
> can't write code, but I am sharing this idea anyway.
>
> The point would be to have a P2P core/daemon in Base with some API to be
> used by clients,
On Wed, 21 Feb 2018 22:22:08 +0800
Julian Elischer wrote:
> On 21/2/18 7:14 pm, Tomoaki AOKI wrote:
> > Hi.
> >
> > +1. But have one suggestion for format.
> > Something like
> >
> > Broken by: rXXX
> > Broken by: Unknown (Bugfix but the revision introduced it is unknown)
> >
> > and opti
Hi, thanks for responding
On Thu, 22 Feb 2018, at 11:10, Jack L. wrote:
> maybe try a clean buildworld, update /usr/src to the latest version, rm -rf
> /usr/obj, then make buildworld && make installworld && make kernel and see
> if that fixes the issue?
I booted to the old kernel as it's apparent
maybe try a clean buildworld, update /usr/src to the latest version, rm -rf
/usr/obj, then make buildworld && make installworld && make kernel and see
if that fixes the issue?
On Thu, Feb 22, 2018 at 2:57 AM, John wrote:
> Hello,
>
> When trying to upgrade from 11-stable to 12-current, make inst
Hello,
When trying to upgrade from 11-stable to 12-current, make installworld broke.
The OS is mainly on a ssd, there is zfs installed (usr/src is on zfs). Is there
a guide somewhere that shows how to recover from this situation? both 11.1 and
12-current kernels are bootable. I can just blat th
When trying to build the kernel, I get:
--- all_subdir_linux ---
/usr/src/sys/amd64/linux32/linux32_dummy.c:1:5: error: unknown type name
'sys'
--- linux_fork.o ---
ctfconvert -L VERSION -g linux_fork.o
--- nsprepkg.o ---
cc -target x86_64-unknown-freebsd12.0
--sysroot=/usr/obj/usr/src/amd64.amd64
On Thu, 22 Feb 2018 08:37:07 +0100
"O. Hartmann" wrote:
> On Tue, 20 Feb 2018 12:39:53 +0100
> Gary Jennejohn wrote:
>
> > On Mon, 19 Feb 2018 14:18:15 -0800
> > "Chris H" wrote:
> >
> > > I'm seeing a number of messages like the following:
> > > kernel: failed: cg 5, cgp: 0xd11ecd0d != bp:
19 matches
Mail list logo
