Date: Thu, 20 Jun 2013 04:50:39 -0400 From: Super Bisquit <superbisquit@gmail.com> To: Alexey Dokuchaev <danfe@nsu.ru> Cc: current@freebsd.org Subject: Re: Updating from 9.1-release to svn head: what might be the problem? Message-ID: <CA%2BWntOujz_RpENuoep%2BsrMWJ1Y4Sq8W8vgY3-RzKYxuKrNWvnA@mail.gmail.com> In-Reply-To: <20130620025155.GA61863@regency.nsu.ru> References: <20130618152133.GA20222@regency.nsu.ru> <20130620025155.GA61863@regency.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
I've been using 10.0 current for a few months now with no problem. What I do know about virtual machines is that they don't share kernel resources too well. If both virtual machines are trying to access the kernel, there will be a problem. On Wed, Jun 19, 2013 at 10:51 PM, Alexey Dokuchaev <danfe@nsu.ru> wrote: > On Tue, Jun 18, 2013 at 10:21:33PM +0700, Alexey Dokuchaev wrote: > > I've been trying to install fresh -CURRENT (in VirtualBox/i386), and > since > > recent snapshots did not work for me, had to do this by first installing > > from 9.1-release .iso. After "svn co .../head /usr/src" and standard > make > > world/kernel/mergemaster procedure (w/out any custom settings in > make.conf > > or src.conf), I apparently keep getting screwed up system [...] > > It's getting strange: colleague at $work convinced me to try VMware Player, > and I reluctantly agreed... Well, with that thing I managed to install > Marchish -CURRENT snapshot, successfully rebuild the world, and now > building > my ports... So I'm puzzled: is it my hands, broken 9.1 -> 10.0 upgrade, or > some VirtualBox vs. VMplayer issue?.. > > ./danfe > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOujz_RpENuoep%2BsrMWJ1Y4Sq8W8vgY3-RzKYxuKrNWvnA>