From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <92606a17ce255a2e74049e4090d948b3@proxima.alt.za> <36c5eca0f06e9acbe2fac19067f457d8@ladd.quanstro.net> <20140519195016.B21E6B827@mail.bitblocks.com> <3a6dcbf0845989d60e627ad4e5df4313@ladd.quanstro.net> <3A01CE35-B176-4A24-B3D4-24AB0874BB48@9srv.net> <1c303148ec8dc74c876330176c2fa54c@mikro.quanstro.net> <20140520183259.Horde.rnYhhqisRVn0pKfceYI5jw1@ssl.eumx.net> Date: Wed, 21 May 2014 12:23:34 +0200 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] syscall 53 Topicbox-Message-UUID: eabfe8cc-ead8-11e9-9d60-3106f5b1d025 On 5/20/14, ron minnich wrote: > Ah well, back to 'm' for this thread, and I now accept that this > community is unwilling to solve this simple problem, as so many others > have. Bummer. > > ron > > This is wrong. I've already solved the problem in my local tree by accident. Basically I've integrated a modified vc (I use an experimental 64bit MIPS here - provided by the chinese government during my internship) into systemd, which I ported to plan9 kernel space. When I boot the system and a syscall is found missing, the kernel simply recompiles itself (there is some heavy trickery involving clusters of neural networks in a fiber network to make that work) So even though this results from my other project as a byproduct, I'm happy to share it.