DietPi installation stats, which device is popular?

[Fourdee]

Update: Since DietPi v6.9 we upgraded and restarted DietPi-Survey and added some public statistics page: https://dietpi.com/survey/
Edit by @MichaIng

DietPi installations from 24th Jan 2017, to 18th Feb 2017:

Thought I'd share these stats on unique installations, interesting results.

Total unique installs:

Code: Select all

root@dietpi:/home/dietpi-survey# ls -lha | grep '.txt' | wc -l
5286

Total Odroid C2 installs:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]oDroid C2[[:space:]]' | wc -l
375

Total C1:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]oDroid C1[[:space:]]' | wc -l
128

Total XU4:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]oDroid XU3/4[[:space:]]' | wc -l
249

Total RPi:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]RPi[[:space:]]' | wc -l
2970

Total Sparky:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]Sparky[[:space:]]' | wc -l
24

Total OrangePi's:

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi Plus[[:space:]]' | wc -l
88

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi PC[[:space:]]' | wc -l
201

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi One[[:space:]]' | wc -l
93

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi Zero[[:space:]]' | wc -l
296

Example survey file (gets uploaded everytime dietpi-software is used)

Code: Select all

-------------------------
DietPi-Survey V3
-------------------------

Upload Count   : 2
DietPi Version : 142
Hardware Index : 1
Hardware Name  : RPi Zero (armv6l)
Distro Index   : 3
Autoboot Index : 0
Country        : United Kingdom
Hostname       : DietPi

