![]() ![]() Single Board Computer (RPi4) with Armbianģ. I am thinking to create some app for Android that can connect over Bluetooth and send WiFi password to connect to wifi network instead of dealing with Ethernet.ġ. I connect it to the Etherenet and put into USB power supplier when I traveling. Resilio Sync to backup all my data to the remote storage gocryptfs (but key is not stored securely currently on my side).ĥ. Single Board Computer (Raspberry PI) with armbian on the board.Ĥ. Therefore I am using the following setup.ġ. And internet bandwidth usually not so good to upload everything immediately. There is no commercial background therefore I don't want to spend $$$ on TB of storage. ![]() I have a drone, a 360 action camera, a mirrorless camera, a phone - I took a lot of photos and video. ![]() Now i downgraded back to 2.3.7, and all is fine again.I am not a professional photographer or videographer, but I am a Software Engineer that works remotely and trying to travel as much as possible. FC: will verify that drive is mounted before proceeding path "eclipse_lin64/configuration//319/0/.cp/icons/help.gif" removal FC: will verify that drive is mounted before proceeding path "eclipse_lin64/configuration//584/0/.cp/icons/full" removal FC: will verify that drive is mounted before proceeding path "eclipse_lin64/features/_8.02051005/META-INF" removal FC: will verify that drive is mounted before proceeding path "eclipse_lin64/features/.ide_3.19.0.v20160315-1830/META-INF/ECLIPSE_.RSA" removal FC: will verify that drive is mounted before proceeding path "eclipse_lin64/features/_1.0902-0002/META-INF/ECLIPSE_.RSA" removal FC: will verify that drive is mounted before proceeding path "eclipse_lin64/features/.feature_3.0706-2237/META-INF/maven//org FC: will verify that drive is mounted before proceeding path "eclipse_lin64/features/_3.05221634/META-INF/maven/.features/ FC: will verify that drive is mounted before proceeding path "android-ndk-r8c/platforms/android-8/arch-arm/usr/include/asm-generic/4level-fixup.h" removal iotop shows that btsync generates 150KiB/s write speed on average, sync.log grows with speed of 50KiB/s to 100KiB/s while it's must be idle (nothing syncing), filled with some thing like this: Hard drives got crazy, they are under heavy seek load, with grinding sound almost constantly. ![]() I've got some trouble after update from 2.3.7 to 2.3.8 on my x86_64 Linux PCs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |