This works. No problem. I see the devices with owdir from a remote machine.
Must be something with the USB then. The Phrozen build works 100% though. Any patches you applied for the Phrozen which I might have missed for the CrisOS version ? On Thu, October 30, 2008 11:48, Paul Alfille wrote: > Well, an easy test to see if it's the USB (as you seem to think) is to > try with the FAKE adapter: > > owserver --fake=10 -p 3000 --foreground --error_level 9 --error_print 2 > > > On Thu, Oct 30, 2008 at 6:36 AM, Jos Hartman > <[EMAIL PROTECTED]>wrote: > > >> >> Hallo >> >> >> Another OWFS / Fox /USB problem. >> >> >> I could get libusb and owfs (owlib,owserver) to compile. I used the >> libusb that came with CrisOS (version 0.1.12). >> >> I have used a version of OWFS which I found on www.mag.cx and then >> ported it to i686. However, I am not sure if this was the correct idea. >> >> When Fox boots, I log in as root and then try to run owserver with a >> USB >> device. Command is as follows: >> >> owserver -u all -p 3000 --foreground --error_level 9 --error_print 2 >> Output is: >> CONNECT: GetAddrInfo error Servname not supported for ai_socktype >> CONNECT: Cannot open server at all >> CALL: PARSENAME path=[] >> Segmentation fault >> # >> >> >> > -- Jos Hartman CAVOK Software Systems GmbH Windentalstrasse 356 CH-5704 Egliswil Switzerland Web: http://www.cavok.eu.com Tel: +41 62 775 09 12 Fax: +41 79 676 11 23 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
