WebOS Internals - User contributions [en]

Building Apps and Kernels

2011-09-03T18:11:53Z

Cyclic: /* Libraries */

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.

It's a good idea to first take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
</pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles. The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.

Let's start by simply compiling libxcb and take a look at the different pieces involved in getting the library to compile properly. If you crack open the Makefile for libxcb:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

You should see the name of the project, the version number for libxcb (this is used to download the package from the tar) and the SRC_BZ2 url. The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing the library into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>
'''Note:''' some packages might need additional work to compile (e.g. compiling libxcb requires that you create the full path for the documentation before it will install properly /usr/local/share/doc/libxcb/tutorial).

Now when you want to configure your own application or library outside of the toolchain or preware directory (such as a library or application you downloaded or are using Eclipse to develop) simply cd into that source directory and enter the toolchain:
<pre>
sb2 -M /srv/preware/cross-compile/staging/mapping-armv7
./configure
make all
</pre>
or
<pre>
cmake .
make
</pre>

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Building Apps and Kernels

2011-09-03T18:07:33Z

Cyclic:

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.

It's a good idea to first take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
</pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles. The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.

Let's start by simply compiling xproto and take a look at the different pieces involved in getting the library to compile properly. If you crack open the Makefile for xproto:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

You should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url. The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing the library into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>
'''Note:''' some packages might need additional work to compile (e.g. compiling libxcb requires that you create the full path for the documentation before it will install properly /usr/local/share/doc/libxcb/tutorial).

Now when you want to configure your own application or library outside of the toolchain or preware directory (such as a library or application you downloaded or are using Eclipse to develop) simply cd into that source directory and enter the toolchain:
<pre>
sb2 -M /srv/preware/cross-compile/staging/mapping-armv7
./configure
make all
</pre>
or
<pre>
cmake .
make
</pre>

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Building Apps and Kernels

2011-09-03T17:57:13Z

Cyclic: /* Libraries */

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.

It's a good idea to first take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
</pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles. The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.

Let's start by simply compiling xproto and take a look at the different pieces involved in getting the library to compile properly. If you crack open the Makefile for xproto:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

You should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url. The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing the library into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>
'''Note:''' some packages might need additional work to compile (e.g. compiling libxcb requires that you create the full path for the documentation before it will install properly /usr/local/share/doc/libxcb/tutorial).

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Building Apps and Kernels

2011-09-03T17:55:36Z

Cyclic: /* Libraries */

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.

First, you it's a good idea to take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
</pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles. The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.

Let's start by simply compiling xproto and take a look at the different pieces involved in getting the library to compile properly. If you crack open the Makefile for xproto:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

You should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url. The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing the library into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>
'''Note:''' some packages might need additional work to compile (e.g. compiling libxcb requires that you create the full path for the documentation before it will install properly /usr/local/share/doc/libxcb/tutorial).

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Building Apps and Kernels

2011-09-03T05:49:05Z

Cyclic:

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

You might also be interested in using additional libraries in your projects. Your best bet is to locate source for your code in some of the existing libraries used in other packages. Let's start by simply compiling libxcb and take a look at the different pieces involved in getting the library to compile properly.

First, you might want to take a look at the directories for all of the common libraries already downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
</pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other make files for both downloading source for the library and various dependencies of your project. Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

