Alternatively, you can use our alternate method of making your application depend upon our application development package. The details are provided in our AXP Developer Guide section: ¿Accessing the Guest Operating System¿. I¿ll take a look at this issue you¿re seeing in AXP 1.5.2



Thanks,



Brett

Custom Application Engineer



From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Wednesday, March 10, 2010 10:14 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Jacek Materna in Application eXtension Platform (AXP) - Technical Questions: Migration from 1.5.1 to 1.5.2 issue



Jacek Materna has created a new message in the forum "Technical Questions":
--------------------------------------------------------------
Have a fully working deployable package on 1.5.1 with:

login.sh
#!/bin/bash

/bin/bash --login

post-install.sh
#! /bin/sh

ln -s /bin/bash /bin/console

Works correctly on 1.5.1 VMWare.

Rebuilt recently with 1.5.2 cleanly and deploying on 1.5.2 Vmware. Everything is fine except connect console reports error. Namely, error message:
execvp("/bin/console") - file not found. punts be back to CLI console.

Image is working fine via show process, etc. Any way to bypass connect console and go directly into image ?

-J


--
To respond to this post, please click the following link:
<http://developer.cisco.com/web/axp/forums/-/message_boards/message/2029007>
or simply reply to this email.

Hi Jacek,
 
Glad you got this console access issue resolved.  We'd like to investigate this issue further to determine the root cause.  What steps did you take to resolve this issue?  Did you need to change anything in your postinstall script?
 
Thanks,
 
Brett