xhyve VS cpplinks

This is due to the way Windows and OSX implement docker. They both use a VM running Linux; Windows uses Hyper-V and OSX uses Bhyve. (https://github.com/machyve/xhyve)

Nowadays, docker uses runc, that is OCI compliant. Docker on macOS uses Hypervisor.framework through xhyve, and is completely macOS native. No VM is used (even under the hood) when running docker on macOS, it's native.

I was happiest with xhyve https://github.com/machyve/xhyve

Serial console in terminal was nice (for me!), network configuration was trash (I think I was able to set the subnet by fiddling around with system plists? and it would revert from time to time), and I didn't have to deal with Virtualbox. I've been away from macs for a while, I don't know if xhyve works on the M1, but it might. I ran a FreeBSD vm so I could run my server code on my laptop in an environment that was like production but slower.

The xhyve fork/port of bhyve for MacOS is worth mentioning: https://github.com/machyve/xhyve

Docker for Mac actually spins up TinyCoreLinux VMs using xhyve that your docker containers run on top of. This is because containers borrow the host kernel, so you can't natively run Linux containers on Mac. Xhyve spawns VMs so a Linux kernel will be present.

There's also been a port of FreeBSD's bhyve to macOS for years: https://github.com/machyve/xhyve (which, in turn, is [or at one point was] used by Docker to virtualize Linux)

I've used xyhve on my Mac to have a FreeBSD VM running a copy of https://www.freshports.org/, including a copy of the database, which runs about 200GB. For dev work, it was fine. I used it when I didn't have [great] internet connectivity, for example, when on the train/plane. When upgrading packages or just doing dev work, it was great.

linking and loading: https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md - in addition to the aforementioned books and blog posts, there also some pretty good talks: https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md#talks

For more compilers correctness* resources see https://github.com/MattPD/cpplinks/blob/master/compilers.correctness.md

As for linkers and loaders, see https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md

More: https://github.com/MattPD/cpplinks/blob/master/atomics.lockfree.memory_model.md

Take the red pill and see how deep the rabbit hole goes... https://github.com/MattPD/cpplinks/ https://github.com/shafik/cpp_learning

x86-64 tutorials here should be a good starting point: https://github.com/MattPD/cpplinks/blob/master/assembly.x86.md#tutorials

See also static analysis resources (more C++-oriented, although some of the readings are general): https://github.com/MattPD/cpplinks/blob/master/analysis.static.md#readings-books and https://gist.github.com/MattPD/71b63a3e1600c2b52e1db80fa2834e60#correctness-in-practice (formal methods and program analysis in industry).

Further readings: Book recommendations in https://github.com/MattPD/cpplinks/blob/master/compilers.md#books as well as program analysis resources (in particular lattice theory, type systems and programming languages theory, related notation): https://gist.github.com/MattPD/00573ee14bf85ccac6bed3c0678ddbef#program-analysis-resources

Microarchitectural performance analysis research is a pretty active and interesting area--see also: https://github.com/MattPD/cpplinks/blob/master/performance.tools.md#microarchitecture

For more on GDB see: https://github.com/MattPD/cpplinks/blob/master/debugging.md#gdb