Oranges...

[garfius]

Hi!
I am a big Dietpi fan, but i use Orange Pi devices. But lately i have found these are no longer supported by this distro....
Last week i downloaded 160 image for one of my 'oranges' and IT WAS GREAT! , but other ones are needed.

Anyways, can anyone post Orange pi legacy images ?
Please...

Thanks in advance.

[WarHawk]

Yeah...apparently I'm going to have to find another distro as well

I don't use Armbian because for some reason if the power cuts out it corrupts the card and I can no longer boot..dietpi uses the raspberry pi type architecture (a small fat 32 partition with boot info, then a larger EXT4 for all the other data) and for some reason will reboot...the developers at armbian constantly chided on me when I would say that, but I have tried it on multiple orange pi's with multiple cards and it kept happening...

Oh well...fooey on dietpi for dropping a large and inexpensive up and comer on the SBC platform

[MichaIng]

Yeah, following the discussion on github about it, you will see that it was a necessary step to drop ARMbian based images/devices from our lineup. I am deeply disappointed by this fact, as the reason is a totally unnecessary conflict, at least from our side. But the situation was going along with constant stress and frustration and bad media from ARMbian side about DietPi on various platforms. The clear cut seem to be the only solution.

However if interest from OPi (as well as BananaPi) users is great enough, we might consider to use alternative images, independent from ARMbian as bases for DietPi. From what I heard, the "official" ons from OPi/BPi are not to good quality wise, but if someone finds a stable/well working/maintained one, requests are welcome as always. So far, it should be still possible to use ARMbian as basis and manually run PREP_SYSTEM_FOR_DIETPI.sh on once supported OPi/BPi devices: https://github.com/Fourdee/DietPi/blob/ ... _DIETPI.sh

[Fourdee]

@WarHawk

I feel your pain and I'am sorry that you (the user), is the one who has to experience the negative impact of our decision to drop ARMbian images.
I wish there was another way, but without lack of trying, it was a dead end that only caused pointless frustrations for those involved.

Ok, maybe we can do a trial run of OPi PC image based on OPi's official image, would that be of interest?
The only downside is that their image is 3 years out of date. Kernel will be 3.x and lack many of the H3 fixes in 4.x.

OPi PC was roughly 600 installs in a month, the highest of all systems we dropped, by some margin.

@garfius

Anyways, can anyone post Orange pi legacy images ?
Please...

I'am sorry, but we cannot allow those images to be re-released in the wild.

[WarHawk]

Yeah, following the discussion on github about it, you will see that it was a necessary step to drop ARMbian based images/devices from our lineup. I am deeply disappointed by this fact, as the reason is a totally unnecessary conflict, at least from our side. But the situation was going along with constant stress and frustration and bad media from ARMbian side about DietPi on various platforms. The clear cut seem to be the only solution.

However if interest from OPi (as well as BananaPi) users is great enough, we might consider to use alternative images, independent from ARMbian as bases for DietPi. From what I heard, the "official" ons from OPi/BPi are not to good quality wise, but if someone finds a stable/well working/maintained one, requests are welcome as always. So far, it should be still possible to use ARMbian as basis and manually run PREP_SYSTEM_FOR_DIETPI.sh on once supported OPi/BPi devices: https://github.com/Fourdee/DietPi/blob/ ... _DIETPI.sh

It's why I'm here, and I recommend anyone that use Orange Pi's. Dropping support for a growing base of Orange Pi users is not a good idea (a bit of a gut punch in fact)
Even if you do release distro's slowly, or go completely different from Armbian...that is fine...but we need the support and welcome this incredible distro.

[WarHawk]

@WarHawk

I feel your pain and I'am sorry that you (the user), is the one who has to experience the negative impact of our decision to drop ARMbian images.
I wish there was another way, but without lack of trying, it was a dead end that only caused pointless frustrations for those involved.

Ok, maybe we can do a trial run of OPi PC image based on OPi's official image, would that be of interest?
The only downside is that their image is 3 years out of date. Kernel will be 3.x and lack many of the H3 fixes in 4.x.

OPi PC was roughly 600 installs in a month, the highest of all systems we dropped, by some margin.

@garfius

Anyways, can anyone post Orange pi legacy images ?
Please...

I'am sorry, but we cannot allow those images to be re-released in the wild.

Absolutely...why mimic Armbian (and all it's nuances)...dietpi is it's own beast...and if the developers can build it that way...rock on!
Why try to learn what they do, to implement into dietpi (reinventing the wheel)...make dietpi it's on distro and build it to your way of thinking (for ease of development and support)...

At the very least..how about a "minimal" server type distro (working drivers, but no other packages other than bare stock)...no scripting (other than simple hardware mounting or other things that are easy to design/implement)..then allow people to build it from the ground up if needed using apt or whatever

This way we can get the SBC's up and running and customize them independent of the supported distro's
Mainly because some of the linux savy folks can configure and setup with debians normal package schemes

[WarHawk]

How about releasing the 6.2 "lite" distro with all packages removed

This way install it, boot it...then apt-get to setup what we want from the repositories...questions then aimed at those communities vs at you

All you guys have to do then is maintain the "base" release

[midnightwatcher]

Why not just splurge on a C2 or, better yet, a Z83?

[WarHawk]

Why not just splurge on a C2 or, better yet, a Z83?

I have 8 kids...

[MichaIng]

About "own" distro:
The thing is that we do no kernel/firmware development. What we do is use an existing Debian/Raspbian image with implemented bootloader/ kernel/firmware, remove all non essential packages/modules/services/files, optimize settings for low resource usage and put DietPi system/scripts on top for easy installation/setup/configuration/user experience.

So we rely on firmware repositories, e.g. achieve.raspberrypi.org, the one odroid/meveric provides or Debian itself. ARMbian provides own up to date kernel/firmware for those devices, where often Debian itself does not (also as they avoid non-free kernel/bootloader firmware blobs e.g.) and/or the device producers do not maintain their own too well/outdated.
So we did remove all non-essential stuff from ARMbian images already, but we needed their firmware.

But yeah, I think it is worth retrying images from OPi/BPi then, still we have to take care they do not use ARMbian themself, which are at least also offered often on their web sites.