-------------------------
DietPi-Software Installed
-------------------------
aSOFTWARE_INSTALL_STATE[0]=2
aSOFTWARE_INSTALL_STATE[1]=0
aSOFTWARE_INSTALL_STATE[2]=0
aSOFTWARE_INSTALL_STATE[3]=0
aSOFTWARE_INSTALL_STATE[4]=0
aSOFTWARE_INSTALL_STATE[5]=0
aSOFTWARE_INSTALL_STATE[6]=0
aSOFTWARE_INSTALL_STATE[7]=0
aSOFTWARE_INSTALL_STATE[8]=0
aSOFTWARE_INSTALL_STATE[9]=2
aSOFTWARE_INSTALL_STATE[10]=0
aSOFTWARE_INSTALL_STATE[11]=0
aSOFTWARE_INSTALL_STATE[12]=0
aSOFTWARE_INSTALL_STATE[13]=0
aSOFTWARE_INSTALL_STATE[14]=0
aSOFTWARE_INSTALL_STATE[15]=0
aSOFTWARE_INSTALL_STATE[16]=0
aSOFTWARE_INSTALL_STATE[17]=0
aSOFTWARE_INSTALL_STATE[18]=0
aSOFTWARE_INSTALL_STATE[19]=0
aSOFTWARE_INSTALL_STATE[20]=0
aSOFTWARE_INSTALL_STATE[21]=0
aSOFTWARE_INSTALL_STATE[22]=0
aSOFTWARE_INSTALL_STATE[23]=0
aSOFTWARE_INSTALL_STATE[24]=0
aSOFTWARE_INSTALL_STATE[25]=0
aSOFTWARE_INSTALL_STATE[26]=0
aSOFTWARE_INSTALL_STATE[27]=0
aSOFTWARE_INSTALL_STATE[28]=0
aSOFTWARE_INSTALL_STATE[29]=0
aSOFTWARE_INSTALL_STATE[30]=0
aSOFTWARE_INSTALL_STATE[31]=0
aSOFTWARE_INSTALL_STATE[32]=0
aSOFTWARE_INSTALL_STATE[33]=0
aSOFTWARE_INSTALL_STATE[34]=0
aSOFTWARE_INSTALL_STATE[35]=0
aSOFTWARE_INSTALL_STATE[36]=0
aSOFTWARE_INSTALL_STATE[37]=0
aSOFTWARE_INSTALL_STATE[38]=0
aSOFTWARE_INSTALL_STATE[39]=0
aSOFTWARE_INSTALL_STATE[40]=0
aSOFTWARE_INSTALL_STATE[41]=0
aSOFTWARE_INSTALL_STATE[42]=0
aSOFTWARE_INSTALL_STATE[43]=0
aSOFTWARE_INSTALL_STATE[44]=0
aSOFTWARE_INSTALL_STATE[45]=0
aSOFTWARE_INSTALL_STATE[46]=0
aSOFTWARE_INSTALL_STATE[47]=0
aSOFTWARE_INSTALL_STATE[48]=0
aSOFTWARE_INSTALL_STATE[49]=0
aSOFTWARE_INSTALL_STATE[50]=0
aSOFTWARE_INSTALL_STATE[51]=0
aSOFTWARE_INSTALL_STATE[52]=0
aSOFTWARE_INSTALL_STATE[53]=0
aSOFTWARE_INSTALL_STATE[54]=0
aSOFTWARE_INSTALL_STATE[55]=0
aSOFTWARE_INSTALL_STATE[56]=0
aSOFTWARE_INSTALL_STATE[57]=0
aSOFTWARE_INSTALL_STATE[58]=0
aSOFTWARE_INSTALL_STATE[59]=0
aSOFTWARE_INSTALL_STATE[60]=0
aSOFTWARE_INSTALL_STATE[61]=0
aSOFTWARE_INSTALL_STATE[62]=0
aSOFTWARE_INSTALL_STATE[63]=0
aSOFTWARE_INSTALL_STATE[64]=0
aSOFTWARE_INSTALL_STATE[65]=2
aSOFTWARE_INSTALL_STATE[66]=0
aSOFTWARE_INSTALL_STATE[67]=0
aSOFTWARE_INSTALL_STATE[68]=0
aSOFTWARE_INSTALL_STATE[69]=0
aSOFTWARE_INSTALL_STATE[70]=0
aSOFTWARE_INSTALL_STATE[71]=0
aSOFTWARE_INSTALL_STATE[72]=0
aSOFTWARE_INSTALL_STATE[73]=0
aSOFTWARE_INSTALL_STATE[74]=0
aSOFTWARE_INSTALL_STATE[75]=0
aSOFTWARE_INSTALL_STATE[76]=0
aSOFTWARE_INSTALL_STATE[77]=0
aSOFTWARE_INSTALL_STATE[78]=0
aSOFTWARE_INSTALL_STATE[79]=0
aSOFTWARE_INSTALL_STATE[80]=0
aSOFTWARE_INSTALL_STATE[81]=0
aSOFTWARE_INSTALL_STATE[82]=0
aSOFTWARE_INSTALL_STATE[83]=0
aSOFTWARE_INSTALL_STATE[84]=0
aSOFTWARE_INSTALL_STATE[85]=0
aSOFTWARE_INSTALL_STATE[86]=0
aSOFTWARE_INSTALL_STATE[87]=0
aSOFTWARE_INSTALL_STATE[88]=0
aSOFTWARE_INSTALL_STATE[89]=0
aSOFTWARE_INSTALL_STATE[90]=0
aSOFTWARE_INSTALL_STATE[91]=0
aSOFTWARE_INSTALL_STATE[92]=0
aSOFTWARE_INSTALL_STATE[93]=0
aSOFTWARE_INSTALL_STATE[94]=0
aSOFTWARE_INSTALL_STATE[95]=0
aSOFTWARE_INSTALL_STATE[96]=0
aSOFTWARE_INSTALL_STATE[97]=0
aSOFTWARE_INSTALL_STATE[98]=0
aSOFTWARE_INSTALL_STATE[99]=0
aSOFTWARE_INSTALL_STATE[100]=0
aSOFTWARE_INSTALL_STATE[101]=0
aSOFTWARE_INSTALL_STATE[102]=0
aSOFTWARE_INSTALL_STATE[103]=2
aSOFTWARE_INSTALL_STATE[104]=0
aSOFTWARE_INSTALL_STATE[105]=2
aSOFTWARE_INSTALL_STATE[106]=0
aSOFTWARE_INSTALL_STATE[107]=0
aSOFTWARE_INSTALL_STATE[108]=0
aSOFTWARE_INSTALL_STATE[109]=0
aSOFTWARE_INSTALL_STATE[110]=0
aSOFTWARE_INSTALL_STATE[111]=0
aSOFTWARE_INSTALL_STATE[112]=0
aSOFTWARE_INSTALL_STATE[113]=0
aSOFTWARE_INSTALL_STATE[114]=0
aSOFTWARE_INSTALL_STATE[115]=0
aSOFTWARE_INSTALL_STATE[116]=0
aSOFTWARE_INSTALL_STATE[117]=0
aSOFTWARE_INSTALL_STATE[118]=0
aSOFTWARE_INSTALL_STATE[119]=0
aSOFTWARE_INSTALL_STATE[120]=0
aSOFTWARE_INSTALL_STATE[121]=0
aSOFTWARE_INSTALL_STATE[122]=0
aSOFTWARE_INSTALL_STATE[123]=0
aSOFTWARE_INSTALL_STATE[124]=0
aSOFTWARE_INSTALL_STATE[125]=0
aSOFTWARE_INSTALL_STATE[126]=0
aSOFTWARE_INSTALL_STATE[127]=0
aSOFTWARE_INSTALL_STATE[128]=0
aSOFTWARE_INSTALL_STATE[129]=0