If you crack open the Makefile for xproto you should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url (you can change this URL to point to the package that you're looking to compile:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Just keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing it into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Building Apps and Kernels

2011-09-03T05:47:58Z

Cyclic: Added info for libraries.

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Setup''' ==
Depending on what you're building you might need some of the prereq's from here:
http://www.webos-internals.org/wiki/WebOS_Internals_PDK

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time or if you already have the toolchain installed, please see below
<pre>
cd build
make toolchain
</pre>

Please see the notes if you already have the correct toolchain installed and do not want to download it again.

== '''Apps''' ==

Package up preware.
<pre>
cd /srv/preware/build/apps/preware
make package
</pre>

== '''Kernels''' ==

Package up UberKernel.
<pre>
cd /srv/preware/build/kernels/uber-kernel-touchpad
make package
</pre>

Testing your kernel
you will find your kernel in
<pre>
build/src-3.0.2-22/linux-2.6.35/arch/arm/boot
</pre>
you can boot it using memboot. to do this do the following 
1) turn off the touchpad 
2) connect it to your machine 
3) press the Volume Up key and power on the device, you should see a giant USB logo on the device 
4) novacom boot mem:// < uImage

== '''Libraries''' ==
Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.

You might also be interested in using additional libraries in your projects. Your best bet is to locate source for your code in some of the existing libraries used in other packages. Let's start by simply compiling libxcb and take a look at the different pieces involved in getting the library to compile properly.

First, you might want to take a look at the directories for all of the common libraries already downloaded when you setup your toolchain:
<pre>
cd /srv/preware/cross-compile/packages/common/x
ls
<pre>
Each directory here is a separate library. The library folder contains a Makefile, which links to other make files for both downloading source for the library and various dependencies of your project. Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.

If you crack open the Makefile for xproto you should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url (you can change this URL to point to the package that you're looking to compile:
<pre>
nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
</pre>

<pre>
NAME = libxcb
VERSION = 1.7

DEPENDS = x/xcbproto \
x/libpthread-stubs \
x/xau

SRC_BZ2 = http://xcb.freedesktop.org/dist/${NAME}-${VERSION}.tar.bz2
...
</pre>

For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory). The process is pretty straight forward from here. Just keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.

If you want to test out compiling and staging (installing it into your target architecture /usr/lib and include folder like we mention above), just type:
<pre>
make stage package
</pre>

Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to. That's about all there is to it!

== '''Notes''' ==

If you already have the correct version of the toolchain installed for the device you are targeting you can symlink it to the proper location (e.g. the touchpad needs the Sourcery G++ Lite 2009q1-203 toolchain).

If it is already installed you can symlink it into the build area:

<pre>
cd toolchain/cs09q1armel
mkdir build
cd build
ln -s <location of toolchain> arm-2009q1
</pre>

== '''Samples''' ==

After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

Application:OpenSSH

2011-09-01T06:59:17Z

Cyclic: /* Generate Keys from Mac OSX Method (tested with Lion) */

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

== Generate Keys from Mac OSX Method (tested with Lion) ==

Start a new terminal session in Mac OS and su to root. Once in root on your mac:
<pre>
/opt/bin/ssh-keygen
</pre>

Accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

<pre>
mv /var/root/.ssh/id_rsa.pub /var/root/.ssh/authorized_keys
</pre>

Now that you have your private and public keys, you need to copy them over to your device. Attach your TouchPad as a USB and copy the files:
<pre>
cp /var/root/.ssh/* /Volumes/HP\ TouchPad/
</pre>

Now disconnect the TouchPad and load up a terminal on your TouchPad. Once in a terminal, you are going to move the key files into the right locations and set permissions on the appropriate files.

<pre>
cp /media/internal/id_rsa /home/root/.ssh/
cp /media/internal/authorized_keys /home/root/.ssh/
</pre>

This is necessary to load the keys.
<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

It's required that the upstart script is modified. As of 08/28/11, there were some issues with upstart not working and OpenSSH not loading.
<pre>
vi /var/palm/event.d/mobi.optware.openssh
</pre>
Comment out the existing start and stop commands and add the new stuff below it. As of writing this, it's still not clear why there were issues starting with the org.webosinternals.optware dependency, so feel free to update with better script or more details:
<pre>
#start on stopped finish and started org.webosinternals.optware
#stop on runlevel [!2]

start on stopped finish
# and started org.webosinternals.optware

# Stop when the Software Update tool is about to install an update.
# upstart restarts the job when installation is complete.
stop on started start_update
</pre>
Exit out of vi and save
<pre>
qw!
</pre>

You can ''test'' that sshd starts and view any key errors by typing:
<pre>
/opt/sbin/sshd -D
</pre>

If you receive an error, "Permissions 0777 for '/opt/etc/openssh/ssh_host_rsa_key' are too open." you should change the permissions on this key file to 600:
<pre>
chmod 600 /opt/etc/openssh/ssh_host_rsa_key
</pre>
and 700 on the parent directory
<pre>
chmod 700 /opt/etc/openssh
</pre>

If you receive a message, opt/sbin/sshd -D Could not load host key: /opt/etc/openssh/ssh_host_ecdsa_key, you can create the key manually:
<pre>
/opt/bin/ssh-keygen -t ecdsa -f /opt/etc/openssh/ssh_host_ecdsa_key -N ''
chmod 600 /opt/etc/openssh/ssh_host_ecdsa_key
</pre>

Once this is done, you should be able to start sshd:
<pre>
start mobi.optware.openssh
</pre>

Test connecting remotely from your Mac (the -vvv option is for verbose debug messages, which you can remove if everything works):
<pre>
su
ssh <touchpad ip> -vvv
</pre>

Use the password you used to create the key at the beginning.

If you have any other problems, be sure to take a look at the log files on your TouchPad:
<pre>
grep ssh /var/log/messages
</pre>

Check that the service is running:
<pre>
ps aux | grep sshd
status mobi.optware.openssh
</pre>

Try connecting to the TouchPad locally:
<pre>
ssh localhost
</pre>

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

=== Setting up ExpanDrive (SftpDrive) ===

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Building Apps and Kernels

2011-08-29T15:11:36Z

Cyclic:

Building Apps and Kernels

2011-08-29T15:10:45Z

Cyclic: Added Samples

Application:OpenSSH

2011-08-28T23:01:19Z

Cyclic: /* Generate Keys from Mac OSX Method (tested with Lion) */

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

== Generate Keys from Mac OSX Method (tested with Lion) ==

Start a new terminal session in Mac OS and su to root. Once in root on your mac:
<pre>
/opt/bin/ssh-keygen
</pre>

Accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

<pre>
mv /var/root/.ssh/id_rsa.pub /var/root/.ssh/authorized_keys
</pre>

Now that you have your private and public keys, you need to copy them over to your device. Attach your TouchPad as a USB and copy the files:
<pre>
cp /var/root/.ssh/* /Volumes/HP\ TouchPad/
</pre>

Now disconnect the TouchPad and load up a terminal on your TouchPad. Once in a terminal, you are going to move the key files into the right locations and set permissions on the appropriate files.

<pre>
cp /media/internal/id_rsa /home/root/.ssh/
cp /media/internal/authorized_keys /home/root/.ssh/
</pre>

This is necessary to load the keys.
<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

It's required that the upstart script is modified. As of 08/28/11, there were some issues with upstart not working and OpenSSH not loading.
<pre>
vi /var/palm/event.d/mobi.optware.openssh
</pre>
Comment out the existing start and stop commands and add the new stuff below it. As of writing this, it's still not clear why there were issues starting with the org.webosinternals.optware dependency, so feel free to update with better script or more details:
<pre>
#start on stopped finish and started org.webosinternals.optware
#stop on runlevel [!2]

start on stopped finish
# and started org.webosinternals.optware

# Stop when the Software Update tool is about to install an update.
# upstart restarts the job when installation is complete.
stop on started start_update
</pre>
Exit out of vi and save
<pre>
qw!
</pre>

You can ''test'' that sshd starts and view any key errors by typing:
<pre>
/opt/sbin/sshd -D
</pre>

If you receive an error, "Permissions 0777 for '/opt/etc/openssh/ssh_host_rsa_key' are too open." you should change the permissions on this key file to 600:
<pre>
chmod 600 /opt/etc/openssh/ssh_host_rsa_key
</pre>
and 700 on the parent directory
<pre>
chmod 700 /opt/etc/openssh
</pre>

If you receive a message, opt/sbin/sshd -D Could not load host key: /opt/etc/openssh/ssh_host_ecdsa_key, you can create the key manually:
<pre>
ssh-keygen -t ecdsa -f /opt/etc/openssh/ssh_host_ecdsa_key -N ''
chmod 600 /opt/etc/openssh/ssh_host_ecdsa_key
</pre>

Once this is done, you should be able to start sshd:
<pre>
start mobi.optware.openssh
</pre>

Test connecting remotely from your Mac (the -vvv option is for verbose debug messages, which you can remove if everything works):
<pre>
su
ssh <touchpad ip> -vvv
</pre>

Use the password you used to create the key at the beginning.

If you have any other problems, be sure to take a look at the log files on your TouchPad:
<pre>
grep ssh /var/log/messages
</pre>

Check that the service is running:
<pre>
ps aux | grep sshd
status mobi.optware.openssh
</pre>

Try connecting to the TouchPad locally:
<pre>
ssh localhost
</pre>

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

=== Setting up ExpanDrive (SftpDrive) ===

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Application:OpenSSH

2011-08-28T22:59:47Z

Cyclic:

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

== Generate Keys from Mac OSX Method (tested with Lion) ==

Start a new terminal session in Mac OS and su to root. Once in root on your mac:
<pre>
/opt/bin/ssh-keygen
</pre>

Accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

<pre>
mv /var/root/.ssh/id_rsa.pub /var/root/.ssh/authorized_keys
</pre>

Now that you have your private and public keys, you need to copy them over to your device. Attach your TouchPad as a USB and copy the files:
<pre>
cp /var/root/.ssh/* /Volumes/HP\ TouchPad/
<pre>

Now disconnect the TouchPad and load up a terminal on your TouchPad. Once in a terminal, you are going to move the key files into the right locations and set permissions on the appropriate files.

<pre>
cp /media/internal/id_rsa /home/root/.ssh/
cp /media/internal/authorized_keys /home/root/.ssh/
</pre>

This is necessary to load the keys.
<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

It's required that the upstart script is modified. As of 08/28/11, there were some issues with upstart not working and OpenSSH not loading.
<pre>
vi /var/palm/event.d/mobi.optware.openssh
</pre>
Comment out the existing start and stop commands and add the new stuff below it. As of writing this, it's still not clear why there were issues starting with the org.webosinternals.optware dependency, so feel free to update with better script or more details:
<pre>
#start on stopped finish and started org.webosinternals.optware
#stop on runlevel [!2]

start on stopped finish
# and started org.webosinternals.optware

# Stop when the Software Update tool is about to install an update.
# upstart restarts the job when installation is complete.
stop on started start_update
</pre>
Exit out of vi and save
<pre>
qw!
</pre>

You can ''test'' that sshd starts and view any key errors by typing:
<pre>
/opt/sbin/sshd -D
</pre>

If you receive an error, "Permissions 0777 for '/opt/etc/openssh/ssh_host_rsa_key' are too open." you should change the permissions on this key file to 600:
<pre>
chmod 600 /opt/etc/openssh/ssh_host_rsa_key
</pre>
and 700 on the parent directory
<pre>
chmod 700 /opt/etc/openssh
</pre>

If you receive a message, opt/sbin/sshd -D Could not load host key: /opt/etc/openssh/ssh_host_ecdsa_key, you can create the key manually:
<pre>
ssh-keygen -t ecdsa -f /opt/etc/openssh/ssh_host_ecdsa_key -N ''
chmod 600 /opt/etc/openssh/ssh_host_ecdsa_key
</pre>

Once this is done, you should be able to start sshd:
<pre>
start mobi.optware.openssh
</pre>

Test connecting remotely from your Mac (the -vvv option is for verbose debug messages, which you can remove if everything works):
<pre>
su
ssh <touchpad ip> -vvv
</pre>

Use the password you used to create the key at the beginning.

If you have any other problems, be sure to take a look at the log files on your TouchPad:
<pre>
grep ssh /var/log/messages
</pre>

Check that the service is running:
<pre>
ps aux | grep sshd
status mobi.optware.openssh
</pre>

Try connecting to the TouchPad locally:
<pre>
ssh localhost
</pre>

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

=== Setting up ExpanDrive (SftpDrive) ===

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Application:OpenSSH

2011-08-28T22:58:26Z

Cyclic:

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

== Generate Keys from Mac OSX Method (tested with Lion) ==

Start a new terminal session in Mac OS and su to root. Once in root on your mac:
<pre>
/opt/bin/ssh-keygen
</pre>

Accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

<pre>
mv /var/root/.ssh/id_rsa.pub /var/root/.ssh/authorized_keys
</pre>

Now that you have your private and public keys, you need to copy them over to your device. Attach your TouchPad as a USB and copy the files:
<pre>
cp /var/root/.ssh/* /Volumes/HP\ TouchPad/
<pre>

Now disconnect the TouchPad and load up a terminal on your TouchPad. Once in a terminal, you are going to move the key files into the right locations and set permissions on the appropriate files.

<pre>
cp /media/internal/id_rsa /home/root/.ssh/
cp /media/internal/authorized_keys /home/root/.ssh/
</pre>

This is necessary to load the keys.
<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

It's required that the upstart script is modified. As of 08/28/11, there were some issues with upstart not working and OpenSSH not loading.
<pre>
vi /var/palm/event.d/mobi.optware.openssh
</pre>
Comment out the existing start and stop commands and add the new stuff below it. As of writing this, it's still not clear why there were issues starting with the org.webosinternals.optware dependency, so feel free to update with better script or more details:
<pre>
#start on stopped finish and started org.webosinternals.optware
#stop on runlevel [!2]

start on stopped finish
# and started org.webosinternals.optware

# Stop when the Software Update tool is about to install an update.
# upstart restarts the job when installation is complete.
stop on started start_update
</pre>
Exit out of vi and save
<pre>
qw!
</pre>

You can ''test'' that sshd starts and view any key errors by typing:
<pre>
/opt/sbin/sshd -D
</pre>

If you receive an error, "Permissions 0777 for '/opt/etc/openssh/ssh_host_rsa_key' are too open." you should change the permissions on this key file to 600:
<pre>
chmod 600 /opt/etc/openssh/ssh_host_rsa_key
</pre>
and 700 on the parent directory
<pre>
chmod 700 /opt/etc/openssh
</pre>

If you receive a message, opt/sbin/sshd -D Could not load host key: /opt/etc/openssh/ssh_host_ecdsa_key, you can create the key manually:
<pre>
ssh-keygen -t ecdsa -f /opt/etc/openssh/ssh_host_ecdsa_key -N ''
chmod 600 /opt/etc/openssh/ssh_host_ecdsa_key
</pre>

Once this is done, you should be able to start sshd:
<pre>
start mobi.optware.openssh
</pre>

Test connecting remotely from your Mac (the -vvv option is for verbose debug messages, which you can remove if everything works):
<pre>
su
ssh <touchpad ip> -vvv
</pre>

Use the password you used to create the key at the beginning.

If you have any other problems, be sure to take a look at the log files on your TouchPad:
<pre>
grep ssh /var/log/messages
</pre>

Check that the service is running:
<pre>
ps aux | grep sshd
status mobi.optware.openssh
</pre>

Try connecting to the TouchPad locally:
<pre>
ssh localhost
</pre>

== Setting up ExpanDrive (SftpDrive) ==

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Application:OpenSSH

2011-08-28T22:57:02Z

Cyclic: added mac os instructions and some troubleshooting steps.

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

== Generate Keys from Mac OSX Method (tested with Lion) ==

Start a new terminal session in Mac OS and su to root. Once in root on your mac:
<pre>
/opt/bin/ssh-keygen
</pre>

Accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

<pre>
mv /var/root/.ssh/id_rsa.pub /var/root/.ssh/authorized_keys
</pre>

Now that you have your private and public keys, you need to copy them over to your device. Attach your TouchPad as a USB and copy the files:
<pre>
cp /var/root/.ssh/* /Volumes/HP\ TouchPad/
<pre>

Now disconnect the TouchPad and load up a terminal on your TouchPad. Once in a terminal, you are going to move the key files into the right locations and set permissions on the appropriate files.

<pre>
cp /media/internal/id_rsa /home/root/.ssh/
cp /media/internal/authorized_keys /home/root/.ssh/
</pre>

This is necessary to load the keys.
<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

It's required that the upstart script is modified. As of 08/28/11, there were some issues with upstart not working and OpenSSH not loading.
<pre>
vi /var/palm/event.d/mobi.optware.openssh
</pre>
Comment out the existing start and stop commands and add the new stuff below it. As of writing this, it's still not clear why there were issues starting with the org.webosinternals.optware dependency, so feel free to update with better script or more details:
<pre>
#start on stopped finish and started org.webosinternals.optware
#stop on runlevel [!2]

start on stopped finish
# and started org.webosinternals.optware

# Stop when the Software Update tool is about to install an update.
# upstart restarts the job when installation is complete.
stop on started start_update
</pre>
Exit out of vi and save
<pre>
qw!
</pre>

You can ''test'' that sshd starts and view any key errors by typing:
<pre>
/opt/sbin/sshd -D
</pre>

If you receive an error, "Permissions 0777 for '/opt/etc/openssh/ssh_host_rsa_key' are too open." you should change the permissions on this key file to 600:
<pre>
chmod 600 /opt/etc/openssh/ssh_host_rsa_key
</pre>
and 700 on the parent directory
<pre>
chmod 700 /opt/etc/openssh
</pre>

If you receive a message, opt/sbin/sshd -D Could not load host key: /opt/etc/openssh/ssh_host_ecdsa_key, you can create the key manually:
<pre>
ssh-keygen -t ecdsa -f /opt/etc/openssh/ssh_host_ecdsa_key -N ''
chmod 600 /opt/etc/openssh/ssh_host_ecdsa_key
</pre>

Once this is done, you should be able to start sshd:
<pre>
start mobi.optware.openssh
</pre>

Test connecting remotely from your Mac (the -vvv option is for verbose debug messages, which you can remove if everything works):
<pre>
su
ssh <touchpad ip> -vvv
</pre>

Use the password you used to create the key at the beginning.

If you have any other problems, be sure to take a look at the log files on your TouchPad:
<pre>
grep ssh /var/log/messages
</pre>

Check that the service is running:
<pre>
ps aux | grep sshd
status mobi.optware.openssh
</pre>

Try connecting to the TouchPad locally:
<pre>
ssh localhost
</pre>

=== Setting up ExpanDrive (SftpDrive) ===

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Application:OpenSSH

2011-08-28T07:20:52Z

Cyclic: /* Generate Keys from webOS Method */

==Introduction==

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on.

OpenSSH is available for installation in Preware. Just Type "OpenSSH" in the Preware home screen to search for and install the package.

Please refer to the [http://www.openssh.com/ OpenSSH Home Page] and read the [http://www.openssh.com/manual.html OpenSSH Manual Pages] before using this package.

There are two ways to generate the keys below. The PC one assumes you have a user account name and password to gain access with putty I assume it is not possible to complete the steps for that method without setting up a user account. I find the webOS method to be much easier to follow. And I imagine if you are new to linux and accessing linux on webOS then you will find the webOS method is the one you will want to follow. I also recommend the webOS method if you have trouble following the PC method or find it too wordy.

==Generate Keys from Windows PC Method==

If you are connecting to your webOS device from a Windows host computer, please read the [http://unixwiz.net/techtips/putty-openssh.html Secure Linux/UNIX access with PuTTY and OpenSSH Tech Tip] and follow those instructions for generating your SSH keys. For the section "Install public key on Linux system", you will need to put the "Public Key for pasting into OpenSSH authorized_keys file" into a /home/root/.ssh/authorized_keys file.

Optware installs openssh under /opt, so you should replace any references to /bin, /sbin, and /etc in the OpenSSH documentation with /opt/bin, /opt/sbin and /opt/etc respectively.

=== Setting up ExpanDrive (SftpDrive) ===

''Note: This requires access to the device's file system by any means.''
* Open ExpanDrive
* Click "New drive..."
* Type a name into the "Drive Name" box.
* Type in the IP address of the device in the "Server" box.
* Type "root" into the "Username" box.
* Choose "Use a public key to log in..." from the "Authentication" drop-down.
* Click "Create New Key Pair"
* Choose "RSA (ssh-rsa)" from the "Key type" drop-down.
* Click "Create Key Pairs".
* Click "Ok".
* Click "Export current Key Pair"
* Click both "Export Private Key" and "Export Public Key" and save the files somewhere (remember where you saved them) and click "Ok".
* Open the .pub file you saved in the previous step using a plain text editor.
* Copy the contents of the entire file and paste it into "/var/home/root/.ssh/authorized_keys" (on the device) on the next line and save it.
* Go back to ExpanDrive and click "Ok" on the still open "Public Key Authentication Properties" dialog.
* Choose "Show the entire server" from the "Directory" drop-down.
* Click "Connect" to connect and save the configuration.
* After the connection process is complete, a new Explorer window will open and you will be in the "%DriveLetter%:\var\home\root" directory.

==Generate Keys from webOS Method==

Launch Preware and install [http://www.webos-internals.org/wiki/Application:Terminal Terminal] if you haven't previously installed it. If Terminal does not work, try XTerm instead. It will be used to create your secure SSH keys for use with OpenSSH directly on your webOS device. Once Terminal is installed launch it and follow these steps:

To go to the root directory type:

cd /

Then type:

/opt/bin/ssh-keygen

to create the private and public keys. After a short time (about a minute) accept the default filename by pressing Enter at the prompt. Enter a passphrase for your private key file. You will use this passphrase later, so remember it. After the key file is generated type:

mv /home/root/.ssh/id_rsa.pub /home/root/.ssh/authorized_keys

to move the public key to become the /home/root/.ssh/authorized_keys file.

Now the secret key needs to be transferred to the PC you want to access linux on webOS from. First copy the secret key to the area accessible from drive mode. To do this, type:

cp /home/root/.ssh/id_rsa /media/internal/id_rsa

We are all done using Terminal so you can close it by tossing it off the top of the screen like you would for any other application. Next you need to connect your device to the PC with the USB cable and tap drive mode. Once drive mode is active open the drive letter for the device on your PC (ex. "PALM PRE (E:)"). Copy the "id_rsa" file to your PC somewhere you will remember it's location (ex. to the desktop). You can also copy the file with a word document extension ".doc" and email it to yourself. You will have to rename it back to "id_rsa".

cp /home/root/.ssh/id_rsa /media/internal/id_rsa.doc

===Using the key with PuTTY===

If you have the webOS SDK installed you will already have PuTTY (in \SDK\bin\ of the folder the SDK was installed in). If you don't have the webOS SDK installed you can install it to get PuTTY or you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. You will also need PuTTYgen. If you will be using winSCP you already have it (in start menu>winSCP>key tools) or download it from the same site as PuTTY. If this is your first time using PuTTY to access linux on webOS or wish to verify the configuration is correct please follow these steps:

*Open PuTTY.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100).
*Enter 22 for the port number.
*Select the radio button for SSH
*Select the Data section under Connection on the left.
*Enter root for the auto-login username.
*Select the Auth section under SSH under Connection on the left.
*Leave PuTTY open here and follow these steps:
**Open PuTTYgen.
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to PuTTY where we left off.
*Click the Browse button for private key file.
*Select the ppk file you made with PuTTYgen and click open.
*Select Session on the left.
*Enter a name in the Saved Session box and click the save button.
**This will allow you to load the settings for future use.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Click open in PuTTY to connect.

If everything is configured correctly you should see the following in the terminal window on your pc:

Using username "root".
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":

*Enter the passphrase you created during key generation.

You should now see:

root@palm-webos-device:/var/home/root#

Congratulations you now have access to linux on your webOS device. You may now begin using the command prompt to work with anything you need or want to use the command prompt for. There is all sorts of stuff you can use it for so if you haven't already check out the rest of the webos-internals site for a number of things you can do. You may also want to setup winSCP for a explorer like windows interface to access and work with files etc as well.

===Using the Filezilla SFTP Client===

Make sure you have installed the OpenSSH SFTP server from Preware

For SFTP using SSH2, FileZilla utilizes the excellent [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] tools. To allow the use of RSA / DSA key files with Filezilla, you'll need to download one more tool from PuTTY: Pageant.

Make sure you have converted your key to PuTTY's PPK format listed above.

Now run Pageant. In your system tray, you'll see the Pageant icon appear. Right-click the icon and select "Add Key" and select your private key (PPK) file. Follow the prompt to enter your pass phrase and you're done.

Now simply launch FileZilla and connect to your server using SFTP using SSH with a root and an empty password. Don't forget to close pageant when you're done.

As you may or may not know, FileZilla can be easily carried around on portable media such as a USB stick and used from any PC. This also applies to the PuTTY tools, so if you stick Pageant and your PPK key file on to, for example, a USB stick, you can now access your server from any Windows PC.

==== Filezilla Alternative Method Using Unprotected Key====

In the Edit - Settings menu of the FileZilla client, you can [Add key file...] under Connection - SFTP, and FileZilla can use the public key authentication in the site manager with the 'Interactive' Logontype. However, the .ppk file is converted to unprotected one if the original .ppk file is password-protected (FileZilla can do that for you when importing the file). As of 3.3.2.1, a password-protected key file is not supported yet.

===Using the key with winSCP===

*Open winSCP.
*Enter the IP address assigned to your webOS device (ex. 192.168.1.100) in the host name box.
*Enter 22 for the port number.
*Enter root in the user name box.
*Leave winSCP open and follow these steps:
**Open PuTTYgen (startmenu>winSCP>key tools).
**Select the conversions menu.
**Select import key.
**Choose the id_rsa file you copied to the PC from your device and click open.
**Enter the passphrase you entered during key generation and click ok.
***You will see all sorts of information in the window at this point.
**Click the save private key button.
**Enter a name for it (no need to type the ppk extension) and save it somewhere you will remember it's location.
**Close PuTTYgen and go back to winSCP where we left off.
*Click the "..." button for the private key file box.
*Select the ppk file you made with PuTTYgen and click open.
*Click the save button and enter a name and click ok.
**This will allow you to load the settings for future use.
*You should now be seeing the stored sessions list with the session you just saved.
*Make sure your device's wifi is on.
**You can install nodoze to keep wifi on if need be.
*Select the session you saved and click the login button.
*Enter the passphrase you created during key generation.

If everything is configured correctly you should see a window with a list of folders similar to explorer. Congratulations you now have access to linux on your webOS device. You may now begin working with files on the device. You can do stuff like copy, delete, etc file like in windows. You can also edit files. Certain actions will require read write mode (mount -o remount,rw / entered at the command prompt in PuTTY or terminal, mount -o remount,ro / to go back to read only mode).

===Using the key with SSH in Terminal===

Put your private key file in the standard location ~/.ssh/id_rsa on the machine you are using to connect to the Pre or you can inform ssh by using the -i switch as follow:

user@host:~$ ssh -i /path/to/private/key remoteuser@remotehost

===Enabling non-root Password logins via SSH using the command line===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the exec line and change

"PasswordAuthentication no"
to
"PasswordAuthentication yes"

The line should now look like this:

exec /opt/sbin/sshd -D -p 22 -o "PasswordAuthentication yes" -o "PermitRootLogin without-password"

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Do not change anything else. Now if you've created a username for yourself and set a password, you'll be able to log in with a password. After every Palm WebOS upgrade, you'll need to recreate any accounts other than root with adduser <account>, which will then prompt you to set a password.

Warning:
It is strongly suggested that you set up another ssh key for any additional users instead of using the password authentication method. Just follow the steps above.

===Enabling ssh over EVDO===

Access the command line on your Pre via Terminal, SSH, or Novaterm.

Type the following at the root prompt to allow write access to your / disk:

mount -o remount,rw /

Edit the mobi.optware.openssh file in the /etc/event.d/ directory. Find the iptables lines and remove the "-i eth0" clause. For example
/usr/sbin/iptables -D INPUT -i eth0 -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -i eth0 -p tcp --dport 222 -j ACCEPT
becomes
/usr/sbin/iptables -D INPUT -p tcp --dport 222 -j ACCEPT || /bin/true
/usr/sbin/iptables -I INPUT -p tcp --dport 222 -j ACCEPT

Save and exit with ZZ or :wq, then restart the openssh service as follows:

stop mobi.optware.openssh
start mobi.optware.openssh

Once you are finished make sure you make your / disk read-only again (this is the default):

mount -o remount,ro /

Building Apps and Kernels

2011-08-28T06:21:42Z

Cyclic: /* Apps */

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Apps''' ==

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time.
<pre>
cd build
make toolchain
</pre>

Package up preware.
<pre>
cd apps/preware
make package
</pre>

Building Apps and Kernels

2011-08-28T06:13:59Z

Cyclic:

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place. If you have not run through the [[WebOS Internals PDK]] wiki page, you should start there.

== '''Apps''' ==

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time.
<pre>
cd build
make toolchain
</pre>

Package up the toolchain.
<pre>
cd apps/preware
make package
</pre>

Building Apps and Kernels

2011-08-28T06:12:57Z

Cyclic: Initial creation.

If you are looking for instructions for building apps and kernels for WebOS, you have come to the right place.

== '''Apps''' ==

If you have not run through the [[WebOS_Internals_PDK]] document, you should start there.

Create the directory structure for the source:
<pre>
sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
</pre>

Pull down the app source with git.
<pre>
git clone git://git.webos-internals.org/preware/build.git
</pre>

After you have the source, you need to build the toolchain — this can take some time.
<pre>
cd build
make toolchain
</pre>

Package up the toolchain.
<pre>
cd apps/preware
make package
</pre>

Building DOOM with scratchbox2

2011-08-26T03:47:26Z

Cyclic:

[[Category:SDL]]

First, follow the tutorial [[WebOS Internals PDK]] to set up the cross compilation environment.

Next, download the sdlDOOM source code:

<pre>
wget http://www.libsdl.org/projects/doom/src/sdldoom-1.10.tar.gz
tar xzf sdldoom-1.10.tar.gz
cd sdldoom-1.10
</pre>

Now run scratchbox2 with the webos / pre mapping file:

<pre>
$ sb2 -M /srv/preware/cross-compile/staging/mapping-armv7
</pre>

NOTE: You should use armv6 if your target device is a Pixi.

You will get a different prompt indicating you are in a scratchbox shell, like:
<pre>
[SB2 mapping-armv7 armv7] $
</pre>

Run:

<pre>
./configure --with-sdl-prefix=/usr/local
make
</pre>

Build should complete successfully with no problems. Download a DOOM shareware WAD:

NOTE: If you receive an error "configure: error: *** SDL version 1.0.1 not found!", you will need to exit the sb2 command line by typing exit, then
<pre>
mkdir -p /usr/local/include/
cd /srv/preware/cross-compile/packages/dev-sdl
make -C libsdl ARCH=armv7 stage</pre>

Be patient. The compile can take 10 minutes. You should be able to cd into the doom directory and continue above at "Now run scratchbox2 with the webos / pre mapping file:"

<pre>
wget http://www.libsdl.org/projects/doom/data/doom1.wad.gz
gunzip doom1.wad.gz
</pre>

Copy the DOOM program binary and wad to root's home directory on the pre:
<pre>
scp doom doom1.wad root@pre:
</pre>

SSH to the device (novaterm would also work to get there, or an on-device terminal)
NOTE: You can also use the usb mode on the TouchPad. If you do use USB, you can find the copied files in /media/internal/
<pre>
ssh root@pre
</pre>

On the device, run DOOM:
<pre>
./doom
</pre>

Yay, it should now run. You may want to customize the code for better controls on the device.

Now let's package it up for all your friends to install. You should be back in your sdldoom-1.1.0 directory. For this, we'll use the Palm SDK, so make sure you have it installed.

First off: Unfortunately palm-package doesn't _quite_ make game packages properly. First, we want type to be "game" and palm-package doesn't understand that (will reject it as an invalid type in the 1.3.5 SDK). Secondly, the executables need to be set with executable permissions. For all this, we need a script to fix up the ipk for you.

palm-game-fix (I put it in /usr/local/bin and chmod 755 /usr/local/bin/palm-game-fix)
<pre>
#!/bin/bash
TMPDIR="fix-game-ipk-tmp.$$"
if [ ! -f "$1" ]; then echo "$1" not found; exit 1; fi
mkdir "$TMPDIR"; cd "$TMPDIR"
ar x "../$1"
tar xvzf data.tar.gz
cd usr/palm/applications/*
chmod 755 *
sed -i 's/"type":.*"web",/"type": "game",/' appinfo.json
cd ../../../..
tar cvzf data.tar.gz usr
rm -rf usr; rm "../$1"
ar -r "../$1" *
cd ..;rm -rf "$TMPDIR"
</pre>

Once you have this, you should be ready to go. Obviously this only needs to be done once.

First make an installation directory with just the files we want to package.

<pre>
mkdir package
cp doom doom1.wad package
cd package
</pre>

Next, create a start script that will be launched by the icon for your application. It can do things like changing the working directory (cd) into the right directory and start your program with the right command line arguments, if any.

Create the file start-doom.sh with your favorite text editor like so:

<pre>
#!/bin/sh
cd /media/cryptofs/apps/usr/palm/applications/com.example.doom
./doom
</pre>

Create the file appinfo.json with your favorite text editor like so:
<pre>
{
"title": "DOOM",
"type": "web",
"main": "start-doom.sh",
"id": "com.example.doom",
"vendor": "example.com",
"version": "0.1.0",
"icon": "icon.png"
}
</pre>

Make sure you change id to a reversed domain name like com.example (example.com) but don't use example.com. Get a domain name to use or ask a friend if you can use theirs. This domain should be unique.

Now we need to package it up and fix up the package to be game-compatible. Run:

<pre>
palm-package .
palm-game-fix *ipk
</pre>

Now you can do a test install and launch.
<pre>
palm-install com.example.doom_0.1.0_all.ipk
palm-launch com.example.doom
</pre>

Hopefully, DOOM should open in all its glory.

Have fun making native apps.

Building DOOM with scratchbox2

2011-08-26T03:44:31Z

Cyclic:

[[Category:SDL]]

First, follow the tutorial [[WebOS Internals PDK]] to set up the cross compilation environment.

Next, download the sdlDOOM source code:

<pre>
wget http://www.libsdl.org/projects/doom/src/sdldoom-1.10.tar.gz
tar xzf sdldoom-1.10.tar.gz
cd sdldoom-1.10
</pre>

Now run scratchbox2 with the webos / pre mapping file:

<pre>
$ sb2 -M /srv/preware/cross-compile/staging/mapping-armv7
</pre>

NOTE: You should use armv6 if your target device is a Pixi.

You will get a different prompt indicating you are in a scratchbox shell, like:
<pre>
[SB2 mapping-armv7 armv7] $
</pre>

Run:

<pre>
./configure --with-sdl-prefix=/usr/local
make
</pre>

Build should complete successfully with no problems. Download a DOOM shareware WAD:

NOTE: If you receive an error "configure: error: *** SDL version 1.0.1 not found!", you will need to exit the sb2 command line by typing exit, then
<pre>
mkdir -p /usr/local/include/
cd /srv/preware/cross-compile/packages/dev-sdl
make -C libsdl ARCH=armv7 stage</pre>

Be patient. The compile can take 10 minutes. You should be able to cd into the doom directory and continue above at "Now run scratchbox2 with the webos / pre mapping file:"

<pre>
wget http://www.libsdl.org/projects/doom/data/doom1.wad.gz
gunzip doom1.wad.gz
</pre>

Copy the DOOM program binary and wad to root's home directory on the pre:
<pre>
scp doom doom1.wad root@pre:
</pre>

SSH to the device (novaterm would also work to get there, or an on-device terminal)
<pre>
ssh root@pre
</pre>

On the device, run DOOM:
<pre>
./doom
</pre>

Yay, it should now run. You may want to customize the code for better controls on the device.

Now let's package it up for all your friends to install. You should be back in your sdldoom-1.1.0 directory. For this, we'll use the Palm SDK, so make sure you have it installed.

First off: Unfortunately palm-package doesn't _quite_ make game packages properly. First, we want type to be "game" and palm-package doesn't understand that (will reject it as an invalid type in the 1.3.5 SDK). Secondly, the executables need to be set with executable permissions. For all this, we need a script to fix up the ipk for you.

palm-game-fix (I put it in /usr/local/bin and chmod 755 /usr/local/bin/palm-game-fix)
<pre>
#!/bin/bash
TMPDIR="fix-game-ipk-tmp.$$"
if [ ! -f "$1" ]; then echo "$1" not found; exit 1; fi
mkdir "$TMPDIR"; cd "$TMPDIR"
ar x "../$1"
tar xvzf data.tar.gz
cd usr/palm/applications/*
chmod 755 *
sed -i 's/"type":.*"web",/"type": "game",/' appinfo.json
cd ../../../..
tar cvzf data.tar.gz usr
rm -rf usr; rm "../$1"
ar -r "../$1" *
cd ..;rm -rf "$TMPDIR"
</pre>

Once you have this, you should be ready to go. Obviously this only needs to be done once.

First make an installation directory with just the files we want to package.

<pre>
mkdir package
cp doom doom1.wad package
cd package
</pre>

Next, create a start script that will be launched by the icon for your application. It can do things like changing the working directory (cd) into the right directory and start your program with the right command line arguments, if any.

Create the file start-doom.sh with your favorite text editor like so:

<pre>
#!/bin/sh
cd /media/cryptofs/apps/usr/palm/applications/com.example.doom
./doom
</pre>

Create the file appinfo.json with your favorite text editor like so:
<pre>
{
"title": "DOOM",
"type": "web",
"main": "start-doom.sh",
"id": "com.example.doom",
"vendor": "example.com",
"version": "0.1.0",
"icon": "icon.png"
}
</pre>

Make sure you change id to a reversed domain name like com.example (example.com) but don't use example.com. Get a domain name to use or ask a friend if you can use theirs. This domain should be unique.

Now we need to package it up and fix up the package to be game-compatible. Run:

<pre>
palm-package .
palm-game-fix *ipk
</pre>

Now you can do a test install and launch.
<pre>
palm-install com.example.doom_0.1.0_all.ipk
palm-launch com.example.doom
</pre>

Hopefully, DOOM should open in all its glory.

Have fun making native apps.

Building DOOM with scratchbox2

2011-08-26T03:43:32Z

Cyclic: added error with sdl 1.0.1

[[Category:SDL]]

First, follow the tutorial [[WebOS Internals PDK]] to set up the cross compilation environment.

Next, download the sdlDOOM source code:

<pre>
wget http://www.libsdl.org/projects/doom/src/sdldoom-1.10.tar.gz
tar xzf sdldoom-1.10.tar.gz
cd sdldoom-1.10
</pre>

Now run scratchbox2 with the webos / pre mapping file:

<pre>
$ sb2 -M /srv/preware/cross-compile/staging/mapping-armv7
</pre>

NOTE: You should use armv6 if your target device is a Pixi.

You will get a different prompt indicating you are in a scratchbox shell, like:
<pre>
[SB2 mapping-armv7 armv7] $
</pre>

Run:

<pre>
./configure --with-sdl-prefix=/usr/local
make
</pre>

Build should complete successfully with no problems. Download a DOOM shareware WAD:

NOTE: If you receive an error "configure: error: *** SDL version 1.0.1 not found!", you will need to exit the sb2 command line by typing exit, then
<pre>
mkdir -p /usr/local/include/
cd /srv/preware/cross-compile/packages/dev-sdl
make -C packages/libsdl ARCH=armv7 stage</pre>

Be patient. The compile can take 10 minutes. You should be able to cd into the doom directory and continue above at "Now run scratchbox2 with the webos / pre mapping file:"

<pre>
wget http://www.libsdl.org/projects/doom/data/doom1.wad.gz
gunzip doom1.wad.gz
</pre>

Copy the DOOM program binary and wad to root's home directory on the pre:
<pre>
scp doom doom1.wad root@pre:
</pre>

SSH to the device (novaterm would also work to get there, or an on-device terminal)
<pre>
ssh root@pre
</pre>

On the device, run DOOM:
<pre>
./doom
</pre>

Yay, it should now run. You may want to customize the code for better controls on the device.

Now let's package it up for all your friends to install. You should be back in your sdldoom-1.1.0 directory. For this, we'll use the Palm SDK, so make sure you have it installed.

First off: Unfortunately palm-package doesn't _quite_ make game packages properly. First, we want type to be "game" and palm-package doesn't understand that (will reject it as an invalid type in the 1.3.5 SDK). Secondly, the executables need to be set with executable permissions. For all this, we need a script to fix up the ipk for you.

palm-game-fix (I put it in /usr/local/bin and chmod 755 /usr/local/bin/palm-game-fix)
<pre>
#!/bin/bash
TMPDIR="fix-game-ipk-tmp.$$"
if [ ! -f "$1" ]; then echo "$1" not found; exit 1; fi
mkdir "$TMPDIR"; cd "$TMPDIR"
ar x "../$1"
tar xvzf data.tar.gz
cd usr/palm/applications/*
chmod 755 *
sed -i 's/"type":.*"web",/"type": "game",/' appinfo.json
cd ../../../..
tar cvzf data.tar.gz usr
rm -rf usr; rm "../$1"
ar -r "../$1" *
cd ..;rm -rf "$TMPDIR"
</pre>

Once you have this, you should be ready to go. Obviously this only needs to be done once.

First make an installation directory with just the files we want to package.

<pre>
mkdir package
cp doom doom1.wad package
cd package
</pre>

Next, create a start script that will be launched by the icon for your application. It can do things like changing the working directory (cd) into the right directory and start your program with the right command line arguments, if any.

Create the file start-doom.sh with your favorite text editor like so:

<pre>
#!/bin/sh
cd /media/cryptofs/apps/usr/palm/applications/com.example.doom
./doom
</pre>

Create the file appinfo.json with your favorite text editor like so:
<pre>
{
"title": "DOOM",
"type": "web",
"main": "start-doom.sh",
"id": "com.example.doom",
"vendor": "example.com",
"version": "0.1.0",
"icon": "icon.png"
}
</pre>

Make sure you change id to a reversed domain name like com.example (example.com) but don't use example.com. Get a domain name to use or ask a friend if you can use theirs. This domain should be unique.

Now we need to package it up and fix up the package to be game-compatible. Run:

<pre>
palm-package .
palm-game-fix *ipk
</pre>

Now you can do a test install and launch.
<pre>
palm-install com.example.doom_0.1.0_all.ipk
palm-launch com.example.doom
</pre>

Hopefully, DOOM should open in all its glory.

Have fun making native apps.

Application:MetaDoctor

2011-08-24T06:39:41Z

Cyclic: /* Step 2: Running the webOS Doctor */

[[Category:Application]]
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]
:[[Image:France.png]] [[Application:MetaDoctor-FR]]
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''
# Burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

