Werner
Werner
I like to test uncommon stuff to see what happens. It is up to you to discard the report.
As stated this has low/no priority as it is handled properly inside the honeypot.
I mostly do this the noob way: ``` du -a /sys|grep led|grep trigger echo heartbeat > /sys/whatever/led/i/need/trigger ``` 🤦
I usually only use on, off or heartbeat on red/green led. I don't know on which familiy more stuff is possible and don't even know what stuff this might be...
From my guts feel no. At least OPis have `orangepi` as string somewhere in the path to the led trigger files. Did not have a chance yet to compare. I'll...
Nanopi R4S: ``` 0 ./devices/platform/gpio-leds/leds/status_led/trigger 0 ./devices/platform/gpio-leds/leds/lan_led/trigger 0 ./devices/platform/gpio-leds/leds/wan_led/trigger ``` Orange Pi One Plus: ``` 0 ./devices/platform/leds/leds/orangepi:red:power/trigger 0 ./devices/platform/leds/leds/orangepi:green:status/trigger ``` Orange Pi One: ``` 0 ./devices/platform/leds/leds/orangepi:red:status/trigger 0 ./devices/platform/leds/leds/orangepi:green:pwr/trigger ```
Yes and no. It is another confirmation that there is no standardization between SoCs...
I don't know why that would make a big difference but welp, you maintain it anyways :D
Isn't there an example file somewhere anyways?
Note: `REPOSITORY_UPDATE` feeds into https://github.com/armbian/build/blob/241f015ac7abb6f74e8ee5fabe61dc0a9f565c0a/lib/general.sh#L809