Date: Mon, 1 Mar 2010 11:35:55 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Martin McCormick <martin@dc.cis.okstate.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Remote Building of FreeBSD Message-ID: <6201873e1003010935q176765k6fbecebe3bc25fc0@mail.gmail.com> In-Reply-To: <201003011719.o21HJjdR015853@dc.cis.okstate.edu> References: <201003011719.o21HJjdR015853@dc.cis.okstate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 1, 2010 at 11:19 AM, Martin McCormick <martin@dc.cis.okstate.edu > wrote: > One can almost but not quite remotely build a FreeBSD system > using mfsbsd. The problem is that in order to install the > mfsboot.img data on the main boot drive, it is necessary to use > dd to write it there and a working system already has mounted > all partitions in the main drive. > > The systems I will be upgrading have 1 or more gigabytes > of RAM available so a memory disk could conceivably hold the > roughly 40-meg image that must be written to the boot sector of > the main drive. > > For this to work, one must unmount all main drive > partitions and still be able to do something like: > > dd if=mfsboot.img of=/dev/ad0 > > After that, the reboot will launch mfsbsd and the rest > appears to be manageable. > > Martin McCormick WB5AGZ Stillwater, OK > This seems to be similar to the depenguinator. http://www.daemonology.net/blog/2008-01-29-depenguinator-2.0.html Maybe there some approach in there to get you over the hump. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6201873e1003010935q176765k6fbecebe3bc25fc0>