From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <21D2CEA2-9FDB-4E1F-9BE5-3302BFF1325A@gmail.com> References: <4C33D9D9-6A99-43E0-A621-0D137564F441@lsub.org> <10DB3CE7-1903-4D06-8784-1416398302CE@lsub.org> <47813B77-1111-4199-8C51-726B55B39BB0@gmail.com> <108c856b42a813c1a5425ed4a4978387@ladd.quanstro.net> <20130617182056.GA1261@polynum.com> <20130617184019.GB54367@intma.in> <21D2CEA2-9FDB-4E1F-9BE5-3302BFF1325A@gmail.com> From: Giacomo Tesio Date: Wed, 2 May 2018 19:14:53 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>, "Fran. J Ballesteros" Content-Type: multipart/alternative; boundary="000000000000ba0edd056b3c3920" Subject: Re: [9fans] 9n Topicbox-Message-UUID: d54f9b94-ead9-11e9-9d60-3106f5b1d025 --000000000000ba0edd056b3c3920 Content-Type: text/plain; charset="UTF-8" 2013-06-17 21:06 GMT+02:00 Nemo : > You should ask if anyone else did that before doing it, instead of saying > they are un-spined life forms. > Here I am, finally! :-) I'm designing yet another file protocol for my toy/research os (whose kernel is derived from Charles Forsyth's Plan9-9k), and I'd like to give a look at your prior art. Some of my design decisions lead to a management of mount tables that is pretty similar to what you describe in your paper about the integration of 9P2000.ix. Given you already walked this path, I'd like to know what you have learnt and if you faced issues I should be aware. For example, the slight difference in bind semantics seems to reduce the risk of accidental loops in the namespace, but I would expect it would break related userspace assumptions. Also, resolving the dot of each process in the Pgrp each time a mount is done, seems pretty complex and prone to deadlocks. > Don't you have a tricorder? > No... but usually I can get away with my sonic screwdriver... :-) Giacomo --000000000000ba0edd056b3c3920 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2013-06-17 21:06 GMT+02:00 Nemo <nemo.mbox@gmail.com>:
You should ask if anyone else= did that before doing it, instead of saying
they are un-spined life forms.

Here I a= m, finally! :-)

I'm designing yet another file protoc= ol for my toy/research os (whose kernel is derived from=20 Charles Forsyth's Plan9-9k), and I'd like to give a look at your pr= ior art.

Some of my design decisions lead to a management= of mount tables that is=20 pretty similar=20 to what you describe in your paper about the integration of 9P2000.ix.
<= /div>

Given you already walked this path, I'd like t= o know what you have learnt and if you faced issues I should be aware.
<= /div>
For example, the slight difference in bind semantics seems to red= uce the risk of accidental loops in the namespace, but I would expect it wo= uld break related userspace assumptions.
Also, resolving the = dot of each process in the Pgrp each time a mount is done, seems pretty com= plex and prone to deadlocks.

=C2=A0
Don't you have a tricorder?

No... but usually = I can get away with my sonic screwdriver... :-)


Giaco= mo

--000000000000ba0edd056b3c3920--