illumos-joyent

You're right, but there is signing of kernel and modules now, via secure boot, eg: https://access.redhat.com/documentation/en-US/Red_Hat_Enterp... I'm not sure about binaries in general - having secure boot as an anchor at least makes the exercise less futile - but there an interesting point brought up here: https://stackoverflow.com/questions/1732927/signed-executabl... Dynamic linker, dynamic libraries and dlopen. I see solaris has elfsign - and it appears to be in OpenSolaris too: https://github.com/joyent/illumos-joyent/blob/master/usr/src... Not sure if it would work on Linux - and you'd might want to prevent running unsigned binaries. Not sure if that's a thing on OpenSolaris. Still, being able to verify a binary might help with handling random downloads, I suppose.

> I read a lot of code too, which wasn’t always easy, but sometimes I was lucky enough to find myself treated to one of Robert’s epic block comments[0]. He wasn't exaggerating, that is an epic, beautiful, I would even say humbling block comment to read. It's completely outside of my regular knowledge domain but that is not at all required to appreciate it. [0] https://github.com/joyent/illumos-joyent/blob/dff0473c792fc5...

Wow -- there's a lot here! Just to unpack this a bit... First, there are a bunch of people that you might be unaware of doing important work in illumos and SmartOS (both at Joyent and in the broader community); I recommend taking a look at the actual repo[1], and some of the recent work we've done like LX-branded zones[2] and (more currently) bhyve.[3] Second, in terms of the engineering team at Joyent: yes, people have come and gone over the years -- but we've grown a bunch since the acquisition by Samsung, adding many engineers from a wide variety of backgrounds. Yes, this has included some ex-Sun folks (we have more ex-Sun now than at any time in our history, if that kind of thing matters to you), but (importantly to me, anyway) it's also included a bunch of people new to the system. These new engineers bring new perspectives and f

Thanks. This is the one I was thinking of, unchanged decades later: https://github.com/joyent/illumos-joyent/blob/master/usr/src... 200 pages before the pager starts running maybe made sense back then, needs to be rethought now. I'm reading the code to see if anyone other that UFS uses it. Something called UDFS does but that looks like DVDs, not that interesting.

Some of the LMXXX's yet remain: https://github.com/joyent/illumos-joyent/blob/master/usr/src...

They are far from abandoned. In fact they are used in production to power Triton cloud's docker emulation. In fact the latest LX-related commit was made 4 days ago (see the commit history of illumos-joyent linked below). https://github.com/joyent/sdc-docker https://github.com/joyent/triton https://github.com/joyent/illumos-joyent/commits/master

All of the bits with the exception of the customer-facing portal are already open-source: SmartOS: https://github.com/joyent/illumos-joyent and https://github.com/joyent/smartos-live Triton (the orchestration around it): https://github.com/joyent/triton - this is the root repository of the project, there are many services which are linked to here: https://github.com/joyent/triton/blob/master/docs/developer-...

You asked for an expert to correct you if you're wrong, so here it is: this is just completely wrong and entirely ignorant of both the capacity of the system and its history. On timers: we (I) added arbitrary resolution interval timers to the operating system in 1999[1] -- predating Linux by years. (We have had CPU binding and processor sets for even longer.) The operating system was and is being used in many real-time capacities (in both the financial and defense sectors in particular) -- and before "every single major financial exchange" was running Linux, many of them were running Solaris. [1] https://github.com/joyent/illumos-joyent/blob/master/usr/src...

> proprietary OS Say what? SmartOS is based on illumos, the only free, open source SVR4 UNIX out there. Get the code: https://github.com/joyent/illumos-joyent Build it! https://wiki.smartos.org/display/DOC/Building+SmartOS+on+Sma... Modify it: https://wiki.smartos.org/display/DOC/SmartOS+Developers+Guid...

Manta doesn't run on a proprietary OS, but runs on SmartOS, a distribution of illumos [1][2]. In fact, almost everything at Joyent is open source, including all of Manta [3]. As for why not anything else, Manta has been around since 2013 [4], before other similar solutions, and allows you to run arbitrary programs on your data. As an example, some of our customers run ffmpeg on videos that they upload, to produce different variants to then store in Manta. [1] https://github.com/joyent/smartos-live [2] https://github.com/joyent/illumos-joyent [3] https://github.com/joyent/manta [4] http://www.theregister.co.uk/2013/06/25/joyent_object_store/

DTrace has been doing this kind of things, in a safe and usable-in-production way, for years (and the code, while not trivial, is usually pretty cool to read): https://github.com/joyent/illumos-joyent/blob/master/usr/src...

Perhaps this is the support you need: https://github.com/joyent/illumos-joyent/commit/9ecc4732a583...

"Impossible" is a bit strong, but yes, it requires deep and unholy knowledge of the interpreter in the debugger. For an example of what this looks like, see some of the monster block comments in mdb_v8.c[1]. [1] https://github.com/joyent/illumos-joyent/blob/master/usr/src...

LZJB looks simpler and clearer: https://github.com/joyent/illumos-joyent/blob/master/usr/src...

TJ can provide examples from his perspective; my personal examples are all from keeping the node.js production debugging facilities[1][2] operating properly. We have tried hard to make these facilities independent from V8, but the reality is that they encode how V8 operates and that changes to V8 can break them. Fortunately, the node.js DTrace ustack helper[3] -- by far the more intricate piece -- hasn't needed major maintenance, but the facilities for iterating over all JavaScript objects from a core dump (for example) have been broken quite a few times. I'm afraid the war stories from debugging these aren't terribly heroic -- they boil down to one of the node.js debugging tests failing and Dave Pacheco or me (exactly which one frequently being adjudicated by fingers-on-noses) sitting down for several intense hours to learn how V8 has