nomadlogic

yea as an ops engineer that's probably the worst violation of trust i've ever heard of.

I could see a use for both - using Lustre as a shared SAN for their flame/smoke/etc suites and using pNFS for workstation/render-node shared storage. at least that's how i've deployed things in the past.

i could see this replacing isilon (which is built on freebsd) for the later use-case :)

NVMe supports SR-IOV much in the same way that NICs do - which i suspect is how AWS is delivering "physical" NICs to VMs currently. So its a pretty safe bet that this is how NVMe devices are being delivered to guest Vm's.

thus spoke the manual nvme(4): "The nvme driver creates controller device nodes in the format /dev/nvmeX and namespace device nodes in the format /dev/nvmeXnsY."

it's been a while since i've had access to nvme gear but it "just worked" at the time - although my use case was for a a daemon that accessed the block device directly to do its own horrible things to it.

netbsd beat you to this by 5 years or so: https://blog.netbsd.org/tnf/entry/kernel_drivers_compiled_to...

"The Design and Implementation of the FreeBSD Operating System" not only does a great job at covering how the UFS filesystem is implemented, but also does a great job at explaining how and Unix systems are implemented. I highly recommend this book to anyone with an interest in Unix internals.

https://www.amazon.com/Design-Implementation-FreeBSD-Operati...

As another commenter mentions SCTP can be encapsulated if needed. SCTP is actually in pretty wide use in online gaming, and has been since at least 2007...

Can't believe it's been that long - whew. Here is an interesting counterpoint to this work by PHK:

http://queue.acm.org/detail.cfm?id=2349257

also i was unable to find a reference to the version/build of java the author was using - thus negating any numbers/benchmarks presented.

Seems to give more credence to: https://www.sudo.ws/todd/papers/strlcpy.html

Pretty sure that when you have to wadge a battle against obvious technology to justify your business model, your industry is going to end up on the wrong side of history.

These books are pretty much a must read for anyone interested in the internals of Unix-type systems. I keep them right next to my TCP/IP Illustrated volumes, I reckon it's always good to have good reference material handy - especially when it is well written and researched.

Trying not to be a curmudgeon - but I really don't see what the big fuss is about, or how docker is fundamentally changing anything.

Not to take anything away from docker being a decent tool in some circumstances - but really this methodology has been around in one implementation for ages on Unix platforms.

+1 from the systems engineer with over a decade experienceat cutting edge facilities - and a BA in philosophy (focused on recent continental thought, not logic). It comes down to the individual and their passion.

no just a self centered rich kid.

Well that explanation IMHO is just another argument as to how people in these positions have zero regard for shared spaces and others in general. I reckon the valleywag has a pretty funny response to that self serving article he wrote.

I'm not going to start a bikeshed over the technicalities covered in the coastal commission report though - my original point was how little regard many of these individuals have for others. And how no one should really be surprised that the technology community seems to represent the worst case examples of this.

Not sure why anyone would surprised about this. It's in the same mentality that allows things like Sean Parker's wedding fiasco in Big Sur happen.

Wonder how big of a factor that the upstream PS4 OS codebase now using LLVM/Clang was in this decision. Even if the PS4 wasn't FreeBSD based I can see the switch making sense on it's own tbh.

I vouch for it being used in a very high-profile, highly concurrent online service with great results.

In this particular case we owned both the client and server-side networking libraries - but all-in-all it worked quite well and helped us deal with NAT traversal issues among other things.

i reckon this is clearly intended for non-technical business/sales people. from an software/systems engineering perspective i feel that one of the primary benefits of email is its async behaviour.

unlike IRC/IM/video/telephone/face-to-face interactions, which happen in realtime, email provides an opportunity for reflecting on conversations and responses, while also allowing people in diverse geographic areas to take part in the natural flow of a conversation.

couple this with the fact that pretty much anyone can run a mail server and communicate with any other person on the internet - i am not sure how abandoning email communication for closed systems like yammer/facebook for near-time communication would be a net positive.

having said that - adding these tools to your suite of communication formats is clearly a good thing.

pretty awesome - but that's just the UI for HAL a full replica :p

I can give a huge thumbs up for ARPnet. They are based in downtown LA (and peer @ 1 Wilshire and I think they also are part of the Any2Net exchange from CoreSite), they also fully support IPv6 on VPC's as well as managed servers.

I've had both from them and have found support to be excellent. Honestly can't say enough good things about these guys.