#DietPi Choice System: SSH Server
INDEX_SSHSERVER_CURRENT=-2
INDEX_SSHSERVER_TARGET=-2

#DietPi Choice System: File Server
INDEX_FILESERVER_CURRENT=0
INDEX_FILESERVER_TARGET=0

#DietPi Choice System: Logging
INDEX_LOGGING_CURRENT=-1
INDEX_LOGGING_TARGET=-1

#DietPi Preference System: Webserver base
INDEX_WEBSERVER_CURRENT=-2
INDEX_WEBSERVER_TARGET=-2

-------------------------
FileSystem
-------------------------
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G  2.2G   12G  16% /
devtmpfs        237M     0  237M   0% /dev
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           242M  4.3M  237M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           242M     0  242M   0% /sys/fs/cgroup
tmpfs            10M  1.2M  8.9M  12% /DietPi
tmpfs            20M   88K   20M   1% /var/log
tmpfs           242M     0  242M   0% /tmp
/dev/mmcblk0p1   63M   23M   41M  36% /boot

[Zombievirus]

very interesting!

What i would like to know is the number of active unique DietPi Installations regardless of Device and Installtion Period.

How many people in the world are running DietPi on their SBCs today?

[Kymru]

very interesting!

What i would like to know is the number of active unique DietPi Installations regardless of Device and Installtion Period.

How many people in the world are running DietPi on their SBCs today?

that would be interesting, to wet your interest, i have currently

oDroid C1+
oDroid C2
Raspberry Pi 2
OrangePi Plus

running DietPi

[Fourdee]

What i would like to know is the number of active unique DietPi Installations regardless of Device and Installtion Period.

Its around 60,000 unique installs since we started (04/2015), minus any users who have disabled dietpi-survey, and downtime we had with the old webserver (which ran from my house).

How many people in the world are running DietPi on their SBCs today?

Unfortunately, we have no real way of knowing, only unique installs. The survey file upload, only occurs when users install something with dietpi-software.

More info on dietpi-survey, and example of the data we receive:
http://dietpi.com/phpbb/viewtopic.php?f=8&t=20&p=34#p34

[Fourdee]

that would be interesting, to wet your interest, i have currently

oDroid C1+
oDroid C2
Raspberry Pi 2
OrangePi Plus

running DietPi

OPi's

Code: Select all

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi Plus[[:space:]]' | wc -l
88

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi PC[[:space:]]' | wc -l
201

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi One[[:space:]]' | wc -l
93

root@dietpi:/home/dietpi-survey# cat *.txt | grep '[[:space:]]OrangePi Zero[[:space:]]' | wc -l
296

[rothchild]

Hmm going to have to check that I have survey running for you as I've got it on a NanoPi Neo (and running very sweetly it is too!)

[WarHawk]

Way cool!!!!!

[DarthKeizer]

Way cool!!!!!

Haha indeed it is

[bronco]

Really interesting. I downloaded the survey files that are currently available:

3717 files today but since the filenames also contain version information these were based only on 3656 different UUIDs (the term 'unique install' is misleading anyway since everyone installing from scratch will end up with a new UUID):

