-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is next ? #2
Comments
I would vote for the last option. |
That’s also my opinion. But I have myself some troubles having this working 😜so there should be a packaging effort to do here ... |
I also prefer option 3, but it may take some time to migrate everything to the new system. |
Where do we want to store our configuration files? /config? |
I vote for a uniq config file in /etc. |
Yes, /etc/ sounds fine. Any idea how to migrate everyone to the new system? |
Step by step. First I would actually need to get my rootfs to boot ;) I have only macs which dislike writing ext3 and one Linux Box which needs to use a LTE stick to write a minisd. Everytime I test a rootfs, the filesystem is destroyed :( Also, I have not yet soldered a serial bridge to one of my cameras, so I am kind of blind during boot phase. |
Is there something wrong with my recipe to build the rootfs?
|
For me it seems correct |
The blue led was not lit at the very start of the boot process. |
I like the idea of an ext3 filesystem. I'm ok with mounting the sdcard on linux for hacking. Would have been nice though if "user" data like /DCIM still could be on a fat32 so that one could slap it into any laptop and get images and videos out that way. On the other hand, with ext3 and a package manager on could get rsync perhaps, to do the job. The limitations of fat32 became clear when I wanted to use scp: [root@DAFANG:bin]# dropbearmulti scp -p /system/sdcard/DCIM/timelapse/2018-08-09/2018-08-09_194817_001.jpg 10.10.10.18: Some symlinks may have fixed that problem, but, alas, no symlinks on fat32. |
Hello gents, I started to work on the scripts in #3 |
I had a couple of problems using this recipe. I have added the additional comments above. All working for me now. My primary reason for trying this rootfs version is to try and eliminate the 'timeout' issue that has been raised in many issues. I have four of these cameras, all Xiaomi Dafang 128MB models. All four have the issue from time to time (its intermittent and inconsistent). There have been various comments made around MQTT control/status being the cause but for me at least this is not the case. I have killed all of the running processes I can leaving just 'dropbear' and I still get the issue albeit much less often. I also get a significant number of dropped packets which leads me to believe the issue is either in the wireless driver or the wireless connection itself. I have upgraded one of the cameras to rootfs and am still getting the dropouts and dropped packets - dang. |
Hi @EliasKotlyar, @jmtatsch,
I succeeded installing my other Dafang with the new bootloader (thanks for your hard work on it)
I am currently trying to install the rootfs on the sdcard.
So my question now is: what shall we do about the path, for example /system/sdcard/ ?
I am just guessing, I am not sure all the implication of the new rootfs ...
Nik0
The text was updated successfully, but these errors were encountered: