Replies: 2 comments
-
Our base image depends on SBC as we use different types of images like Armbian, plain Debian or Raspberry OS. Furthermore, we don't do own kernel development. Most of the time, we use stock kernel / mainline kernel provided by the base image. We already offer Debian Bookworm images. Feel free to use/test them https://dietpi.com/downloads/images/ |
Beta Was this translation helpful? Give feedback.
-
To be precise: All our images are build from scratch via The dietpi-installer can be used to turn any Debian image into a DietPi image. For our own images, we use dietpi-build to generate the base image. It also allows you to choose between Debian Bullseye and Bookworm as well as choose the root filesystem type. But the letter, I think, still needs some updates to use Btrfs and F2FS, as I haven't tested it since a while. That script also includes minimising and archiving the image, which can otherwise be done separately with dietpi-imager. |
Beta Was this translation helpful? Give feedback.
-
I love what DietPi brings to the table, but I have some obscure needs that aren't met by the default images. Rather than request that the team build special images just for me, I would love to just do it myself, as I currently am able to with Armbian.
Currently, the things that I (and doubtlessly others) need from a custom build system are as follows:
Being able to do this with DietPi instead of Armbian would require less hacks to de-cruft and doubtlessly end up being more stable. As of now, I have not been able to find any info on how DietPi is currently built. Even a dump of whatever is used now would be helpful, and I would be happy to contribute back anything I end up building as far as scripts go.
Beta Was this translation helpful? Give feedback.
All reactions