Code: Select all

macbookpro-tk:dietpi.com tk$ ls -la *.txt | cut -c47-82 | sort | uniq | wc -l
    3656

So today DietPi is a RPi distro with some ODROID, x86, Rock64 and Tinkerboard installations:

Code: Select all

macbookpro-tk:dietpi.com tk$ grep 'Hardware Name' * | awk -F" : " '{print $2}' | tr '[:upper:]' '[:lower:]' | sort | uniq -c | sort -r
1298 rpi 3 model b (armv7l)
 358 rpi 2 model b (armv7l)
 301 rpi 3 model b+ (armv7l)
 249 rpi b (armv6l)
 221 rpi zero w (armv6l)
 210 virtual machine (x86_64)
 157 odroid xu3/xu4/hc1/hc2 (armv7l)
 149 odroid c2 (aarch64)
  96 rock64 (aarch64)
  94 orangepi zero (armv7l)
  84 rpi b+ (armv6l)
  81 asus tinker board (armv7l)
  70 native pc (x86_64)
  40 rpi zero (armv6l)
  31 pine a64 (aarch64)
  29 orangepi pc (armv7l)
  28 nanopi neo (armv7l)
  27 rpi  (armv7l)
  25 sparky sbc (armv7l)
  20 orangepi one (armv7l)
  14 nanopi neo 2 (aarch64)
  12 odroid c1 (armv7l)
  12 nanopi m1/t1 (armv7l)
  10 rpi b (ecn0001) (armv6l)
   8 pine a64+ 2gb (aarch64)
   8 generic device (armv7l)
   7 rpi  (armv6l)
   7 nanopi m2/t2 (armv7l)
   6 orangepi plus (armv7l)
   6 opi pc2 (aarch64)
   6 nanopi m3/t3 (armv7l)
   5 generic device (aarch64)
   4 unknown device (armv7l)
   4 opi win (aarch64)
   3 rpi a+ (armv6l)
   3 pine a64+ 1gb (aarch64)
   3 opi zero 2 plus (aarch64)
   3 odroid xu3/4 (armv7l)
   3 nanopi k1 plus (aarch64)
   3 bananapi pro (armv7l)
   2 rpi a (armv6l)
   2 opi prime (aarch64)
   2 odroid n1 (aarch64)
   2 generic device (x86_64)
   1 unknown device (armv6l)
   1 rpi cm 3 (armv7l)
   1 orangepi plus / plus 2 (armv7l)
   1 opi zero 2 plus (armv7l)
   1 nanopi m3/t3 (aarch64)
   1 bananapi m2+ (armv7l)
   1 bananapi (armv7l)

Also nice: You make it easy for your users to get hacked by encouraging them to use insecure protocols (FTP in 2018, what a funny idea!) with handlers that store logon credentials in a horribly insecure way and then upload these logon credentials to a publicly readable directory somewhere on the Internet without asking users first! Well done.

Code: Select all

macbookpro-tk:dietpi.com tk$ grep 'curlftpfs' *.txt | wc -l
      13

2 of these sites publicly available via FTP from everywhere and you publishing the logon credentials on dietpi.com accessible by everyone.

On a related note (security): The whole world even Microsoft included tries to get rid of SMB1 since years now and you make it DietPi's default in 2018. https://blogs.technet.microsoft.com/fil ... sing-smb1/ vs. https://github.com/Fourdee/DietPi/issues/1693

Now let's have a look how DietPi deals with security issues in 2018: Simply censoring the reports and ignoring the problem as in the past or able to improve and fix issues?

[Fourdee]

Really interesting. I downloaded the survey files that are currently available:
94 orangepi zero (armv7l)

Hi Thomas @bronco,

I can confirm a potential risk due to $(df -h), contained at the end of our survey file, printing curlftp mount credentials in its output.
Although this is not an issue for local IP FTP servers, external FTP IP's using curlftp mount are at risk (i counted 2 users), should this information come into the wrong hands.

I was unaware of this. As such, we've removed all the survey files and taken it offline. This data is no longer available, or, uploaded to our server.

We'll re-review dietpi-survey at some point in the future.

Thanks for bringing this to our attention.