Personal Technical Notes & Documentation
Self-maintained technical notes & documentation, forming my technical PKM. PR's are welcome!
To keep the maintenance burden to a minimum, the content is only cataloged using directories. No other indexes are provided.
However, using a documentation platform such as Read the Docs, you are able to auto-generated a hierarchical view of this content.
-- Marco Vedovati (docs (at) sba dot lat)
Read the Docs
I am using Read the Docs + mkdocs to auto-generate HTML from Markdown.
For local development & testing, this command will bring up a local webserver
rendering documentation pages:
$ mkdocs serve [-a LISTEN-IP:LISTEN-PORT] [--livereload]
Linting
Use ruby-mdl.
Navigation
- Personal Technical Notes & Documentation
- Google Sheets / Excel "advanced" uses
- Apps
- Architecture
- Coding
- Containers
- Debugging
- GNU Make
- Git
-
Lang CXX
- C vs C++
- Generate code coverage information
- Compiler optimizations
- Constructors and initialization
- C++
- cscope: browse a C program source code (e.g. kernel)
- Division with ceiling
- glibc
- Libraries and Linking
- C macros, token pasting, stringification
- Macros
- Malloc fork
- C / C++ Memory Model (Atomics et al.)
- Single-depth loop replacement for nested loops
- Size of data types
- C / C++
- Thread local storage
- Undefined behaviour
- volatile
- Lang Go
- Lang HTML CSS
- Lang Nodejs
- Lang Python
- Lang bash
-
Linux
- Processes
- Signals
- awk
- BPF (eBPF)
- Linux/Unix Command Line Tools
- Deb Packages
- DNS Tools
- Kernel misc
- Soft (Sym) and Hard Links
- Linux Memory Map and Address Space
- Linux Namespaces
- Linux Network (iproute2) Commands
- Linux Networking
- Procfs kernel internals
- Notes on the Linux Programming Interface
- Rpm Packages
- SUSE OSC Command line tool
- Linux Threads
- Tips n Tricks
- macOS