On Fri, Mar 07, 2025 at 01:09:30PM -0600, Jacob Moody wrote:
> On 3/7/25 06:10, tlaro...@kergis.com wrote:
> > On Thu, Mar 06, 2025 at 03:47:42PM -0800, ron minnich wrote:
> >> thanks, Jacob.
> >> I'm going to keep at it, and your rebase has now made it much easier to
> >> keep up.
> >>
> >> In the usual manner of such things, I think now that we figured out that we
> >> can make it work, it's time to toss a lot of those commits away, and get to
> >> something a lot less messy. There's where others can help.
> >>
> >
> > May I ask why you didn't keep the small nix set of files that you (I
> > mean you Ron, and Paul) have finally selected?
> >
> > It seems to me that having, a la 9legacy (that has sys/src/9 and
> > sys/src/9k), a sys/src/nix, that is having a git repo just nix, with a
> > branch 9front (this flavor has just to be binded in 9front
> > sys/src/nix) and, why not, a 9legacy (this flavor has just to binded
> > in 9legacy sys/src/nix) would avoid the pain, for now, to have to
> > update when 9front is moving and will have the supplementary benefit
> > of showing what is Nix.
>
> The main issue is that nix is not self contained, presumably the nix kernel
> wants access to 9front's drivers, multiboot, nvme support etc.
Just for the sake of argument: This can be solved by the order of
binding or in the mkfiles, by explicit rules to select the correct
file when there are same filenames.
> [...]
> Also to be frank I would find it highly unlikely that a single repository
> would work for
> both 9legacy and 9front, [...]
This is not what I wrote: a Nix repository, with two distinct branches,
not the same, because there are indeed divergences. But in 9legacy,
there is also the "memory" of 9k, with evolutions about memory
allocation done after 2011 that need to be evaluated (and apparently,
Nemo has done work, after 2011, on memory allocation for
Nix too). So, later, there will have to be some weaving to be done,
with some jigsaw puzzles pieces scattered here and there to perhaps
put back in the picture.
Since it will take weeks before I can make any significant code
contributions to Nix (since I'm at the moment largely out of my
depth in the kernel aera), I will document things --- because I
have found it a great way to learn to "pretend teaching" a subject;
when trying to explain, questions arise about which you never
thought when simply reading an expos\'e and more than once something
I was about to describe as "obvious" with a waving hand was not
obvious at all, sometimes generally true but could in some contexts
be false, and even sometimes definitively wrong).
I will start from the subset isolated (due to the pace of Ron and
Paul, looong ago now; at least two weeks...), having the current
state as reference, but trying to get things working against 9legacy.
But using binds and explicit mkfile rules to reach the correct source
when there are same filenames between Nix and the host distribution.
The differences will be my Ariadne thread in the kernel maze. And I
expect it will be quite instructive to compare what is done
differently in the amended original 9legacy and in 9front.
--
Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tc82cdeb7e597b9d2-Mc1dcddff71083fc4077d6b8f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
