On a normal boot (not verbose) of -CURRENT from today's sources I'm
getting the following message printed once for each logical CPU:
arc4random: no preloaded entropy cache
Since other messages, including the same one in random_harvestq.c are
under bootverbose, should this one in arc4random.c
On 10/27/18 10:34 AM, Kyle Evans wrote:
Hmm... something's definitely amiss here- there's no reason this
should be munging through /usr/local/... at all- it's not in the
LUA_PATH. I'd be interested in knowing if there's anything funky about
your build or run setup- I have lua53 installed, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[ cross posted to several FreeBSD lists.
Please keep replies to x...@freebsd.org ]
Hi!
As some of you are aware, the X.org project posted a security advisory
on October 25 regarding a vulnerability in xorg-server [1].
This has been given the identi
On 10/27/18 11:00 PM, Niclas Zeising wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[ cross posted to several FreeBSD lists.
Please keep replies to x...@freebsd.org ]
Yes, I know the signature is BAD. GPG is as user friendly as always.
I'm about to re-send this with a (hopefully) go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[ cross posted to several FreeBSD lists.
Please keep replies to x...@freebsd.org ]
Hi!
As some of you are aware, the X.org project posted a security advisory
on October 25 regarding a vulnerability in xorg-server [1].
This has been given the identi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
One minor correction:
On Sat, Oct 27, 2018 at 05:03:48PM +, Glen Barber wrote:
> === SPECIAL NOTE ===
> This only affects systems that employ geli(4)-backed encrypted
> filesystems and currently running 11.x or 10.x. Upgrades from
> 12.0-BETA1,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The second BETA build of the 12.0-RELEASE release cycle is now
available.
Please see the "SPECIAL NOTE" below regarding upgrading from FreeBSD
10.x and 11.x for important information regarding geli(4)-backed
filesystems.
Also note, pkg(8) builds fo
On 27/10/2018 18:27, Glen Barber wrote:
>
Package builds are currently in progress (this will be noted in the
upcoming BETA2 announcement text I am currently drafting). It will be
about 48 hours, give or take, before binary packages from the repository
at pkg.freebsd.org are updated.
Thanks,
On Sat, Oct 27, 2018 at 10:49 AM Rebecca Cran wrote:
>
> When booting a recent 13-CURRENT installation, I’m seeing the following:
>
> Startup error in /boot/lua/loader.lua:
> LUA ERROR: /boot/lua/loader.lua:45: error loading module ‘local’ from file
> ‘/usr/local/lib/lua/5.3/local.so’:
> dynamic
On Sat, Oct 27, 2018 at 06:14:39PM +0200, David Marec wrote:
> On 09/10/2018 23:34, Glen Barber wrote:
> > OpenSSL has been updated to version 1.1.1 as of r339270.
> >
> > It is important to rebuild third-party packages before running:
> >
> > # make -C /usr/src delete-old && make -C /usr/src d
On 09/10/2018 23:34, Glen Barber wrote:
OpenSSL has been updated to version 1.1.1 as of r339270.
It is important to rebuild third-party packages before running:
# make -C /usr/src delete-old && make -C /usr/src delete-old-libs
I just do a fresh install a FreeBSD-12 from
http://ftp.freebs
When booting a recent 13-CURRENT installation, I’m seeing the following:
Startup error in /boot/lua/loader.lua:
LUA ERROR: /boot/lua/loader.lua:45: error loading module ‘local’ from file
‘/usr/local/lib/lua/5.3/local.so’:
dynamic libraries not enabled: check your Lua installation.
I then ha
Yes, I ran fsck in single user mode and it fixed some errors, one of
them was the entry that was causing the panic, that was removed.
I just wanted to confirm if panics on UFS were expected if the file
system had errors, that Sean and Kirk confirmed, or if it should be
investigated.
On Sat, Oct 27
Until it settles down, you can make your own build of ports-mgmt/pkg?
--
Markiyan
чт, 25 жовт. 2018 о 20:05 Pieper, Jeffrey E
пише:
> This was build this morning and includes:
>
> commit f37256a01fe12fe4d65128c82c6804d47dd511c1
> Author: kib
> Date: Thu Oct 25 13:37:57 2018 +
>
> Bum
Leandro wrote this message on Wed, Oct 24, 2018 at 12:22 -0300:
> I'm seeing a kernel panic when trying to move a specific file.
>
> panic: Bad effnlink fip 0xc004a2c69a00, fdp 0xc00497093be0,
> tdp 0xc004be6295a0
> cpuid = 72
> time = 1540283798
> KDB: stack backtrace:
> 0xe000adb
15 matches
Mail list logo
