An overlay setup part of the stock configuration. I guess if you knew you were going to change many things you could remove what would only be replaced in the overlay from the initial squashfs image, but that's fairly advanced - either needing an expansion and recreation of the squashfs on another machine, or a rebuild of LEDE from sources.
I do wonder if what's being seen is perhaps a behavior where the jffs2 overlay ends up read only when it becomes full of past changes.
If the changes made are known, a factory reset should get the overlay writeable again and then the USB storage could be set up. It may also be possible to create a mountpoint on some partition which is itself a ramdisk, and so still writeable - but you'd have to re-do that on every boot.
It is not possible. In addition to the missing socket, there are other components missing, some are under the shield.
Care to elaborate? Not much should be required, so this is a bit surprising, unless it's an intentional disabling.
That said, USB-based storage could be another option - but it should be kept in mind that neither is robust in the face of unexpected shutdowns/reboots - one of the real strengths of these platforms over the computationally far more powerful and hardly more expensive raspberry pi, is that they don't depend on a fragile SD card. If you could boot a pi W from an SPI flash, it's questionable if there would be a market for MT7688 systems at all.
I succed to put the exec and read permissions for files and folders with the line option in fstab
"option options 'rw,sync,uid=65534,gid=65534,umask=0000'"
but it's impossible to put write permissions make import the umask.
I use nobody user's and nothing changes.
Hi @Janus-Sanders, hmmm, installing a package on the Omega shouldn't crash it... Can you give us a little bit more description on what happened? This way we might be able to figure out what the issue might be and hopefully resolve it in the future.
Looks like your connection to Community was lost, please wait while we try to reconnect.