Date: Fri, 14 Jan 2011 09:58:14 -0700 From: Warner Losh <imp@bsdimp.com> To: freebsd-hackers@FreeBSD.org Subject: Re: best way to run -RELEASE and -CURRENT on the same machine Message-ID: <4D3080A6.6010704@bsdimp.com> In-Reply-To: <AANLkTin-SQTT8fxgGBcgLkNK8GE6NbyTkKdm27ykxCK5@mail.gmail.com> References: <AANLkTin-SQTT8fxgGBcgLkNK8GE6NbyTkKdm27ykxCK5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/14/2011 03:19, Aryeh Friedman wrote: > My normal work doesn't require -CURRENT but the stuff I need to do > Android development only works on -CURRENT the problem I only have one > machine and want to make it so I can run 8.2-RC1 for most everyday > things but can switch to -CURRENT when I do Android work.... Obviously > I would like to make it so my ports are also build for both machines > everytime I run portmaster (or the equiv)... dual boot or jail or > what?.... note that -CURRENT currently is unusable due to active > refactoring of the interrupt handling and my NIC (ale(4)) causing a > panic when it goes from down to up I'd be tempted to run a -current jail inside of an 8.x base system. That's not supported, but would likely work. An even better idea might be to run a -current system inside a VirtualBox container. This would allow you to run it at full speed, but insulate your primary system if there's bad things going on with -current this week. I do a lot of FreeBSD development inside of VirtualBox. It is quite nice that way. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D3080A6.6010704>