On this note, 9front does have an arm64 qemu kernel which is designed
specifically to be
able to make use of the Hypervisor.framework available on modern macs and Linux
KVM.
The relevant pieces of the FQA are: https://fqa.9front.org/fqa3.html#3.3.1.1.1
This section also includes what is required
That name collision question re Nix-OS came up in 2011. I talked to
some folks, they more or less said "don't worry about the name", so I
decided not to.
The name NxM was intended to mean "N kernel cores, M application
cores" -- i.e. to be evocative of the NIX model. We probably could
have called
On Tue, 7 Jan 2025 at 04:24, Ben Huntsman wrote:
>
> So basically there's no getting 9vx to work on modern Mac OS (on Intel, I
> don't mean ARM)?
>
> That's truly unfortunate.
BoxedWINE exists and works, so I don't see that there can't be a "9pcemu".
And yes, "unfortunate" is right - drawterm e
Regarding the status of 9vx on macOS and m1, I would suggest an
alternative: use 9front or 9legacy with qemu. I use the 9legacy amd64
image with qemu on an M1 regularly and even that runs reasonably fast
for my taste.
In the last few hours I tried to bring up the 9pi4 kernel using
'qemu-system-aar
But what about the name collision with the other Nix OS?
On Mon, 6 Jan 2025 at 03:57, Ron Minnich wrote:
>
> I think it's ok to start with NIX, not NxM.
>
> On Sun, Jan 5, 2025 at 10:45 AM Stuart Morrow wrote:
> >
> > On Sun, 5 Jan 2025 at 16:39, Ron Minnich wrote:
> > > take that 2011 code, br
I had to use:
$ hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount 9legacy.rpi
Or the image wasn't recognized.
I tried a quick startup but just got a blank screen. I don't have much time to
take a look, but I'll do so later this evening.
Thanks for this.
--
Mat Kovach
m.
On Tue, Jan 07, 2025 at 09:20:06AM -0800, Ron Minnich wrote:
>
> Why NIX?
>
> If you think about it, timesharing is designed for a world where cores
> are scarce. But on a machine with hundreds of cores, running Plan 9,
> there are < 100 processes. We can assign a core to each process, and
> let
I found the original 2011 paper, which was a sandia report, from may
2011. It's a modification of the original proposal, which I no longer
have; but it is a good summary of where we were at the end of my visit
in May.
This is interesting: "We have changed a surprisingly small amount of
code at thi
As you say, Ron.
First, here's my nix script, such as it is, cribbed from the old nix one.
It has holes, guaranteed. Also, I went and pulled in a "user" directory,
just for old habits dying hard. Yes, I still use glenda on this old
terminal. Call me names for it.
#!/bin/rc
unmount /sys/includ
so for work like this, my motto is commit early, commit often, to a
branch we can always drop later. no harm. It's easier (for me anyway)
than shuffling patches around in email.
I'm happy to accept a pull request against rminnich/nix-os, , let's
call the branch regen.
thanks
On Tue, Jan 7, 2025
Ok, not a bad first day poking at it. I have a growing (but not ready) new
nix script to pull the right pieces over top of my build environment.
I have a near-complete build, but with hazards: 9front has evolved in a
number of places with many ulong parameters becoming usize. I have a list
of tho
And a bit more digging. Yes, I'm clearly doing this wrong. In building
nix-os/sys/src/k10/trap.c it should absolutely be using the Tos structure
from nix, not the one in the host system.
How do I re-root this correctly for this build?
Paul
On Tue, Jan 7, 2025 at 4:47 PM Paul Lalonde
wrote:
>
if you look at the first_commit branch, you'll see a sys/src/nix/nix
script, which sets up some binds.
What we did, before building nix, on plan 9, in 2011, was a set of
binds to get the right things such as /sys/include and so on.
This won't be just a 'mk and it builds'. There's 13 years of bit
if you can document your steps, then others can stand on your
shoulders, possibly, and we can all move forward?
On Tue, Jan 7, 2025 at 9:08 PM Paul Lalonde wrote:
>
> Ok, not a bad first day poking at it. I have a growing (but not ready) new
> nix script to pull the right pieces over top of my
Ok, I thought, what could do.
So I went to my rPi 400, set up SSH for github, got Ron's nix-os repo and
hit "mk".
When that errored out a bunch I realized that I needed /amd64 built, so I
did that. Just as painless as I remembered.
And now, I get a ways further into the build, but hit an incompa
15 matches
Mail list logo
