|
You are here |
eklausmeier.goip.de | ||
| | | | |
ounapuu.ee
|
|
| | | | | Introduction I've covered my self-hosting setup in a previous post. It has been a couple of months and the setup has mostly been fine. Sure, the power usage was pretty big under load, and yes, my internet did cut out every time I turned the VM on with all the services starting, but other than that, it has been rock-solid. However, I soon realized that in most situations, the 12 CPU cores is a bit overkill. | |
| | | | |
dan.langille.org
|
|
| | | | | ||
| | | | |
www.berrange.com
|
|
| | | | | [AI summary] The user has provided a detailed description of a tool for creating custom initramfs images for testing purposes. The tool allows copying specific files, kernel modules, and libraries into the initramfs, enabling low-overhead debugging of QEMU/Linux guest behavior. It is designed to be simple, fast, and non-intrusive, with options for copying files, kernel modules, and handling specific testing requirements. The tool has been useful for debugging Linux kernel regressions, such as issues with the iTCO watchdog. | |
| | | | |
dan.langille.org
|
|
| | | [AI summary] The provided text is a mix of technical system logs and unrelated content. Here's a breakdown: 1. **System Logs**: These show hardware and storage device initialization, including SATA drives, SCSI devices, and system boot processes. Key points include: - Multiple SATA drives (ada0, ada1, etc.) identified as TOSHIBA models. - SCSI devices (da0, da1, etc.) also detected, likely connected via a SAS controller. - System boot information, including CPU initialization and kernel loading. 2. **Unrelated Content**: The text includes: - A call to action for commenting on a blog post. - Affiliate links and product recommendations. - Website navigation and copyright information. 3. **Potential Issues**: The logs and unrelated content ... | ||