OpenWRT 18.06 is the latest stable version. you can tweak it as you want and you will never be disappointed.
My Omega is running quite well for 48 hours, make sure to enable Luci in make menuconfig. You can setup all wifi and network interfaces from there.
one minor issue might be wifi is turned off at initial install. and then it seems only out of the box configured for IPv6 and not IPv4 which may or may not be an issue for the systems one is using to setup the omega2. additionally, in order to use sd card and/or usb thumb drive there needs to be packages installed before openwrt will recognize them. which without getting IPv4 wifi setup first there is no way get them onboard the omega2. another thing that sucks is most all the openwrt setup guides use ethernet connection for initial setup @ 192.168.1.1, good luck achieving that with the omega2 without a few packages and some trying configuration. yeah, generic 18.06 boots and runs but expect a challenge or two, especially if you have never done an openwrt install before. then again, running through a openwrt install makes you realize what a nice job folks at onion did in the setup processes for the omega2
I have not found how to disable it so I try to compile firmware but after reflashing i have some errors and Omega not booting.
So i'm still searching how to disable it without compiling.
Is any way how to change booting process where i can disable failsafe mode?
I have found that booting process is saved in read-only partition squashfs and i don't know if is possible to change something there.
I would like to use Onion Omega 2 for commercial use and i need to disable access to file system. Problem is that via failsafe mode and mount_root anybody can read and edit any content in device without password.
do download that OpenWrt package onto your Omega2(+) and install it
wget <LINK ADDRESS>
opkg install <PACKAGE NAME>
or add the proper OpenWrt repo to the /etc/opkg/distfeeds.conf file and reboot your Omega and run
opkg install <PACKAGE NAME>
Check @WereCatf 's source directory, specially first_time_setup.sh and my docker project on info about how to build from LEDE.
The OnionIoT repository is not ready yet, they will publish the source code in the future*.
Hopefully the docs will include cross compilation soon.
I'm still vague on why I might be running out of memory. I'm confused because the image size is always the same (16252928 bytes). Even for the different images on the repo site. It seems like this is normal, but I don't understand it. Perhaps the image size is always the same, regardless of what it contains. If that is true, do you (or does anyone) know how to determine what a given image contains?
Seems like we are having about the same config. Need to look into it more. What started the whole thing was that the official FW for Omega2(+) does not have it compile for including POSIX Messaging (mqueue) which I need for communication between my threads. But with LEDE I can get that, but so far no correct Wifi. Anyways, for now, I gave up on the mqueue and rewrote my apps to use mutex's and cond vars for synch and communication between threads (Client Server for Consumer/Producer notifications). So I am back using the official FW for it and stress testing it with 50 clients throwing messages at it randomly between 0-100ms inbetween for each client does not stress it much, so I am still happy with the implementation.
Thanks for all the help so far though from both of you! I may come back later and see if we can revisit this.