Implement

The Plan

Since systemd claims to not be tightly coupled, we should be able to replace components one-at-a-time. If this turns out to be hard the documentation we create in the process will be available as a refutation of the loose coupling claim.

Components

• /sbin/init
  • system lifecycle
    • startup
    • state change (dock/undock, network change detection and response)
    • shutdown
  • process lifecycles
• Session Management
• Logging
• Process Restriction
• Configuration Management
  • system settings
    • network
    • time
    • kernel
  • user settings?
• Messaging

Testing

Full testing will be slow because we will have to build/install a distro "from scratch" (debootstrap), including something like GNOME, run it in a VM to measure baseline, then install NiceSystem in that VM and re-run all the tests again. We can probably crib from those projects' own test systems to save development effort, but a full end-to-end test run could be a multi-day affair.