Date: Thu, 28 Feb 2008 16:54:14 +0100 From: Marko Zec <zec@icir.org> To: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= <des@des.no> Cc: Julian Elischer <julian@elischer.org>, FreeBSD Current <current@freebsd.org> Subject: Re: warning of pending commit attempt. Message-ID: <200802281654.14726.zec@icir.org> In-Reply-To: <86zltlyuc2.fsf@ds4.des.no> References: <47C39948.3080907@elischer.org> <200802281531.28052.zec@icir.org> <86zltlyuc2.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 28 February 2008 16:27:41 Dag-Erling Sm=C3=B8rgrav wrote: > Marko Zec <zec@icir.org> writes: > > Actually the patch provides certain level of support for > > virtualizing leaf sysctl nodes. So far I have only introduced > > macros for methods / data types that I've found necessary to > > virtualize, such as SYSCTL_V_OID, SYSCTL_V_STRING, SYSCTL_V_INT, > > and SYSCTL_V_PROC. [...] > > Thanks, this is exactly what I was looking for. Now all we need is a > way to start a vimage with hw.machine and hw.machine_arch set to a > vimage-specific value... So your question opens up a pandora's box... Obviously it's trivial to=20 virtualize a sysctl, but I still don't have a clear idea on what would=20 be the most convenient way of specifying start-up constraints or=20 parameters when instatiating a new vimage. At the moment each=20 virtualized variable is initialized to some system-wide compiled in=20 constant - we need to come up with a much more flexible / configurable=20 model... Marko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802281654.14726.zec>