[Dev] ziptie questions

[John Tomawski]

Regarding the CentOS package:

I am running CentOS 5, with subversion-javahl-1.4.2-2.el5. Usually the
RHEL packages work with CentOS just as they would on RHEL.

Thanks,
John

-----Original Message-----
From: dev-bounces at ziptie.org [mailto:dev-bounces at ziptie.org] On Behalf
Of Kartick Suriamoorthy
Sent: Thursday, January 03, 2008 6:04 PM
To: ZipTie Development List
Cc: Bryan Brown
Subject: [Dev] ziptie questions


Rabih Sabbagh had asked the following questions and
the answers are inline (KS>>).

If anybody has more info, please reply to the dev.
mailing list.

Here are the issues I have:

1. Installing the svn-javahl on CentOS 4 (that what
we are using) I can't find the correct RPM and the YUM
does not know about it. If you have some steps I can
follow or how to build from source.

KS >> I don't have any experience on CentOS, so hopefully
KS >> somebody on the dev. list can help you out.

2. Passing parameters to my PERL script for example myTool.
I am calling the toolsProvider.executeScriptTool(toolName,deviceCSV,
arguments);
The arguments is a list of key=value. I am having problem
matching the keys with the command line parameters for the
PERL script which are specified in the myTool.properties file.

KS >> Can you run your server in debug mode and set break
KS >> points at ScripToolManager in the o.z.provider.tools
KS >> project. ScriptToolTask in the same project has a
KS >> method formatParameters which seems to handling input
KS >> params. It is a little bit difficult for me to figure
KS >> out what is going on from your description. Alternatively,
KS >> take a look at the iosPasswordChange.pl (and .properties)
KS >> tool to see how we handle input arguments.

3. For development, after I add my code and build the server.
Is it ok for me copy the dist directory to where I want it
running? It seems to be running ok. I just want to make sure
I am not missing anything.

KS >> I don't see anything wrong with it. The dist folder has
KS >> everything to run the server and client. I run from the
KS >> dist folder whenever I want to run the server/client from
KS >> my development environment.

4. For development, how do I start ZipTie so that the tftp server
is running and it binds to the correct port? For my understanding,
after running ZipTie tftp server all requests coming to port 69 will
be directed to 11069. Documentation on your website points to
ztwrapper. I can't get it to run with that.

KS >> I think I can partially help you with this. In your server
KS >> install directory, there should be a file called tftp.properties
KS >> in <server-install-dir>/osgi-config/network. You should be
KS >> able to edit that to set the port to 11069. Regarding the
KS >> actual work that needs to happen to get the port forwarding
KS >> to work in Linux - I will have to defer that to some of the
KS >> more Linux savvy folks on the dev. list.

Any documents or references to archived IRC discussion will be
greatly appreciated. Some of the references from search on your
website to the archived IRC discussion are broken after the move
to the new website.

KS >> I will ask Bryan Brown (the guy behind our cool website)
KS >> to take a look into the broken references.


Let me know if any of this helps.

Thanks,
Kartick

_______________________________________________
Dev mailing list
Dev at ziptie.org
http://mailman.ziptie.org/listinfo/dev

******************************************************************************
This email and any files transmitted with it are solely intended for the use of the addressee(s) and may contain information that is confidential and privileged.  If you receive this email in error, please advise us by return email immediately.  Please also disregard the contents of the email, delete it and destroy any copies immediately. 

Computershare Limited and its subsidiaries do not accept liability for the views expressed in the email or for the consequences of any computer viruses that may be transmitted with this email. 

This email is also subject to copyright.  No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner.
******************************************************************************