Once you have installed WUBI, you should follow the instructions in the Linux section below.

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre>
# Create a downloads directory. Type: <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.
#Install md5sum: <pre>sudo port install md5sha1sum</pre>
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
#Install wget: <pre>sudo port install wget</pre>
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
#Install patch: <pre>sudo port install gpatch</pre>
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.

'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre>
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use.
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

This should begin a process within the terminal that should take 10 minutes max.
'''Note ''':if you receive an error message, 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads', you need to append the version number to the end of the file (e.g. sudo mv webosdoctorp302hstnhwifi.jar webosdoctorp302hstnhwifi-3.0.2.jar)

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.

If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

CD to the folder where your new jar file is, and type something like:

java -jar webosdoctorp302hstnhwifi.jar

If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscellaneous=
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.
Steps:
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
4. Put com.palm.wifi.prefsDB.sl in the config directory.
5. Continue following instructions in the makefile.

==How to enable WIFI profiles==
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile.

# Move to the meta-doctor directory (cd meta-doctor)
# Create a "config" folder in the meta-doctor directory (mkdir config)
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.
# Build the custom doctor by running the script, or otherwise building it.

On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.

See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].

==How to get the optional ext3fs partition mounted at device boot==

'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''

Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.

All of this is done on device either via novaterm or an SSH login.
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

<pre>mount -o remount,rw /
mkdir -p /media/ext3fs</pre>

it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.

After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.

<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre>

Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.

<pre>mount -a</pre>

If you do not want it mounted at bootup, but you do need it mounted, you can use this command.

<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre>

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

== Problems with Novacom ==
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].

== How to Install webOS 2.x on "unoffical" Devices==
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]

Application:MetaDoctor

2011-08-24T06:29:26Z

Cyclic: /* Step 2: Running the webOS Doctor */

[[Category:Application]]
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]
:[[Image:France.png]] [[Application:MetaDoctor-FR]]
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''
# Burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

Once you have installed WUBI, you should follow the instructions in the Linux section below.

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre>
# Create a downloads directory. Type: <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.
#Install md5sum: <pre>sudo port install md5sha1sum</pre>
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
#Install wget: <pre>sudo port install wget</pre>
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
#Install patch: <pre>sudo port install gpatch</pre>
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.

'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre>
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use.
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

This should begin a process within the terminal that should take 10 minutes max.

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.

If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

CD to the folder where your new jar file is, and type something like:

java -jar webosdoctorp302hstnhwifi.jar

If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscellaneous=
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.
Steps:
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
4. Put com.palm.wifi.prefsDB.sl in the config directory.
5. Continue following instructions in the makefile.

==How to enable WIFI profiles==
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile.

# Move to the meta-doctor directory (cd meta-doctor)
# Create a "config" folder in the meta-doctor directory (mkdir config)
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.
# Build the custom doctor by running the script, or otherwise building it.

On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.

See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].

==How to get the optional ext3fs partition mounted at device boot==

'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''

Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.

All of this is done on device either via novaterm or an SSH login.
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

<pre>mount -o remount,rw /
mkdir -p /media/ext3fs</pre>

it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.

After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.

<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre>

Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.

<pre>mount -a</pre>

If you do not want it mounted at bootup, but you do need it mounted, you can use this command.

<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre>

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

== Problems with Novacom ==
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].

== How to Install webOS 2.x on "unoffical" Devices==
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]

Application:MetaDoctor

2011-08-24T06:25:17Z

Cyclic: /* Step 2: Running the webOS Doctor */

[[Category:Application]]
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]
:[[Image:France.png]] [[Application:MetaDoctor-FR]]
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''
# Burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

Once you have installed WUBI, you should follow the instructions in the Linux section below.

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre>
# Create a downloads directory. Type: <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.
#Install md5sum: <pre>sudo port install md5sha1sum</pre>
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
#Install wget: <pre>sudo port install wget</pre>
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
#Install patch: <pre>sudo port install gpatch</pre>
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.

'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre>
# Rename the file that you download to include the version number for future reference (examples: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). An example (i.e. will not work, you need to work out the filename based on the URL you used to download it) command to do that would be:<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre>
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use.
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

This should begin a process within the terminal that should take 10 minutes max.

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar''.

If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

CD to the folder where your new jar file is, and type something like:

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscellaneous=
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.
Steps:
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
4. Put com.palm.wifi.prefsDB.sl in the config directory.
5. Continue following instructions in the makefile.

==How to enable WIFI profiles==
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile.

# Move to the meta-doctor directory (cd meta-doctor)
# Create a "config" folder in the meta-doctor directory (mkdir config)
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.
# Build the custom doctor by running the script, or otherwise building it.

On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.

See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].

==How to get the optional ext3fs partition mounted at device boot==

'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''

Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.

All of this is done on device either via novaterm or an SSH login.
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

<pre>mount -o remount,rw /
mkdir -p /media/ext3fs</pre>

it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.

After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.

<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre>

Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.

<pre>mount -a</pre>

If you do not want it mounted at bootup, but you do need it mounted, you can use this command.

<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre>

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

== Problems with Novacom ==
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].

== How to Install webOS 2.x on "unoffical" Devices==
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]