from my point of view, what is lacking in NIX is that it's not integrated into a living code base, rather it is its own thing. That means it can not take advantage of the last 14 years of plan 9 improvements and bug fixes.
Paul has done excellent work pulling it into 9front and I've tried to build on it, see https://github.com/rminnich/9front/tree/ron_nix I am not sure we need a list, maybe we do, but NIX is very, very simple, by design, and I think what's more important is to dig into the code and get it going. I think we're within a month or maybe sooner of having the NIX based on 9front working as NIX used to work. I'm following the rule that, for every change, the kernel must build and boot. I am not at the point where we can enable an AC, but we're getting there. It would be very useful if you can take a look at the code and understand, for example, what tcore.c and acore.c are doing, and where I've messed up pulling that code over. Also I'm still not completely understanding how 9 front does startup IPI -- we added SIPI in nix, vector 62, but I don't see that in 9front. I added VectorSIPI to pc/io.h, but maybe that's a botch. This means staring at code, and it's a real grind, but there's just about no other way to do it. In particular, the path in acmmuswitch needs more eyes. On Sun, Feb 2, 2025 at 4:16 PM Cody Holliday <cody.parker.holli...@gmail.com> wrote: > Hello everyone, > > I created an issue on the GitHub but I figure using the mailing list was > more the projects speed. > > Is there already a list of things to do? Shall we maintain a file to track > tasks needing to be completed? > > I would like to at least be able get a handle on what is still lacking in > NIX. > > Hope you all had a good Groundhog Day! > Cody ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T7e645b96f1f70c95-M08b40f86dec00baef6650b24 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
