Date: Mon, 09 Jun 2008 21:11:02 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Marko Zec <zec@fer.hr> Cc: freebsd-current@freebsd.org, Julian Elischer <julian@elischer.org>, freebsd-virtualization@freebsd.org, FreeBSD Current <current@freebsd.org> Subject: Re: kinda headsup.. Message-ID: <484D8046.7020403@FreeBSD.org> In-Reply-To: <200806092046.02847.zec@fer.hr> References: <484CC690.9020303@elischer.org> <484CFE6E.7040305@FreeBSD.org> <200806092046.02847.zec@fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
Marko Zec wrote: > On Monday 09 June 2008 11:57:02 Kris Kennaway wrote: >> Julian Elischer wrote: >>> At the BSDCAn devsummit we discussed how to proceed with committing >>> Vimage to -current. >>> >>> the Milestones included something like: >>> >>> June 8 (today) Headsup.... >>> >>> June 15 commit changes that add macros for vnet >>> (network module) and vinet(inet virtualisation) >>> with macros defined in such a way to make 0 actual >>> differences. provable by md5 etc. >>> Documentat >>> s/hostname/g//V_hostname/ >>> #define V_hostname hostname >>> 2 weeks settle time, next step prepared, tested >>> and reviewed. >> ... >> >>> diffs can be found at: >>> http://www.freebsd.org/~julian/vimage.diff and it are usually >>> fairly up to date. >> Did Marko fix the panic I saw back in May? I wasn't even able to >> boot a vimage kernel yet, let alone begin testing it :) > > I just submitted a p4 change that allows for a machine to boot with > rpc.lockd enabled, but haven't tested it with any NFS mounts yet. But > do you really need to have rpc.lockd running to be able to do any > testing? Probably not in an absolute sense, but it presumably is something that must be fixed anyway :) > Pls. note that the vimage branch tracking HEAD has other misterious > lockups that I haven't been able to track down yet. The > user/zec/vimage_7 branch is in much better shape... OK, I will wait until the HEAD branch is in good shape. Please let me know when I can start testing. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?484D8046.7020403>