Re: FreshPorts, pkg query and pkg rquery: versions of dependencies

Graham Perrin writes: > devel/icu for example. > > On Mon, 29 Oct 2018 at 04:13, I wrote: > >> Waterfox: downgrading to icu-62.1_2,1 and rebuilding consumers > >> … >> specifies icu>=59.1,1 so I'm probably OK there … > > I say

Re: Waterfox: downgrading to icu-62.1_2,1 and rebuilding consumers

On Mon, 29 Oct 2018 at 04:36, Jan Beich wrote: > Graham Perrin writes: > > > - is this DEFAULT_VERSIONS= line correct/sufficient for > > Thunderbird etc. to be built with the inferior version of icu? > > > > DEFAULT_VERSIONS= icu=62.1_2,1 > > Only one icu version is supported in the ports

Re: Waterfox: downgrading to icu-62.1_2,1 and rebuilding consumers

Graham Perrin writes: > - is this DEFAULT_VERSIONS= line correct/sufficient for > Thunderbird etc. to be built with the inferior version of icu? > > DEFAULT_VERSIONS= icu=62.1_2,1 Only one icu version is supported in the ports tree, so the above is nop. The ports are built against whatever

FreshPorts, pkg query and pkg rquery: versions of dependencies

devel/icu for example. On Mon, 29 Oct 2018 at 04:13, I wrote: > Waterfox: downgrading to icu-62.1_2,1 and rebuilding consumers > … > specifies icu>=59.1,1 so I'm probably OK there … I say "probably" because I'm not sure how to

Waterfox: downgrading to icu-62.1_2,1 and rebuilding consumers

Thanks, people! devel/icu was the hint that I needed. On Sun, 28 Oct 2018 at 23:26, Jan Beich wrote: > … Either rebuild www/waterfox from the last revision before removal or > downgrade devel/icu to 62.1 if nothing else requires 63.1. In the former > case you can also update the port (adjust

Re: 12.0-BETA1 vnet with pf firewall

On 28 Oct 2018, at 14:39, Rodney W. Grimes wrote: Bjoern A. Zeeb wrote: On 28 Oct 2018, at 15:31, Ernie Luzar wrote: Tested with host running ipfilter and vnet running pf. Tried loading pf from host console or from vnet console using kldload pf.ko command and get this error message;

Re: Waterfox: shared object "libicui18n.so.62" not found, required by "libxul.so"

Graham Perrin writes: > $ waterfox > XPCOMGlueLoad error for file /usr/local/lib/waterfox/libxul.so: > Shared object "libicui18n.so.62" not found, required by "libxul.so" > Couldn't load XPCOM. devel/icu major updates aren't ABI-compatible, so each update requires rebuilding every consumer.

Re: Waterfox: shared object "libicui18n.so.62" not found, required by "libxul.so"

On Sun, Oct 28, 2018 at 10:33:31PM +, Graham Perrin wrote: > $ waterfox > XPCOMGlueLoad error for file /usr/local/lib/waterfox/libxul.so: > Shared object "libicui18n.so.62" not found, required by "libxul.so" > Couldn't load XPCOM. > $ date ; uname -v > Sun 28 Oct 2018 22:31:00 GMT > FreeBSD

Waterfox: shared object "libicui18n.so.62" not found, required by "libxul.so"

$ waterfox XPCOMGlueLoad error for file /usr/local/lib/waterfox/libxul.so: Shared object "libicui18n.so.62" not found, required by "libxul.so" Couldn't load XPCOM. $ date ; uname -v Sun 28 Oct 2018 22:31:00 GMT FreeBSD 13.0-CURRENT r339737 GENERIC-NODEBUG $ Is there any easy-ish way to work

Re: 12.0-BETA1 vnet with pf firewall

W dniu 28.10.2018 o 22:39, Rodney W. Grimes pisze: >> Bjoern A. Zeeb wrote: >>> On 28 Oct 2018, at 15:31, Ernie Luzar wrote: >>> Tested with host running ipfilter and vnet running pf. Tried loading pf from host console or from vnet console using kldload pf.ko command and get this

Re: 12.0-BETA1 vnet with pf firewall

> Bjoern A. Zeeb wrote: > > On 28 Oct 2018, at 15:31, Ernie Luzar wrote: > > > >> Tested with host running ipfilter and vnet running pf. Tried loading > >> pf from host console or from vnet console using kldload pf.ko command > >> and get this error message; > >> > >> linker_load_file:

Re: 12.0-BETA1 vnet with pf firewall

> On 28 Oct 2018, at 12:56, Ernie Luzar wrote: > > Bjoern A. Zeeb wrote: >>> On 28 Oct 2018, at 15:31, Ernie Luzar wrote: >>> Tested with host running ipfilter and vnet running pf. Tried loading pf >>> from host console or from vnet console using kldload pf.ko command and get >>> this error

Re: 12.0-BETA1 vnet with pf firewall

Bjoern A. Zeeb wrote: On 28 Oct 2018, at 15:31, Ernie Luzar wrote: Tested with host running ipfilter and vnet running pf. Tried loading pf from host console or from vnet console using kldload pf.ko command and get this error message; linker_load_file: /boot/kernel/pf.ko-unsupported file

Re: UEFI boot hangs after loader

Warner Losh wrote: > On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > >> Jung-uk Kim wrote: >>> On 18. 10. 24., Warner Losh wrote: On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > gryphon# efivar -N --hex $(efivar | grep Boot0002) > : 01 00 00 00 98 00 55 00 45 00

Re: UEFI boot hangs after loader

The patch you emailed fixed it for me ... was there something else I've missed ? On 28 October 2018 at 16:40, Warner Losh wrote: > > > On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > >> Jung-uk Kim wrote: >> > On 18. 10. 24., Warner Losh wrote: >> >> On Wed, Oct 24, 2018 at 10:33 AM Harry

Re: UEFI boot hangs after loader

On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > Jung-uk Kim wrote: > > On 18. 10. 24., Warner Losh wrote: > >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> > >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >>> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > >>>

Re: UEFI boot hangs after loader

Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: >> >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) >>> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >>> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >>> 0020:

