I agree with (1), vmx is not ready for nix yet.
as for (2), I'll take a slight change: the goal is to remove nix as an
independent entity, and subsume it in other plan 9 kernels (I prefer 9front
at this point)
Big picture, NIX could be a build option for 9front, or a branch in 9front;
something li
It seems to me that the best course, for now, is the following:
1) [Using qemu or booting the kernel on baremetal] Try and correct
Nix, in its present state, to achieve a running Nix, with 9front, for
objtype==amd64;
2) Once 1) is achieved, start cleaning (then, at this moment, the mps
stuff coul
On 1/28/25 15:49, Skip Tavakkolian wrote:
> I stumbled onto this today and it made me chuckle. Performance isn't bad at
> all.
>
> https://copy.sh/v86/?profile=9front
>
> It might be interesting to have a Plan 9 server on the backend to
> import the '#l' from and to boot the term with user crede
I think it would be pretty easy to follow the pattern of including nix
conditionally in a conf file so you would have instead of pc64 , nixpc64.
I’m already doing that with my VM threads kernel — It’s an unchanged kernel
with just two additional lines to add a new device and support code.
There’s
On Wed, Jan 29, 2025 at 07:14:10AM -0800, ron minnich wrote:
> I agree with (1), vmx is not ready for nix yet.
> as for (2), I'll take a slight change: the goal is to remove nix as an
> independent entity, and subsume it in other plan 9 kernels (I prefer 9front
> at this point)
>
> Big picture, NI
Thank you. It looks like it has been rolled out already.
Another amusing find, the Windows 2000 image on the site includes
Inferno. Turtles all the way down, indeed.
On Wed, Jan 29, 2025 at 8:05 AM Jacob Moody wrote:
>
> On 1/28/25 15:49, Skip Tavakkolian wrote:
> > I stumbled onto this today an
