Quote:
Originally Posted by knc1
Surprise yourself then.
The only sshfs server is in the USBnet package. *
And the only way to start that, and to open a hole in the firewall is to start USB networking.
The reason is as I gave above.
The way our USBnetworking add-in is implemented, putting the USB cable into USBnetworking mode is hardcoded with the enabling of the servers and opening the firewall.
Read the scripting for yourself if you still doubt that -
see /mnt/us/usbnet/bin/* Where internally /mnt/us/* is same-same as "highest visible usb storage level" seen from outside.
And yes, I will be willing to match my six years experience with how we code our add-ins vs your, what?, six hours?
(*) If you are writing about your K3 (I presume you are, from the thread you are posting in), then there may be factory installed sshd/sshfsd in the 'diags' system.
But people are rarely interested in getting custom screensavers working in the 'diags' system so I am also assuming your writing about your K3 running the 'main' system.
If you are writing about your touch screen device(s) - then they never had factory sshd.
|
Thanks for the pointers. You may have deduced, I am as much in interested in knowing about the design (the why) as I am in the solution (or how).
Also - I meant no disrespect, or disapproval in how I phrased my "surprise". I know that functionality sometimes gets packaged in ways that might not seem to to fit a novice's expectation of scope based on "naming". I was only looking for confirmation.
BTW background is QA on Linux. The caution in my questions reflects experience that sometimes when you find problems you stop, get a +1 before trying to get further by "fixing" things. Shovels are great tools which work in both directions :-)
Your answer's given me the confidence to try again, and also observe a bit more how it's working which is part of my goal anyways.