Maybe ask yourself where DP comes from? The github MichaIng/build is a fork of armbian/build. What you see when you look inside an image is that DP lags behind the original and has of course also copied typos and errors from the original. Also note that an important script is: sed -i 's/armbian/dieptpi/g' for various names/files, with most important: armbian.list -> dietpi.list. That is at least what I see for some non-RPi board.Many people have written about DietPi, but I've never spent much time looking at it. I checked out the website today, and discovered that it's built on Debian. Guess what? RasPiOS is also built on Debian, which means they are quite similar, except (at a high level) for installation and management.
I didn't review the website in detail, but from my perhaps jaded perspective, I don't see much difference between DietPi and RasPiOS Lite other than DP supports a much broader range of hardware, which is great if you have one or more of those non-RaspberryPi boards.
But for the RaspberryPi, it seems to me that one would be better served running RasPiOS, which is from the same team that builds the hardware. The only exception I'd suggest is if you have a fleet of non-Pi boards and throw a Pi-board in there. DP makes sense for consistency in this scenario, assuming that it has the bits and pieces you need.
I'm not trying to unfairly denigrate DP. My observations and opinions are based on nearly 50 years of working on a broad range of computers and OS, and are worth exactly what you paid for them
For 64-bit BCM27xx, I see: ( cat /etc/apt/sources.list.d/dietpi.list )
deb https://dietpi.com/apt bookworm main rpi4
deb https://dietpi.com/apt all rpi
raspi.list is still there, one should probably grep for 'dietpi' to see what files are hacked/patched. At least fstab is beautified and crontab is calling /etc/cron.*/dietpi
There is no /etc/rpi-issue
DNS is set to 9.9.9.9
... etc.
Statistics: Posted by redvli — Wed Feb 12, 2025 11:49 am