Re: i386 update to latest -HEAD broke things

2013-11-24 Thread Ilya Bakulin
On 22.11.13 11:49, Dimitry Andric wrote: On 22 Nov 2013, at 04:23, Adrian Chadd adr...@freebsd.org wrote: I just updated a laptop from a month old -HEAD to the latest -HEAD. Things .. didn't work. * No processes ran - they'd complain about being out of anonymous memory * /rescue/sh works

Re: i386 update to latest -HEAD broke things

2013-11-22 Thread Adrian Chadd
r258446 built, installed and booted fine. I'll try a more recent i386 in a chroot soon. Would someone please double-check -HEAD on i386 and see if it's ok? Thanks, -adrian On 21 November 2013 19:23, Adrian Chadd adr...@freebsd.org wrote: hi, I just updated a laptop from a month old -HEAD

Re: i386 update to latest -HEAD broke things

2013-11-22 Thread Andreas Tobler
- Original Message From: Adrian Chadd adr...@freebsd.org To: freebsd-current freebsd-current@freebsd.org Subject: Re: i386 update to latest -HEAD broke things Date: 22/11/13 10:05 r258446 built, installed and booted fine. I'll try a more recent i386 in a chroot soon. Would

Re: i386 update to latest -HEAD broke things

2013-11-22 Thread Adrian Chadd
On 22 November 2013 01:11, Andreas Tobler andreast-l...@fgznet.ch wrote: - Original Message From: Adrian Chadd adr...@freebsd.org To: freebsd-current freebsd-current@freebsd.org Subject: Re: i386 update to latest -HEAD broke things Date: 22/11/13 10:05 r258446 built

Re: i386 update to latest -HEAD broke things

2013-11-22 Thread Dimitry Andric
On 22 Nov 2013, at 04:23, Adrian Chadd adr...@freebsd.org wrote: I just updated a laptop from a month old -HEAD to the latest -HEAD. Things .. didn't work. * No processes ran - they'd complain about being out of anonymous memory * /rescue/sh works fine, but /rescue/dhclient seems to be doing

i386 update to latest -HEAD broke things

2013-11-21 Thread Adrian Chadd
hi, I just updated a laptop from a month old -HEAD to the latest -HEAD. Things .. didn't work. * No processes ran - they'd complain about being out of anonymous memory * /rescue/sh works fine, but /rescue/dhclient seems to be doing the wrong thing with regards to which dhclient-script it calls *