mount kernel filesystems if run as pid1

[Vincinator]

Hi aurae community,

This PR adds first steps to make auraed boot as pid1, mainly mounting the kernel filesystems (devfs, procfs and sysfs), but also some minor fixes to make auraed boot without kernel panic.

• Fixes kernel panic due to a rust panic thrown by syslog creation (missing unix sockets [1])
  • The rust panic causes auraed to stop, and if started as pid1 the kernel will in turn also panic because the init process ended.
• Fixes hack/hack.mk for zsh users
• Adds a SystemRuntime (analog to AuraedRuntime), which handles system preparation.
  • SystemRuntime Case: not-pid1
    • assume a systemd environment (currently only unix socket /var/run/syslog)
  • SystemRuntime Case: pid1
    • initializes logging without unix socket dependency. Using syslog crate would require creation of unix socket first, and I suggest to discuss this first if there is a use case to have a unix socket for logging.
    • mounts file based kernel interfaces
    • devfs, sysfs, procfs
• Added helper functions for basic file io (currently for devfs, sysfs, procfs interfaces)
  • get content of e.g. /dev, /sys or /proc
  • or /sys/class/net/ to see available network interfaces

ToDo:

• Discuss Logging targets
  • Same log targets for all SystemRuntime cases?
• Network initialization
• Stop auraed in pid1 case gracefully (kernel halt syscall to shutdown or reboot)

How to test

Steps to run auraed as pid in a qemu vm are documented in the hack/README.md. Copy pasted them here:

make build-container
make kernel
make initramfs

# create `vm-br0` bridge on your machine:
make network

# run auraed in a VM as pid 1:
make virsh-start virsh-console virsh-stop

# exit VM console with Ctrl+]

Links

[1] https://docs.rs/syslog/latest/src/syslog/lib.rs.html#232-243

[cla-bot[bot]]

In order to contribute to an Aurae project you must sign and agree to the CLA.

[MalteJ]

@cla-bot check

[cla-bot[bot]]

In order to contribute to an Aurae project you must sign and agree to the CLA.

[cla-bot[bot]]

Rechecking your CLA permissions. Remember to add your GitHub username to the .clabot file. You can run @cla-bot check any time to check again.

[Vincinator]

@cla-bot check

[cla-bot[bot]]

In order to contribute to an Aurae project you must sign and agree to the CLA.

[cla-bot[bot]]

Rechecking your CLA permissions. Remember to add your GitHub username to the .clabot file. You can run @cla-bot check any time to check again.

[cla-bot[bot]]

In order to contribute to an Aurae project you must sign and agree to the CLA.

[MalteJ]

@cla-bot check

[cla-bot[bot]]

Rechecking your CLA permissions. Remember to add your GitHub username to the .clabot file. You can run @cla-bot check any time to check again.

[krisnova]

Non blocker however I am wondering about the name system for a module for init. This seems to be overloaded. I am unsure how I feel about it. Does anyone else have any thoughts?

[Vincinator]

Non blocker however I am wondering about the name system for a module for init. This seems to be overloaded. I am unsure how I feel about it. Does anyone else have any thoughts?

My vote goes to naming it init. Current scope is just initialization of stuff for the user space.

[Vincinator]

@kris-nova this PR is ready to be merged from my point of view Thanks for your feedback!

[krisnova]

Note for myself. Configuration to remove /proc procfs(5) is in this issue: https://github.com/aurae-runtime/auraed/issues/25