Re: 12.0-BETA1 vnet with pf firewall

On 28 Oct 2018, at 15:31, Ernie Luzar wrote: Tested with host running ipfilter and vnet running pf. Tried loading pf from host console or from vnet console using kldload pf.ko command and get this error message; linker_load_file: /boot/kernel/pf.ko-unsupported file type. Looks like the 12.0

Re: "arc4random: no preloaded entropy cache" printed once per CPU on startup

On Sat, 27 Oct 2018 16:38:00 -0600 Rebecca Cran wrote: > 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

12.0-BETA1 vnet with pf firewall

Tested with host running ipfilter and vnet running pf. Tried loading pf from host console or from vnet console using kldload pf.ko command and get this error message; linker_load_file: /boot/kernel/pf.ko-unsupported file type. Looks like the 12.0 version of pf which is suppose to work in vnet

12.0-BETA1 vt console with rc.conf blanktime, screensaver or loader.conf splash screen not working.

blanktime, screensaver has no effect on vt console. splash screen has no effect on vt console. no messages of any kind issued. They all work on sc console. ___ freebsd-current@freebsd.org mailing list

Re: UFS panics

On 10/27/18 5:34 PM, Leandro wrote: I just wanted to confirm if panics on UFS were expected if the file system had errors This is no official answer, but yes, basing on my nearly 20 years of experience with UFS, I've come to expect them. Several times after some boxes of mine crashed, they

Re: Facing kernel panic during early boot from 12.0 ALPHA9

Thanks Mark. On Sat, Oct 27, 2018 at 12:29 AM Mark Johnston wrote: > On Fri, Oct 26, 2018 at 07:35:14PM +0530, Rajesh Kumar wrote: > > Hi Mark, > > > > Thanks for the inputs. With the two patches you pointed out, I could able > > to compile from current, install and boot properly without any