![]() This license doesn¡¦t apply to embedded hardware devices such as NAS drives, Smart Routers and setup boxes which are not Tonido branded devices. License: Subject to Your acceptance of the TOS, CodeLathe hereby grants You a limited, personal, non-commercial, non-exclusive, non-sub licensable, non-assignable license to download, install and use Tonido on Your computer for the sole purpose of using the services and products provided by Tonido (the License). Who Can Accept TOS: You may not accept the TOS and therefore may not use Tonido if (a) you are not of legal age to form a binding contract with CodeLathe, or (b) you are a person barred from using Tonido under the laws any applicable country or other jurisdiction. YOU MAY NOT USE TONIDOPLUG UNLESS YOU ACCEPT THE TOS. YOU INDICATE YOUR ACKNOWLEDGMENT THAT YOU HAVE READ THIS AGREEMENT AND AGREE TO BE BOUND BY AND COMPLY WITH ITS TERMS. BY SETTING UP OR OTHERWISE USING THIS PRODUCT YOU MUST READ THE TERMS OF THIS AGREEMENT BEFORE SETTING UP OR USING THE TONIDOPLUG AND ITS SOFTWARE. You under the terms and conditions of this Terms of Service agreement (the TOS). I may try that myself at some point.Tonido, including its applications, devices (TonidoPlug), software and services, and the, , (collectively referred to as Tonido) are owned, published and operated by CodeLathe, LLC ( CodeLathe), and provided to May be as simple as the sshd socket, if sshd generates it's keys on 1st boot. Hope this helps someone and the appropriate maintainers know what to fix. # /etc/fstab: static file system information $this->bbcode_second_pass_code('', ~]# mount -o remount,rw / Update: Was also bit by the read-only file system. Not sure what I'd have done without that. I have 2 v1 tonidoplugs here with working (sort of) systems (enough to ssh into), so I was able to do the work on the target box. I had tried what I thought was a different image (may have messed it up), it would log me in, but never gave a shell prompt. Didn't help w/o the sshd work, and didn't need it with sshd. Adding the 2 lines to the end of /etc/network.d/wired-eth0 was not necessary. Kudos to you, my friend! Particularly helpful were the steps he listed to get the correct bits mounted in the chroot environment to create the sshd key. I can confirm thoughtcriminal's procedure from his post worked on one of my v1 tonidoplug. ![]() Great progress, though! thoughtcriminal Posts: 4 Joined: Sat 2:30 am It came up clean, and I'm still getting the Read-only file system error. So I tried "pacman -Syu" and I got this output:Įrror: failed to update core (unable to lock database)Įrror: failed to update extra (unable to lock database)Įrror: failed to update community (unable to lock database)Įrror: failed to update alarm (unable to lock database)Įrror: failed to update aur (unable to lock database)Įrror: failed to synchronize any databasesĮrror: failed to init transaction (unable to lock database)Įrror: could not lock database: Read-only file systemįollowing this thread (it's not quite the same, but worth a shot), I plugged the USB drive into my desktop machine and ran fsck. vi wouldn't open the file, though (no error message or anything). However, the first thing I tried was removing the two extra lines in /etc/network.d/wired-eth0 (to see if they were part of the solution or not). sda is my working (pre-systemd) arch drive, sdb is the partition I'm working on with a fresh arch image. Once I did that, I was able to successfully SSH in with the default root/root username/pass! Obviously enough it's because I hadn't run "ssh-keygen -A". $this->bbcode_second_pass_code('', 'ssh_exchange_identification: Connection closed by remote host') Then I tried booting it and I got this error when I tried to SSH: $this->bbcode_second_pass_code('', 'ln -s '/usr/lib/systemd/system/sshd.socket' '/etc/systemd/system//sshd.socket'') I ran "systemctl enable sshd.socket" as nicux recommended, and I got this output: I guess it's because I'm trying to chroot into an ARM system via an amd64 host, so I booted up my outdate but working (pre-systemd) tonido arch image via a USB hub, then I plugged in the new (non-working) USB drive along side it and chrooted in that way. Here's the details:Īt first, I plugged my arch USB drive into my main desktop, but I got this error when I tried to chroot:įailed to run command `/bin/bash': Exec format error
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |