If needed your package may include some scripts that will be invoked by the package maintenance system. This will prevent the package management system from automatically overwriting configuration changes when the user upgrades the package. If your package has any configuration files, then create a file CONTROL/conffiles which lists the absolute path of each configuration file, (as it will appear on the installed system), one per line. The meaning of each of the fields will be given later in this document. Optional fields include Priority, Section, and Depends. Required fields are Package, Version, Architecture, Source, Maintainer, and Description. Inside CONTROL create a file named control with lines of the form 'Field: value'. Now, change the following line of the pms_config.ini which you can find in the Server2Go folder.Ĭreate the directory structure and files you want to appear on the mvBlueLYNX.Ĭreate a directory named CONTROL at the top-level of this directory structure. Please follow these steps, to get the webserver running:Įxtract the Server2Go tool on an USB stick.Īfterwards, a htdocs folder is available.Ĭopy the IPK packages you want to install/upgrade in the htdocs folder. The tool is called Server2Go and can be downloaded here (the Micro-Package is enough for this type of installation and it is a self-extracting EXE file): If you have neither an internet access nor the VMware locally nor a webserver available, there is still a possibility to install IPK packages. The path to the directory can be entered in the ipk.conf of device ( /var/www/ppc_603e for mvBlueLYNX IPK packages /var/www/ppc_6xx for mvBlueLYNX-M7 and mvBlueCOUGAR-P IPK packages). The only thing you have to know is the IP address of the Virtual Machine (VMware). The Apache webserver of the Virtual Machine (VMware) makes them available and by using a browser you can navigate through the directories. var/www/ppc_6xx # for mvBlueLYNX-M7 and mvBlueCOUGAR-P IPK packages var/www/ppc_603e # for mvBlueLYNX IPK packages To install a package file called mvstest.ipk: Package installation scripts from prompting. force-defaults Use default options for questions asked by ipkg. force-depends Make dependency checks warnings instead of errors dest package installation, removal, upgrading.Ĭonfiguration file, (but can also be a directoryįorce Options (use when ipkg is too smart for its own good):

Status ] Display all/some status fields for or allĭepends Print uninstalled package dependencies for Info ] Display all/some info fields for or all

List List available packages and descriptions

Install Download and install (and dependencies) Upgrade Upgrade all installed packages to latest version

Ipk files download