From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) From: "Fran. J Ballesteros" In-Reply-To: Date: Wed, 2 May 2018 19:24:29 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: 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> To: Giacomo Tesio Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] 9n Topicbox-Message-UUID: d55b9408-ead9-11e9-9d60-3106f5b1d025 I just learned to love absolute paths. IIRC, there was no deadlock caused that you should be aware of. I'ts been a long time and quite a few protocols since then, I can look = for the source; there must be also some docs in the web. Also, I'm more in favor of prefix mount tables, that they are very = different from what 9 does and they would lead to a very different = system. Good luck and have fun. > On 2 May 2018, at 19:14, Giacomo Tesio wrote: >=20 > 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. >=20 > Here I am, finally! :-) >=20 > 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. >=20 > 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. >=20 > 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. >=20 > =20 > Don't you have a tricorder? >=20 > No... but usually I can get away with my sonic screwdriver... :-) >=20 >=20 > Giacomo >=20