oh I found a trove of information on the extra repo.

FYI: i also have a repo, you can access it if you are a lucky enough to live in the countries i allowed to access my domain : pkghost.extrowerk.com

that's not ominous-sounding at all.

Rogers Shaw in Canada appears barred, in any event.

I ban everything except 2 countries in the EU, sorry.

oddly both vague and specific

cursed guess: austerrich and hungary?

jclulow: Oh wonderful. Yes, I would really appreciate to get the "BE"-shared filesystems into OmniOS. This makes data live so much easier with minimal downsides.

I expect it

mostly belongs up in the common illumos bits

But yeah, I think it would be valubale

Just needs someone to work on it! (this could be you!)

well well well, I wrote a comment and offered to work on the definition and the testing. Currently no capacity to actually do programming. (not that I'm busy with cleaning up old BE that capture volatile data from cores, stale logsfiles, stale pkg cache :) )

I suspect the part in the middle where the feature actually gets implemented is probably the part we need the most to be honest

indeed :) but we are lucky, "someone else" has already proven the basic concept works well.

A bit of a sanity check. I wanna make a zone dedicated to just building binaries and have that that dataset exported out into other zones as readonly (and global too). Is that a good idea?

and how would it get exported? Noticed you can specify filesystems and datasets in zonecfg, alongside sharenfs on the dataset itself. So far I ain't managed to any to do it.

maybe a loopback mount could work

well, if you map in outside filesystems into a zone this is internally a loopback mount

<filesystem special="/path/outside/the/zone/on/host" directory="/path/inside/the/zone" type="lofs"> and add options=ro for the immutable mount in consuming zones

roger, I'll give that a try!