Date: Mon, 6 Mar 2017 16:02:18 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Karl Denninger <karl@denninger.net> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: Booting an old kernel on RPI2 Message-ID: <20170307000218.GA20241@www.zefox.net> In-Reply-To: <a7d62207-91b7-107b-1e09-96651871eafb@denninger.net> References: <20170304165740.GA9625@www.zefox.net> <E1ckory-004k8U-Sq@smtp.hs-karlsruhe.de> <20170306163005.GB19195@www.zefox.net> <1488818491.18764.21.camel@freebsd.org> <20170306170241.GC19195@www.zefox.net> <a7d62207-91b7-107b-1e09-96651871eafb@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 06, 2017 at 11:06:39AM -0600, Karl Denninger wrote: > I can build working 11-STABLE images for the RPI2 using Crochet, and Is there some intrinsic advantage to using Crochet for a self-hosted build (apart from the fact that make memstick in /usr/src/release seems to be broken)? My only tested Crochet installation is on an X86 box running 10.something that hasn't been plugged in for over a year. It'll take at least a little work to proceed in either case. If a small (or at least enumerable) list of binaries could be copied onto the damaged filesystem from a running RPI2 that would be easiest, I think... Thanks for reading! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170307000218.GA20241>