Files
linuxkit/projects
Thomas Gazagnaire f5716ce985 Split the DHCP client into three components communicating via named pipes
3 components:

- network: read eht0 and proxy only DHCP traffic
- engine: read DHCP traffic, handle DHCP client state machine, and call the
  host actuator to change the host config when a lease is obtained
  host system configuration.
- actuator: perform the acutall net syscalls, read and write host configuration
  files, etc

These three components can either be linked together in a single binary
(see src/dhcp-client/main.ml) or can be used as 3 binaries communicating
over cap-n-proto.

Signed-off-by: Thomas Gazagnaire <thomas@gazagnaire.org>
2017-07-17 17:46:17 +02:00
..
2017-07-17 11:04:18 +01:00
2017-07-17 11:04:18 +01:00
2017-07-15 14:13:25 +01:00
2017-07-17 11:04:18 +01:00
2017-07-17 11:04:18 +01:00
2017-07-15 14:13:25 +01:00
2017-07-15 14:13:25 +01:00
2017-07-17 11:04:18 +01:00
2017-07-15 14:13:25 +01:00
2017-06-13 11:08:29 -06:00

Projects

We aim to provide a set of open spaces for collaboration to help move projects towards production. Projects should usually at a minimum provide a README of how to get started using the project with Moby, and a roadmap document explaining what the aims are and how to contribute. Most projects will probably provide a way to run the project in a custom Moby build in its current state, which ideally will be integrated in the Moby CI so there are checks that it builds and runs. Over time we hope that many projects will graduate into the recommended production defaults, but other projects may remain as ongoing projects, such as kernel hardening.

If you want to create a project, please submit a pull request to create a new directory here.

Current projects

Current projects not yet documented

  • VMWare support (VMWare)
  • ARM port and secure boot integration (ARM)

Completed projects

  • aws/: AWS support was merged into mainline in #1964.