Hello!
Someone else should chime in here, but see what what user and group
the entry is assigned to. For example the plugs I have here who're
running normal firmware will only allow the user who set things up to
log in to them.
I'm looking at how to enable the classic Pink one that arrived on
Wednesday here, to run Slackware on ARM. One of my pet peeves is that
they use the 2.6.22 kernel and that's too old for the mini root file
system images the developers make available...... Oddly enough one of
my better known releases was that of the 11.0 release which is
technically too old for the site. But it does make available a kernel
who's almost in sync with the plug.
Sorry to dump, but that's one of the reasons why I continued to stick
with the groups. The fact that the plug is on their hardware list
makes things work here.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature fought the Time Wars, time and again."
On Fri, Feb 13, 2015 at 11:25 AM, stevedemento@yahoo.com [nslu2-linux]
<nslu2-linux@yahoogroups.com> wrote:
>
>
>
> Gregg, I received the pl2303 and the cable a couple days ago and was able to get it working without too much fuss. You're right about the cable. The one I received is different than what was pictured in the howto and only has 3 wires (no yellow) instead of 4. Below is Qui's pictured cable from the article. But my white connector was wired different...
>
> Instead of White-Yellow-Red-Black, mine was wired Red-Black-White (no yellow). I left the white connector as is. The black connector I disassembled using a safety pin as he suggested. Then looking at the above picture I made the the following color substitutions: White->Red; Red->White; Yellow->Black. The idea is to maintain continuity between appropriate pins on the black and white connectors as illustrated in the picture. Hope that's clear enough.
>
> I installed the attached driver on my win xp laptop and set up putty as per the instructions. It worked straight away and I was able to undo my initial blunder by adding a command to start the sshd daemon in file rcS which runs on boot. Now I can use sshfs to mount and play my 4TB of music remotely.
>
> I have one remaining problem though. It only seems to work if I sshfs as the root user:
>
> sshfs -p 22222 root@ip_address: mountpoint_folder --> this works fine
>
> sshfs -p 22222 user@ip_address: mountpoint_folder --> this fails with error: "remote host has disconnected"
>
> An important note: ssh login works fine for both root and user!
>
> Even on an obscure port like 22222 I don't like connecting as root (I would actually like to disable root login), but I can seem get it to work as a regular user. This is my first time using sshfs. Can anyone point me in the right direction?
>
> -Steved
>
>
> ________________________________
> Posted by: stevedemento@yahoo.com
Posted by: Gregg Levine <gregg.drwho8@gmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (7) |
No comments:
Post a Comment