mirage

The Mirage frontend tool now generates a Makefile with a make depend
target, instead of directly invoking OPAM as part of mirage configure.
This greatly improves usability on slow platforms such as ARM, since the
output of OPAM as it builds can be inspected more easily. Users will now
need to run make depend to ensure they have the latest package set,
before building their unikernel with make as normal.

• Improve format of generated Makefile, and also colours in terminal output.
• Add make depend target to generated Makefile.
• Set OPAMVERBOSE and OPAMYES in the Makefile, which can be overridden.
• Add an ENTROPY device type for strong random sources (#256).

• Build OPAM packages in verbose mode by default.
• [types] Add FLOW based on TCPV4
• travis: build mirage-types from here, rather than 1.1.0

• Improvement to the Amazon EC2 deployment script.
• [types] Augment STACKV4 with an IPV4 module in addition to TCPV4 and UDPV4.
• Regenerate with OASIS 0.4.4 (which adds natdynlink support)

• Man page fixes for typos and terminology (#220).
• Activate backtrace recording by default (#225).
• Fixes in the V1.STACKV4 to expose UDPv4/TCPv4 types properly (#226).

The Mirage 1.1.0 release features a new combinator interface to make it easier to map device drivers in config.ml into concrete applications. This breaks backwards compatibility with Mirage 1.0 configuration files, but the added benefit is significant, so we felt it was worthwhile.

The types directory also now contains the V1 and V1_LWT module types used throughout the Mirage libraries.

The Makefile generated by mirage configure now includes debugging, symbols and annotation support for both the new-style binary annotations and the old-style .annot files.

• Do not remove OPAM packages when doing mirage clean (#143)
• [xen] generate a simple main.xl, without block devices or network interfaces.
• The HTTP dependency now also installs mirage-tcp-* and mirage-http-*.
• Fix generated Makefile dependency on source OCaml files to rebuild reliably.
• Support Fat_KV_RO (a read-only k/v version of the FAT filesystem).
• The Unix KV_RO now passes through to the underlying filesystem instead of calling crunch, via mirage-fs-unix.

• Add HTTP support.
• Fix KV_RO configuration for OPAM autoinstall.