aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlonkaars <loek@pipeframe.xyz>2024-05-11 17:02:28 +0200
committerlonkaars <loek@pipeframe.xyz>2024-05-11 17:02:28 +0200
commit159f34a6637ad2685748e34ab904f8ad95c5073e (patch)
tree6dcb997eee82fd9e4f90b0b920c61f2a7e91e8a8
parent98003246dc087541e1cf57441f25ca0a1cda03ed (diff)
more tips
-rw-r--r--readme.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/readme.md b/readme.md
index 3326740..ef2f63a 100644
--- a/readme.md
+++ b/readme.md
@@ -24,6 +24,8 @@
# tips
+- **Start writing a kernel module that targets the kernel version of the
+ BeagleBone image you're planning on using.**
- When the kernel documentation references manpages, these actually contain
useful information. Manpages are not only for commands, but also include
detailed documentation for the syscall interface and other C APIs.
@@ -32,8 +34,11 @@
system calls), you should append the number between brackets to the `man`
command, i.e. to read 'write(2)' use the command `man 2 write`.
- Use `dmesg` with the `-w` or `-W` option (see man dmesg(1))
-- Start writing a kernel module that targets the kernel version of the
- BeagleBone image you're planning on using.
+- If you somehow manage to corrupt/break your system in any way, the IoT images
+ seem to work fine for `chroot`ing and fixing stuff. (Installing a
+ `linux-image-` package from chroot prints lots of errors, but seems to work
+ fine afterwards?). I have not tried using the IoT images as an installation
+ base, as we were steered away from using these images due to slow boot times.
# direct ethernet setup