| commit | 1b2df233817ae3dd09ff33ad18d319a50be10584 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Tue Jun 14 12:42:03 2022 +0200 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Thu Jun 16 09:59:11 2022 +0000 |
| tree | 380e12519010691e7f701d71b171225a9c853e15 | |
| parent | f8da2e7dfbcbb144ee894875e46c44a525e57c5c [diff] |
m/n/core: add pstore handling Adds a one-shot runnable which dumps all kmsg dumps to the system log and then clears the pstore. This makes sure that there is always space for new pstore entries and gives administrators the option of reading crash logs without booting another operating system. It also helps some broken EFI firmware to not fail to boot. Change-Id: Icbf30c0a0898e0e660910a80637d544f022a97cd Reviewed-on: https://review.monogon.dev/c/monogon/+/770 Reviewed-by: Sergiusz Bazanski <serge@monogon.tech> Tested-by: Jenkins CI
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
Launch the node:
scripts/bin/bazel run //:launch -c dbg
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -c dbg -- kubectl describe
Run tests:
scripts/bin/bazel test -c dbg //...