WebOS Internals - User contributions [en]

Proximity Sensor

2010-04-28T00:38:15Z

Nt4cats:

While poking around in '''com.palm.app.crotest''' code I found some code that interacts with the IR proximity sensor. I think quite a few apps could use it as an input, for one the stock "Clock" app can utilize it to control it's alarm / snooze / dismiss functions. I haven't done much with it yet and don't think it would be appropriate to cut-paste code here but if you're interested in exploring this functionality check out:

'''/usr/palm/applications/com.palm.app.crotest/app/controllers/proximity-assistant.js'''

I'll try and update this page when I find more information / code examples.

UPDATE: The code in "proximity-assistant.js" does not get any events from the proximity sensor. It is unable to know whether a user has gotten close to the proximity sensor. All it can do is turn the sensor on (and be notified that it successfully set it on). The screen turning off is done by the sensor, NOT by the phone app's code. Unfortunately unless we find a way to get events from the proximity sensor it is effectively useless for apps like the alarm clock suggested above.

Application:OpenSSH

2010-04-18T22:23:07Z

Nt4cats: Added "How to enable ssh over EVDO" to the bottom of the page

==Introduction==

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

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. 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).

===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 /

Manually Remove Preware Feeds

2010-04-18T21:42:32Z

Nt4cats: /* Special Note */

== Special Note ==
You should not need to use these instructions under normal circumstances. Preware allows you to add, edit, and delete feeds via the "Manage Feeds" option in its application menu. These instructions should only be used in the event of difficulties using this functionality from within Preware.

Some versions of Preware will not delete a disabled feed. Before you try these steps, enable the feed(s) before deleting them.

== Instructions ==

Feed files are stored in '/media/cryptofs/apps/etc/ipkg'. We recommend you move the feed files you want to remove into an archive folder on /media/internal in case you change your mind. You can go back and physically remove them later.

In the example below, an archive directory is created and the "WebosTesting" feed is moved there:

<pre>
root@palm-webos-device:/# cd /media/cryptofs/apps/etc/ipkg
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# ls
Alpha.conf.disabled palm-beta.conf.disabled precentral-themes.conf.disabled
WebosTesting.conf.disabled palm-catalog-updates.conf.disabled precentral.conf
arch.conf palm-catalog.conf.disabled prethemer.conf.disabled
optware.conf palm-web-updates.conf.disabled webos-internals.conf
palm-beta-updates.conf.disabled palm-web.conf.disabled webos-patches.conf
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mkdir /media/internal/feed-archive
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mv WebosTesting.conf.disabled /media/internal/feed-archive/
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg#
</pre>

Manually Remove Preware Feeds

2010-04-17T18:24:39Z

Nt4cats: /* Special Note */ modified to convince people that I speak English

== Special Note ==
You should not need to use these instructions under normal circumstances. Preware allows you to add / edit / and delete feeds via the "Manage Feeds" option in its application menu. These instructions should only be used in the event of difficulties using this functionality from within Preware.

== Instructions ==

Feed files are stored in '/media/cryptofs/apps/etc/ipkg'. We recommend you move the feed files you want to remove into an archive folder on /media/internal in case you change your mind. You can go back and physically remove them later.

In the example below, we'll remove the "WebosTesting" feed by moving it to an archive folder that we created.

<pre>
root@palm-webos-device:/# cd /media/cryptofs/apps/etc/ipkg
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# ls
Alpha.conf.disabled palm-beta.conf.disabled precentral-themes.conf.disabled
WebosTesting.conf.disabled palm-catalog-updates.conf.disabled precentral.conf
arch.conf palm-catalog.conf.disabled prethemer.conf.disabled
optware.conf palm-web-updates.conf.disabled webos-internals.conf
palm-beta-updates.conf.disabled palm-web.conf.disabled webos-patches.conf
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mkdir /media/internal/feed-archive
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mv WebosTesting.conf.disabled /media/internal/feed-archive/
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg#
</pre>

Manually Remove Preware Feeds

2010-04-17T18:23:41Z

Nt4cats: Removed extra header

== Special Note ==
You should, in normal circumstances, not need to use these instructions. Preware allows you to add / edit / and delete feeds via the "Manage Feeds" option in its application menu. These instructions should only be used in the event of difficulties using this functionality from within Preware.

== Instructions ==

Feed files are stored in '/media/cryptofs/apps/etc/ipkg'. We recommend you move the feed files you want to remove into an archive folder on /media/internal in case you change your mind. You can go back and physically remove them later.

In the example below, we'll remove the "WebosTesting" feed by moving it to an archive folder that we created.

<pre>
root@palm-webos-device:/# cd /media/cryptofs/apps/etc/ipkg
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# ls
Alpha.conf.disabled palm-beta.conf.disabled precentral-themes.conf.disabled
WebosTesting.conf.disabled palm-catalog-updates.conf.disabled precentral.conf
arch.conf palm-catalog.conf.disabled prethemer.conf.disabled
optware.conf palm-web-updates.conf.disabled webos-internals.conf
palm-beta-updates.conf.disabled palm-web.conf.disabled webos-patches.conf
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mkdir /media/internal/feed-archive
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mv WebosTesting.conf.disabled /media/internal/feed-archive/
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg#
</pre>

Manually Remove Preware Feeds

2010-04-17T18:23:04Z

Nt4cats: Initial creation based upon a conversation I had with irc user 'sethron'

= How-to manually remove feeds from Preware =

== Special Note ==
You should, in normal circumstances, not need to use these instructions. Preware allows you to add / edit / and delete feeds via the "Manage Feeds" option in its application menu. These instructions should only be used in the event of difficulties using this functionality from within Preware.

== Instructions ==

Feed files are stored in '/media/cryptofs/apps/etc/ipkg'. We recommend you move the feed files you want to remove into an archive folder on /media/internal in case you change your mind. You can go back and physically remove them later.

In the example below, we'll remove the "WebosTesting" feed by moving it to an archive folder that we created.

<pre>
root@palm-webos-device:/# cd /media/cryptofs/apps/etc/ipkg
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# ls
Alpha.conf.disabled palm-beta.conf.disabled precentral-themes.conf.disabled
WebosTesting.conf.disabled palm-catalog-updates.conf.disabled precentral.conf
arch.conf palm-catalog.conf.disabled prethemer.conf.disabled
optware.conf palm-web-updates.conf.disabled webos-internals.conf
palm-beta-updates.conf.disabled palm-web.conf.disabled webos-patches.conf
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mkdir /media/internal/feed-archive
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg# mv WebosTesting.conf.disabled /media/internal/feed-archive/
root@palm-webos-device:/media/cryptofs/apps/etc/ipkg#
</pre>

Optware

2010-04-13T19:56:03Z

Nt4cats: Added "Optware Advanced Linux Command Line Installer" to the prereq's

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install both the "Optware Bootstrap" and the "Optware Advanced Linux Command Line Installer" using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There over one thousand Optware packages hosted at nslu2-linux.org that are not available from preware.org. We will refer to these as '''raw''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that raw Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

To get a list of all packages

ipkg-opt list

To get a list of installed packages

ipkg-opt list_installed

Here is an example of the command used to install the Python 2.5 interpreter

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-13T14:16:45Z

Nt4cats: /* Installing "raw" nslu2-linux.org Optware packages */

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There over one thousand Optware packages hosted at nslu2-linux.org that are not available from preware.org. We will refer to these as '''raw''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that raw Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

To get a list of all packages

ipkg-opt list

To get a list of installed packages

ipkg-opt list_installed

Here is an example of the command used to install the Python 2.5 interpreter

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-13T13:56:40Z

Nt4cats: /* "Raw" Optware packages vs. mobi.optware.* packages */

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There over one thousand Optware packages hosted at nslu2-linux.org that are not available from preware.org. We will refer to these as '''raw''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that raw Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

Then you can use the list, list_installed, info, and install commands as needed

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-12T14:11:34Z

Nt4cats: /* "Raw" Optware packages vs. mobi.optware.* packages */

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There are hundreds of Optware packages that are not available from preware.org. These packages are hosted at nslu2-linux.org, and we will refer to these as '''raw''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that raw Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

Then you can use the list, list_installed, info, and install commands as needed

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-12T14:10:59Z

Nt4cats: /* "Raw" Optware packages vs. mobi.optware.* packages */

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There are hundreds of Optware packages that are not available from preware.org. These packages are hosted at nslu2-linux.org, and we will refer to these as "raw" Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that raw Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

Then you can use the list, list_installed, info, and install commands as needed

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-12T14:09:56Z

Nt4cats: /* "Raw" Optware packages vs. mobi.optware.* packages */

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package file names follow the pattern '''mobi.optware.*'''.

There are hundreds of Optware packages that are '''not''' available from preware.org. These packages are hosted at nslu2-linux.org, and we will refer to these as '''"raw"''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that "raw" Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

Then you can use the list, list_installed, info, and install commands as needed

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Optware

2010-04-12T14:08:56Z

Nt4cats: New page: ==Using Optware== Preware has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Prewa...

==Using Optware==

[[Preware]] has several of the most popular and useful Optware packages available in the Optware feed. If the Optware package you're looking for is available in [[Preware]], just use [[Preware]] to install it.

At a minimum, please install the Optware Bootstrap using [[Preware]]. The instructions on this page assume that you have done so.

These instructions also assume you have command-line access to your Pre. Instructions for getting this access can be found at [[Application:OpenSSH|Access via SSH]] and [[Portal:Accessing_Linux|Access via Novaterm]].

=="Raw" Optware packages vs. mobi.optware.* packages==

As mentioned previously, the Optware feed from preware.org includes a selection of popular packages. These package files follow the pattern '''mobi.optware.*'''.

There are hundreds of Optware packages that are '''not''' available from preware.org. These packages are hosted at nslu2-linux.org, and we will refer to these as '''"raw"''' Optware packages (or "the nslu2-linux.org Optware packages"). One other important distinction is that "raw" Optware packages are managed using the '''ipkg-opt''' command, while the all packages installed by Preware (including the mobi.optware.* packages) are managed under the covers using the stock '''ipkg''' command.

Let's re-state the advice that if there is a mobi.optware.* version of the package you are looking for you should use [[Preware]] to install it instead of using the "raw" Optware package.

==Installing "raw" nslu2-linux.org Optware packages==

Make your filesystem read-write

mount -o rw,remount /

Then you need to download a fresh copy of the package list from nslu2-linux.org.

ipkg-opt update

Then you can use the list, list_installed, info, and install commands as needed

ipkg-opt install python25

Don't forget to make your filesystem read-only once you're done.

mount -o ro,remount /

Application:OpenSSH

2010-04-05T15:13:53Z

Nt4cats: The bottom section had content from the dropbear package. I updated it to be accurate for the openssh package.

==Introduction==

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

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. 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).

===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 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.

Portal:Updating webOS Versions

2009-11-16T21:41:28Z

Nt4cats:

{{portal-header
|Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results.

*'''1.''' Open [[Application:Preware|Preware]] and select Installed Packages.
*'''2.''' Remove any Theme(s) you have installed. There SHOULD only be one...
*'''3.''' Go back to the main menu and select "List of Everything" and search for "Emergency".
*'''4.''' Select and install "Emergency Patch Recovery". Note: This will remove all patches. Please read the description.
** After it completes (might take a couple minutes), choose "Update Feeds" from the App Menu (top left corner). Then go back to main menu and "Installed Packages".
***If "Patches" IS NOT listed as a category, go to step 5.
***If "Patches" IS listed as a category, select it and remove any patches still installed. Then continue to step 5.
*'''5.''' If you have [[Application:Luna Manager|Luna Manager]] installed, start it and "Restart Luna". If not, reboot your phone.
*'''6.''' Update webOS. :)
*'''7.''' Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).
*'''8.''' Select Update Feeds.
*'''9.''' Continue on to reinstalling your Patches/Theme.
*'''10.''' Thank the webOS-Internals group!

If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

 
''For advanced users:'' You can dump a list of installed packages using the following technique before running the Emergency Patch Recovery (EPR) tool. This assumes you already have shell access to your your Pre via novaterm or ssh.

*'''1.''' Ssh into your Pre (you do not need to adopt root privileges)
*'''2.''' Type (no quotes) "ipkg -o /var list_installed <nowiki>|</nowiki> grep patches". This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.

Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.
}}

Portal:Updating webOS Versions

2009-11-16T21:40:30Z

Nt4cats:

{{portal-header
|Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results.

*'''1.''' Open [[Application:Preware|Preware]] and select Installed Packages.
*'''2.''' Remove any Theme(s) you have installed. There SHOULD only be one...
*'''3.''' Go back to the main menu and select "List of Everything" and search for "Emergency".
*'''4.''' Select and install "Emergency Patch Recovery". Note: This will remove all patches. Please read the description.
** After it completes (might take a couple minutes), choose "update feeds" from the PreWare menu. Then go back to main menu and "Installed Packages".
***If "Patches" IS NOT listed as a category, go to step 5.
***If "Patches" IS listed as a category, select it and remove any patches still installed. Then continue to step 5.
*'''5.''' If you have [[Application:Luna Manager|Luna Manager]] installed, start it and "Restart Luna". If not, reboot your phone.
*'''6.''' Update webOS. :)
*'''7.''' Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).
*'''8.''' Select Update Feeds.
*'''9.''' Continue on to reinstalling your Patches/Theme.
*'''10.''' Thank the webOS-Internals group!

If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

 
''For advanced users:'' You can dump a list of installed packages using the following technique before running the Emergency Patch Recovery (EPR) tool. This assumes you already have shell access to your your Pre via novaterm or ssh.

*'''1.''' Ssh into your Pre (you do not need to adopt root privileges)
*'''2.''' Type (no quotes) "ipkg -o /var list_installed <nowiki>|</nowiki> grep patches". This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.

Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.
}}

Portal:Updating webOS Versions

2009-11-16T21:37:29Z

Nt4cats:

{{portal-header
|Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results.

*'''1.''' Open [[Application:Preware|Preware]] and select Installed Packages.
*'''2.''' Remove any Theme(s) you have installed. There SHOULD only be one...
*'''3.''' Go back to the main menu and select "Patches" and then "Recovery".
** You might need to select "Available Packages" before "Patches".
*'''4.''' Install "Emergency Patch Recovery". Note: This will remove all patches. Please read the description.
** After it completes (might take a couple minutes), choose "update feeds" from the PreWare menu. Then go back to main menu and "Installed Packages".
***If "Patches" IS NOT listed as a category, go to step 5.
***If "Patches" IS listed as a category, select it and remove any patches still installed. Then continue to step 5.
*'''5.''' If you have [[Application:Luna Manager|Luna Manager]] installed, start it and "Restart Luna". If not, reboot your phone.
*'''6.''' Update webOS. :)
*'''7.''' Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).
*'''8.''' Select Update Feeds.
*'''9.''' Continue on to reinstalling your Patches/Theme.
*'''10.''' Thank the webOS-Internals group!

If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

 
''For advanced users:'' You can dump a list of installed packages using the following technique before running the Emergency Patch Recovery (EPR) tool. This assumes you already have shell access to your your Pre via novaterm or ssh.

*'''1.''' Ssh into your Pre (you do not need to adopt root privileges)
*'''2.''' Type (no quotes) "ipkg -o /var list_installed <nowiki>|</nowiki> grep patches". This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.

Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.
}}

Portal:Updating webOS Versions

2009-11-14T21:46:38Z

Nt4cats:

{{portal-header
|Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results.

*'''1.''' Open [[Application:Preware|Preware]] and select Installed Packages.
*'''2.''' Remove any Theme(s) you have installed. There SHOULD only be one...
*'''3.''' Go back to the main menu and select "Patches" and then "Recovery".
*'''4.''' Install "Emergency Patch Recovery". Note: This will remove all patches. Please read the description.
*'''5.''' If you have [[Application:Luna Manager|Luna Manager]] installed, start it and "Restart Luna". If not, reboot your phone.
*'''6.''' Update webOS. :)
*'''7.''' Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).
*'''8.''' Select Update Feeds.
*'''9.''' Continue on to reinstalling your Patches/Theme.
*'''10.''' Thank the webOS-Internals group!

If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

 
''For advanced users:'' You can dump a list of installed packages using the following technique before running the Emergency Patch Recovery (EPR) tool. This assumes you already have shell access to your your Pre via novaterm or ssh.

*'''1.''' Ssh into your Pre (you do not need to adopt root privileges)
*'''2.''' Type (no quotes) "ipkg -o /var list_installed <nowiki>|</nowiki> grep patches". This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.

Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.
}}

Talk:Patch Email DeleteAll

2009-10-19T15:25:59Z

Nt4cats: /* Delete some vs. all messages? */

=Icon File=
Do you know where I could get a list of valid icons? - [[User:Ikyo|Ikyo]]

=Delete some vs. all messages?=
Is there a way to select a certain number of messages and then delete those versus all those on the page? -[[User:Mamouton|Mamouton]]

:Not currently with this patch. I figure if I am going to click on them to select them to be deleted it is just as easy to swipe them away at the same time. With that said I believe I saw someone working on an approach similar to what you are describing on precentral.net. -[[User:Lclarkjr|Lclarkjr]]

=Mark some messages as read?=
Is there a way to select a certain number of messages and then mark them as read? I'll get a batch of messages from our monitoring server that I want to mark as read, but I have a dozen other messages in my inbox that I don't want marked as read at the same time. Do you know who may have already been working on this? Maybe I can pitch in and help them (or you) implement this -[[User:nt4cats|nt4cats]]

Solution to App Catalog Installation Limit

2009-10-12T15:34:38Z

Nt4cats: /* Solution (symbolic link method) */

Based on rwhitby's findings that temporarily moving /var/usr/palm/applications will allow installing apps from the App Catalog, here's a permanent way to keep the apps on (much larger) /media/internal by using links. This will permanently save space on /var.

It's unfortunate that Palm has not resolved the issue in the 1.2 update. This is a tactical workaround that could potentially work long term, also saving space on /var, but this needs support by the homebrew community to add in the homebrew installer apps.

== Overview ==
This solution involves creating a (hidden) directory in the /media/internal area, moving selected applications to the newly created directory, and then creating a symbolic link in the /var/usr/palm/applications directory pointing to the new location. This frees up the disk space from the relatively limited /var volume to the larger /media/internal. The included script (which must be created) will move the files and create the appropriate link. It will also provide information on the size of the applications stored in the /var/usr/palm/applications directory.

== Solution (symbolic link method) ==

Create a script to move apps to new home and create link. You can use an editor or use the following cat command to paste the code, for those not familiar with editors.

Here's how to do it for those comfortable with accessing Linux...

- Enter Linux mode on Pre through a computer (linux commands are in bold)

- Set read/write to allow creating script 
<code>'''mount -o remount,rw / '''</code>

- create a script using cat command, paste the code below and then do 'ctrl c' on the keyboard to break out. 
<code>'''cat >/usr/bin/mvapp''' </code>

- paste the code below here, press ctrl-c on keyboard to exit after pasting the code.

- when you see a linux prompt, set command to be executable 
<code> '''chmod 755 /usr/bin/mvapp''' </code>

----
code:
<pre>
#!/bin/sh

# This code is open for re-use with no restrictions. xorg
# This is a working proof of concept script still in development.
# Intent is for someone to port to a webOS app.
# Use at your own risk.

#-------------------------------------------------------------------------#
# versions:
# 0.1.0 - original (xorg)
# 0.1.1 - added unlink and clean functions (daventx)
# 0.1.2 - added bulkmv function, allows moving many apps (xorg)
# 0.1.3 - added option for tar backups (xorg)
# 0.1.4 - added listmoved function to show apps already moved (xorg)
# 0.1.5 - added restoreall function, couple cleanup items (xorg)
# 0.1.6 - fixed to show usage if no appname supplied to link/unlink (xorg)
# 0.1.7 - added cleanexit (w/mount ro /)
# - added exit code documentation for javascripts calling this (xorg)
# 0.2.0 - will not move apps that would have attribute issues (xorg)
# - will not move apps that have no json file
# - improved error handling, improved listing shows actual app names
# 0.2.1 - minor update, proper cleanup if link command doesn't move app
# - don't create tar backup until testing if app is movable
# 0.2.2 - minor update to make this script compatible with rwhitby's
# - "Fair Dinkum App Limit" fix by providing an explicit path
# - to the "du" command. (nt4cats)
#-------------------------------------------------------------------------#

#-------------------------------------------------------------------------#
# variables: these are globally available to all functions
#-------------------------------------------------------------------------#
COMMAND=$1
APP=$2
MEDIA=/media/internal/.apps
VAR=/var/usr/palm/applications

# Backup keeps file attributes but uses more /media space. Recommend doing backups.
BACKUP=1 # set to 1 for tar backups, 0 to disable
BACKUPDIR=/media/internal/.appbackups

# This should be turned on. Only turn off if javascript is calling this script.
PROMPTS=1

#-------------------------------------------------------------------------#
# exit codes for javascripts:
# function usage:
# 1 - normal usage error
#
# function cleanapp:
# 0 - normal exit
#
# function linkapp:
# 10 - app name not supplied
# 11 - link already exists
# 12 - app does not exit in VAR
# 13 - copy failed from VAR to MEDIA
# 14 - removing app from VAR failed
# 15 - APP needs permissions not supported on FAT, did not move to MEDIA
# 16 - APP has no json file, did not move to MEDIA
#
# function unlinkapp:
# 20 - app name not supplied
# 21 - app doesn't exit on MEDIA
# 22 - tar restore failed
# 23 - copy failed
# 24 - remove failed
#
#-------------------------------------------------------------------------#

#-------------------------------------------------------------------------#
# function: cleanexit - exit with cleanup items
#-------------------------------------------------------------------------#

cleanexit () {
code=$1

# put / back to read only
mount -o remount,ro /

# Uncomment if you want verbose exit codes
# echo "exit code: $code"

exit $code
}
# end of cleanexit function

#-------------------------------------------------------------------------#
# function: usage - show command usage options
#-------------------------------------------------------------------------#
usage () {
exitcode=$1
if [ ! $exitcode ]
then
exitcode=1 # default exit code for usage, otherwise exit with incode
fi

echo "Usage: mvapp link domain.appname - move app to media and link"
echo "Usage: mvapp unlink domain.appname - restore app to var, remove link"
echo "Usage: mvapp clean domain.appname - remove app dir and links"
echo "Usage: mvapp list - list all apps sorted by size"
echo "Usage: mvapp bulkmv - move/link bulk apps"
echo "Usage: mvapp listmoved - list apps that have been moved"
echo "Usage: mvapp restoreall - restore all apps to original"

cleanexit $exitcode
}
# end of usage function

#-------------------------------------------------------------------------#
# function: cleanapp - removes symbolic links and folder in media and var
#-------------------------------------------------------------------------#

cleanapp () {

mount -o remount,rw /

# exit to usage if no app name supplied
if [ ! $APP ]
then
usage 1
fi

# Continue on if PROMPTS turned off (call from outside app)
if [ $PROMPTS ]
then
echo "This will remove $APP from both $VAR and $MEDIA."
echo "You should first attempt to remove the app using the official Pre methods."
echo "Are you sure you want to remove $APP? [y/N]: "
read answer
case $answer in
[Yy]*) continue;;
*) cleanexit 0;;
esac
fi

if [ -h $VAR/$APP ]
then
echo "Removing all traces of $APP."
else
echo "$APP does not exist..."
usage 10
fi

echo "Size of $VAR before cleanup... "
/usr/bin/du -sh $VAR

if [ -d $MEDIA/$APP ]
then
rm -r $MEDIA/$APP
echo "Removed directory" $MEDIA/$APP
fi
if [ -d $VAR/$APP ]
then
rm -r $VAR/$APP
echo "Removed directory" $VAR/$APP
fi
if [ -L $VAR/$APP ]
then
rm -r $VAR/$APP
echo "Removed link" $VAR/$APP
fi
if [ -f $BACKUPDIR/$APP.tgz ]
then
rm -r $BACKUPDIR/$APP.tgz
echo "Removed tar backup" $BACKUPDIR/$APP.tgz
fi

# rescan luna in case it's needed
luna-send -n 1 palm://com.palm.applicationManager/rescan {} >/dev/null 2>&1
echo "$APP directories and links removed."
echo "Size of $VAR after cleanup... "
/usr/bin/du -sh $VAR
cleanexit 0
}
# end of cleanup function

#-------------------------------------------------------------------------#
# function: listapps - list the size of each app, sort showing largest last
#-------------------------------------------------------------------------#
listapps () {
cd $VAR
for i in `/usr/bin/du -s * | sort -n |cut -f 2`
do
APP=$i
SIZE=`/usr/bin/du -s $VAR/$APP |cut -f1`
TITLE=""
if [ -f $VAR/$APP/appinfo.json ]
then
TITLE=`grep title $VAR/$APP/appinfo.json |cut -d: -f2 |cut -d\" -f2`
fi
echo "$SIZE - $APP - $TITLE"
done

cleanexit 0
}
# end of listapps function

#-------------------------------------------------------------------------#
# function: listmoved - list apps moved/linked, sort showing largest last
#-------------------------------------------------------------------------#
listmoved () {
#/usr/bin/du -sk $MEDIA/* | sort -n #doesn't show proper size on FAT fs, removing
cd $MEDIA
for i in `/usr/bin/du -s * | sort -n |cut -f 2`
do
APP=$i
# Not sure why du reports incorrectly on FAT fs
#SIZE=`/usr/bin/du -s $MEDIA/$APP |cut -f1`
SIZE=""
TITLE=""
if [ -f $MEDIA/$APP/appinfo.json ]
then
TITLE=`grep title $MEDIA/$APP/appinfo.json |cut -d: -f2 |cut -d\" -f2`
fi
echo "$SIZE - $APP - $TITLE"
done
cleanexit 0
}
# end of listmoved function

#-------------------------------------------------------------------------#
# function: linkapp - move the app to media and create symbolic link
#-------------------------------------------------------------------------#
linkapp () {

if [ ! $APP ]
then
echo "No application supplied..."
usage 10
fi

if [ ! -f $VAR/$APP/appinfo.json ]
then
echo "$APP has no json file. Will not be moved."
code=16
return 16
fi

if [ ! -d $MEDIA ]
then
mkdir $MEDIA
fi

if [ -h $VAR/$APP ]
then
echo "Link already exists for... ${APP}"
cleanexit 11
fi

TITLE=`grep title $VAR/$APP/appinfo.json |cut -d: -f2 |cut -d\" -f2`

mount -o remount,rw /

if [ -d $VAR/$APP ]
then
echo "Moving $APP $TITLE to $MEDIA..."
else
echo "$APP does not exist..."
usage 12
fi

mount -o remount,rw /

echo "Size of $VAR before move... "
/usr/bin/du -sh $VAR

# move over to USB drive
cp -rp $VAR/$APP $MEDIA >/tmp/cpresult.out 2>&1
if [ $? != 0 ]
then
grep "cannot preserve" /tmp/cpresult.out >/dev/null 2>&1
if [ $? = 0 ]
then
echo
echo "$APP cannot be moved as it contains special attributes."
echo "Leaving app in $VAR."
code=15
else
echo "Copy failed. Leaving app in $VAR."
code=13
fi
rm -r $MEDIA/$APP
rm /tmp/cpresult.out
return $code
fi

# Backup using tar if enabled
if [ $BACKUP ]
then
if [ ! -d $BACKUPDIR ]
then
mkdir $BACKUPDIR
fi
echo "Backing up $APP $TITLE to $BACKUPDIR..."
tar czf $BACKUPDIR/${APP}.tgz $VAR/$APP
fi

rm -r $VAR/$APP
if [ $? != 0 ]
then
echo "Remove failed. Leaving app in $VAR."
rm -r $MEDIA/$APP
cleanexit 14
fi

# create the symbolic link
ln -s $MEDIA/$APP $VAR/$APP

# rescan luna in case it's needed
luna-send -n 1 palm://com.palm.applicationManager/rescan {} >/dev/null 2>&1

echo "$APP moved and linked."
echo "Size of $VAR after move... "
/usr/bin/du -sh $VAR
}
# end of linkapp function

#-------------------------------------------------------------------------#
# function: unlinkapp - restore the app to var and remove symbolic link
#-------------------------------------------------------------------------#
unlinkapp () {

if [ ! $APP ]
then
echo "No application supplied..."
usage 20
fi

mount -o remount,rw /

if [ -d $MEDIA/$APP ]
then
echo "Restoring $APP..."
else
echo "$APP does not exist..."
usage 21
fi

echo "Size of $VAR before move... "
/usr/bin/du -sh $VAR

# remove the old symbolic link
rm -r $VAR/$APP

# move to original location or restore from tar if it exists
if [ -f $BACKUPDIR/$APP.tgz ]
then
cd /
tar xzf $BACKUPDIR/$APP.tgz
if [ $? != 0 ]
then
echo "Tar restore failed. Remove and restore app using official webOS/Pre methods."
cleanexit 22
else
rm -r $BACKUPDIR/$APP.tgz
fi
else
cp -r $MEDIA/$APP $VAR
if [ $? != 0 ]
then
echo "Copy failed. Leaving app in $MEDIA."
cleanexit 23
fi
fi

rm -r $MEDIA/$APP
if [ $? != 0 ]
then
echo "Remove failed. Leaving app in $MEDIA."
rm -r $VAR/$APP
cleanexit 24
fi

# rescan luna in case it's needed
luna-send -n 1 palm://com.palm.applicationManager/rescan {} >/dev/null 2>&1

echo "$APP moved and unlinked."
echo "Size of $VAR after move... "
/usr/bin/du -sh $VAR
}
# end of unlinkapp function

#-------------------------------------------------------------------------#
# function: bulkmv - move/link many apps
#-------------------------------------------------------------------------#
bulkmv() {
echo
echo
echo "This allows moving many apps, asking which you'd like to move."
echo "Starting with the largest apps."
echo

mount -o remount,rw /
cd $VAR

for i in `/usr/bin/du -s * | sort -nr |cut -f 2`
do
export APP=$i
SIZE=`/usr/bin/du -sh $APP |cut -f 1`
TITLE=`grep title $VAR/$APP/appinfo.json |cut -d: -f2 |cut -d\" -f2`
echo "Size of $APP - $TITLE is $SIZE."
echo "Would you like to move and link... $TITLE? [y/N/q]: "
read answer
case $answer in
[Yy]*) linkapp;;
[Qq]*) cleanexit 0;;
*) echo "$APP not moved."
continue;;
esac

echo
done
}
# end of bulkmv function

#-------------------------------------------------------------------------#
# function: restoreall - restore all apps, back to /var
#-------------------------------------------------------------------------#
restoreall() {

#Only confirm if PROMPT turned on. (allows outside app to call)
if [ $PROMPT ]
then
echo "This will restore all applications back to original location"
echo "and remove the links. Are you sure you want to continue? [y/N]:"
read answer
case $answer in
[Yy]*) continue;;
*) cleanexit 0;;
esac
fi

ls $MEDIA | while read APP
do
echo "Restoring $APP and unlinking..."
unlinkapp
done
}
# end of restoreall function

#-------------------------------------------------------------------------#
# main - begins here
#-------------------------------------------------------------------------#

case $COMMAND in
"clean")
cleanapp
;;
"list")
listapps
;;
"listmoved")
listmoved
;;
"link")
linkapp
;;
"unlink")
unlinkapp
;;
"bulkmv")
bulkmv
;;
"restoreall")
restoreall
;;
*)
usage 1
;;
esac

cleanexit $code

</pre>

----

- Be sure to set execute permissions if you missed the step above...
<code>chmod 755 /usr/bin/mvapp</code>

== Precautions ==

So far, no one has reported an app that has issues due to linking. These are best practices to avoid issues.

- Be selective about what you move. You may not want to move apps that store important information to you such as password lockers, memo apps, EverNote, Agenda, etc. Games, web content apps and information viewing apps should be safer to move as there is no data at risk.

- Close apps before moving them. Do not move an app while it is open and running. I actually tested this and figured some apps would break but none have yet. It is still not wise to move apps while they are open and running.

== Commands ==

'''To find the largest apps in /var/usr/palm/applications'''

<code>mvapp list</code>

It shows the largest apps last... IE.... 
<code>
8352 com.apnews.webos 
8512 com.fandango.app.fandango 
8672 com.palm.app.musicplayerremix 
10304 com.shortcovers.palm.pre 
10432 com.fusioncreativestudios.deadman 
10656 com.ulocate.app.where 
</code>

'''To move and link an app to /media'''

<code>mvapp link domain.appname</code>

Example: mvapp link com.ulocate.app.where

The app should now work in the new location thanks to the link. Test each app to make sure it works before doing another. Looping the script to do every app in the dir or to link the entire app dir is not recommended. File attributes are lost on the move, which some apps may need. You need to test each app after a move.

Continue moving apps until it reports that /var.../applications is about 25MB or less.

There is an option to turn on/off tar-based backups. See the BACKUP variable in the script. If set to 1, it will perform a tar backup. This takes up more space on /media but if you need to restore, it puts it back with full file attributes. Recommend keeping this on.

'''To move and link many apps'''

<code>mvapp bulkmv</code>

This will show largest app first, ask if you want to move/link and then moves on to the next largest app. If you answer no to an app, it will skip to the next. Answer 'q' to quit. Is easiest to use this method directly on a device using the Terminal app.

'''To revert the move and delete the link'''

<code>mvapp unlink domain.appname</code>

The application will be moved back to the original directory. File attributes are lost on the move if tar backup is turned off, which some apps may need. You need to test each app after a move. If tar backup is turned on (default - see BACKUP variable in script), file attributes will be restored.

'''To list apps that have been moved and linked...'''

<code>mvapp listmoved</code>

This shows a list of apps that have been moved and linked to /media.

'''To restore all moved apps back to original location'''

<code>mvapp restoreall</code>

If backup was turned on, this will restore ALL applications that have been moved/linked, back to the original location in /var with original attributes (using tar). If backup was not turned on, it will still attempt to move the applications back to /var using the files in /media, but without original file attributes. This may take several minutes to complete. It will show each application progress.

'''To cleanup and remove directories and symlinks'''

<code>mvapp clean domain.appname</code>

If you have any issues, first attempt to remove the app from the App Catalog or Homebrew app installer. Then issue the 'clean' command to remove the applications directories at both locations and also the symlink. You can then reinstall the app from the App Catalog or any Homebrew App installer.

== Contingency Plan==

If you have problems with an application, follow these steps... 
-- Close the application if open 
-- mvapp unlink domain.appname 
-- Try using the App 

If the application still does now work correctly... 
-- Remove the App using official methods 
-- mvapp clean domain.appname 
-- Reinstall through the App Catalog or Homebrew installer app 

== Proposal to Dev Community ==

This is a formal proposal to the Dev Community suggesting that PreWare, WebOS Quick Install and other Pre installer apps provide an option to move any app in /var to the /media fs and create a link similar to the code above.

The Homebrew Community somewhat created part of the storage problem so needs to come up with their own solution. The symbolic link proponents propose that Homebrew apps be moved with a link to /media/internal by default and physically use /var only if needed (per conditions stated below). The developer would put a flag in the package (or some other method during submission) to state their app is able to run linked to /media or if it specifically needs to physically be on /var. Will propose additions to Packaging Standards to support /media links. The homebrew installer apps could then automatically do the move/link if the package is flagged for it.

Candidate apps for moving to /media 
- apps that do not depend on file attributes not supported by FAT (such as sticky bit or internal links) - The script (post 0.2.0 now deals with this). 
- apps that do not perform data operations to home app directory when device is USB mounted 

Exceptions for maintaining apps on /var 
- apps that depend on file attributes not supported by FAT - The script (post 0.2.0 now deals with this). 
- apps that won't work well when device is USB mounted, such as performing data or DB operations in home app directory 

(Please update with other known candidates/exceptions)

== Benefits over other methods ==

''Resizing /var'' 
One challenge with resizing /var is that it will still have a fixed static limit - how do you decide how much to increase it? Many will still probably hit the limit or waste space if setting too high. There is also the warning from Palm that resizing var may interfere with future updates. The link method allows to dynamically use the /media partition, so there is no need to set a specific size dedicated to apps. If the USB drive is filled, users can decide if they use the space for media or apps on the fly.

''AppPath in /etc/luna.conf'' 
I proposed a while back adding an AppPath to luna.conf to include apps stored on /media. Some apps would not work because some apparently reference /var. IE, the vampire/mafia/quest series could not access graphics. The symbolic link fixed this because apps think they are in /var.

''Link/mount [[all]] of /var/usr/palm/applications/ to /media/internal'' 
If some apps rely on file attributes this won't work since file attributes are lost when moved to FAT fs. While this is rare, it probably isn't wise to force all /var apps to /media. Selectively moving apps one at a time is less risky. Update: Have found that "PDF View" app does not allow to be linked, so it appears that selectively moving apps is necessary.

''Creating a loopback filesystem to a virtual file located on /media/internal'' 
This has been worked on [http://www.webos-internals.org/wiki/Tutorials_Linux_opt_on_loopback here] and still has potential. Unfortunately it locks out USB mount and media sync altogether. If a workaround can be found with low risk, this may be the most ideal solution.

== Risks, Issues, Dependencies ==

- Some file attributes of linux fs are not possible on FAT fs (USB drive). The 0.2.0 version (and higher) now deals with any apps that cannot copy attributes/permissions properly. The script will not move apps that have special attributes or conditions that FAT fs can't deal with. In general, this has been resolved. No known issues with apps since version 0.2.0 or later.

- Some apps may not behave well if USB drive is mounted to computer, though I've tested several that behaved fine. Linux type background services probably would not work well so probably should not be moved, however I'm not aware of any service stored in the app home directory - they are usually setup somewhere else. Apps that do IO to the home directory of the app while USB mounted may have issues when located on /media. I'm not aware of any apps that write to their own home directory, so this may not be a risk in general, but is still a possibility. If you run into issues with an app, see the Contingency Plan.

== Future Versions ==

Plans for future versions...

- The script will soon be modified to be friendly for javascript calls... no prompting and no output, just result codes. Will still maintain user interaction capability as well.

== Confirmed Apps ==
=== Apps Confirmed ''Not'' to Work ===
com.palm.app.pdfviewer (script v0.2.0 and higher properly handles this, won't allow it to move)

== Discuss ==
Discuss in the Discussion tab or PreCentral...

http://forums.precentral.net/web-os-development/205649-resolution-app-catalog-install-limit-proposal.html

'''Your Experiences'''

Please post your experiences, good or bad. I'd like to get any kinks worked out before attempting to turn this into a webOS app.

- How many apps did you move? 
- Did you find an app that won't work linked? 
- Did you move any back? (please test) 
- How far down did you have to get /var.../applications down in MB before you could start adding apps from the App Catalog? 

== Credits ==
xorg - initially developed script and proposal. maintainer of this page. 
daventx - added unlink and clean functions.

Application:Preware

2009-10-09T13:52:09Z

Nt4cats: /* Adding reference to AutoPatch transition URL */

{{application
|name=Preware
|type=webOS
|version=Version: Beta 0.9.3 (9 Oct 2009)
|tag=Utilities
|screenshot=Application_Preware_List.png
|description=

== Summary ==
{{icon|Icon_Preware.png|float:right;}}
Preware is a package management application for the Palm Pre. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.

This application was the result of extensive community-based design in [[IPKG Service]] and [[Preware Design]].

For application management, Preware can access more applications, and has more features, than any other on-device package installer.

And since it is open source, and has a completely open development process supported by a team of world-class WebOS Internals developers, it will continue to get better much faster than any other package management application.

Preware is the open application installer that has been written specifically to support a homebrew ecosystem where any developer can upload any application to any submission site, and that application can then be installed by any user. Developers no longer need to upload their applications to multiple submission sites, and users are no longer excluded from accessing applications from any open standard package repository.

== Status ==

This is beta software. Even so, as of 27 August 2009 it is the only over-the-air installer for the palm capable of installing advanced palm applications such as the [[On_Screen_Keyboard|on screen keyboard]] or the terminal application. Also as of 27 August 2009 it is the only application supporting installation from all existing palm homebrew feeds. As of 17 September 2009 it also supports installation of themes. As of 8 October 2009 it also supports installation of webos patches.

== License ==

Please be aware that org.webosinternals.preware and org.webosinternals.ipkgservice are licensed under the GPLv2.

They cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the authors.

== Operating notes ==

=== Limitations ===

Preware does not individually sequence dependencies during installation, and ipkgservice only runs the postinst and prerm scripts for the requested app, so if you have a dependency for the app that you're installing, and that dependency needs a postinst or prerm script to be run, then it will fail to run them. Please install the dependency first, and then install the app that you want. This will be fixed before the 1.0.0 version.

=== Known bugs ===

No known bugs.

== Installation ==

You do not need to access the Linux command line or "root your Pre" to install or use Preware.

Please use the [http://forums.precentral.net/homebrew-apps/206905-webos-quick-install-v2-7-beyond.html WebOS Quick Install] tool to install the Package Manager Service and the Preware application directly from the WebOS Internals feed.

No other application installer tool is sophisticated enough to install the custom Package Manager Service that Preware requires. Preware can install it, but you need a way to bootstrap Preware first, so you need to use WebOS Quick Install for the very first installation of Preware.

Note that Preware works just as well on the Emulator as it does on a real device, and is installed in exactly the same way.

=== Installation Steps ===
* Run WebOS Quick Install
* Press the third button on the right
* Choose WebOS Internals Feed (all) from the dropdown list at the top.
* Select ''Package Manager Service'' from the list.
* Press DOWNLOAD.
* Press INSTALL.
* Press the third button on the right
* Choose WebOS Internals Feed (all) from the dropdown list at the top.
* Select ''Preware'' from the list.
* Press DOWNLOAD.
* Press INSTALL.

=== Updating ===

'''Make sure you update the Package Manager Service first, and the Preware application second'''. When dependencies are supported, this restriction will be lifted.

If you are running a version of the Preware prior to 0.9.0, then you must use the WebOS Quick Install program to upgrade the Package Manager Service.

To update Preware or the Package Manager Service, simpy use Preware version 0.9.0 or later.

If you are updating to Preware version 0.9.3 and you have used the autopatch-feed package, please follow these [http://forums.precentral.net/webos-patches/208312-autopatch-transitioning-webos-patches-feed.html] directions for the update.

=== Removal ===

Why would you ever want to remove Preware?

To remove Preware, use WebOS Quick Install's Device Management page and unselect the Package Manager Service and the Preware application.

=== Recent enhancements ===

0.9.3: Adds the webos-patches feed, and feed management support.

0.9.1: Adds the All category, plus other miscellaneous fixes.

0.9.0: Now supports themes, restart flags and the new memory-reduction service methods.

0.8.5: Massive speed improvement on loading, now supports package types and adding feeds.

0.8.2: More preferences added and now functional, with listing and update frequency options.

0.8.1: Preferences scene implemented. Upstart job stops on removal.

0.8.0: Now supports Descriptions and Screenshots.

0.7.7: Addition of ipkglog and config list, and if ipkgservice fails at start it notifies people, and if it fails after postinst it considers it complete anyways

0.7.6: Fixed the superfluous update subscription message windows

0.7.5: Fixed update subscription oddity.

0.7.4: Fixed remounting of root filesystem for post-install and pre-remove scripts on the Pre.

0.7.1: Fixed buttons and title on script view screen.

0.7.0: Initial support for post-install and pre-remove scripts, including secure informed user consent. Does not work properly with dependencies yet, so please install dependencies one at a time.

0.6.7: Fixed bug in category drop-down list.

0.6.6: Fixed bug in package size reporting.

0.6.5: Updated icon and other graphical annotations.

0.6.4: Categories drop-down bug fixed. Preware category updated.

0.6.2: Categories now work to some extent. Still a bug in the drop down box.

0.6.1: Sorting by name or date is now available. Application details screen is much more organized.

0.6.0: No user visible changes. Preparation for the secure informed user consent functionality.

0.5.1: Filtering is now available on the list screens. Just start typing ...

== Repository ==

Preware and the Package Manager Service are housed in the applications/preware and services/ipkservice git repositories at http://git.webos-internals.org/

For commit permission to the open source project, contact rwhitby on #webos-internals or email [[mailto:support@webos-internals.org support@webos-internals.org]]

== Alternative Installation (ADVANCED/CLI Method)==

Really, unless you *really* know what you are doing, you should use the WebOS Quick Install installation instructions above.

This method is for '''LINUX EXPERTS ONLY''' and depends on the ipkg.preware.org/feeds/webos-internals repository. You must install the [[Application:Terminal]] application first to set up the feeds correctly.

=== Installing via IPKG ===

Really, unless you *really* know what you are doing, you should use the WebOS Quick Install installation instructions above.

If you have never configured the ipkg feed perform the following, then follow directions below:
<source lang="text">
mount -o remount,rw /

mkdir -p /var/etc/ipkg/
ln -s /etc/ipkg/arch.conf /var/etc/ipkg/
echo "src/gz webosinternals http://ipkg.preware.org/feeds/webos-internals/all" > /var/etc/ipkg/webos-internals.conf

echo "src/gz webosinternals-armv7 http://ipkg.preware.org/feeds/webos-internals/armv7" >> /var/etc/ipkg/webos-internals.conf
</source>

If you have already configured the ipkg feed, perform the following:
<source lang="text">
mount -o remount,rw /

/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var install org.webosinternals.ipkgservice
/usr/bin/ipkg -o /var install org.webosinternals.preware
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

=== Updating via IPKG ===

Really, unless you *really* know what you are doing, you should use the Preware update instructions above.

If you are already running Preware 0.9.0 or later, you should use the Preware update instructions above.

<source lang="text">
mount -o remount,rw /

/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var upgrade
sh /var/usr/lib/ipkg/info/org.webosinternals.ipkgservice.postinst
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

mount -o remount,ro /
exit
</source>

}}

Development & Tweak Ideas

2009-10-07T18:01:58Z

Nt4cats: /* Tweak Ideas */

Here are some ideas for tweaks which have not been implemented yet (to my knowledge):

If you decide to start working one of these, '''please leave a note''' under the item as a second-level bullet. If you don't have wiki access, find someone in the IRC channel who does. This will help encourage collaborative discovery, and reduce duplicate effort. We also recommend starting a new wiki page where you '''take notes about any discoveries''' you've made related to the tweak idea.

Once you've figured it out, it would be appreciated if you make a write-up for the Stock App Mods page. If you don't want to do a write up, at least try to share your findings with someone who can subsequently document them for you. At the very least, jot a few notes onto a wiki page, and tag it with "cleanup".

=Patch Ideas=
* Create a patch for showing day events in month view on calendar
* Restore "Ignoring calendar alarm repeats the alarm in 5 minutes" to WebOS 1.10, the way it was in WebOS 1.04 and Palm
* Enable simultaneous Voice and Data access.

=Tweak Ideas=
* Device automatically goes into USB Drive Mode without tapping on the option (For bad touchscreen issues). Another option is to do an Orange + Symbol + key sequence for that.
* Make bootup faster (parallel?)
** See [http://ubuntuforums.org/showthread.php?t=727224 Upstart on Ubuntu info]
* Fix the horrendous white balance issues with the camera (especially with the flash on)
** See http://www.theregister.co.uk/2009/06/25/cameraphone_faceoff/ for a post showing the problems.
* Make the Pre vibrate differently based on caller ID
** See http://www.azarask.in/blog/post/know-whos-calling-tactile-design/
*Enable image saving/save to wallpaper from the browse.
*Enable opening PDF/doc whatever from Web browser.
** //Done a slight bit of testing with this. It's very easy to get the browser to pass along a link to the application (tested with PDF). <code>/usr/palm/command-resource-handlers.json</code> contains all of the MIME types and you just have to change <code>streamable</code> to true. Of course, the application itself has an issue with this and errors out.//
* Enable uploads in a browser (dialog box with browse, etc.).
* Enable track skipping without turning the device on.
** [[Hardware Key Track Skip]]
** [[track-skipping-using-volume-up-down-buttons|Skip tracks using volume up/down buttons]] ~ FXDemolisher
* Quick copy of locked calendar events to the local calendar so that they can be edited.
* Make the Pre vibrate longer.
** tictac is working on this [[make-pre-vibrate-longer | here]].
* Allow other messaging protocols using libpurple plugins (Facebook, Jabber, etc.).
* Trigger camera remotely.
** Wonder420 is working on this [[camera-remote-view | here]].
* Back up contact link information. (This is currently not stored in the Palm Profile, so it will be lost on a device wipe.) -- [[Contact Link Backup]]
* Landscape virtual keyboard in the Web app.
* Find better touch scroll threshold numbers so the action is not as jerky/fuzzy while moving. 1.0.3 update seems to have improved that a bit.. //~ Robi//
* Look into [http://www.lesswatts.org/projects/powertop/ PowerTop] to potentially save even more power and extend batt life. //~ Robi//
* Allow universal search to search through email text as well
* Multiple card rows in the small card view
* Add a "scrubber" to the music app to control song position
* Remove Amazon section from music app to see if it loads faster without (Music app loads instantly but then you have to wait 30 seconds or so before you can do anything until the Amazon section shows up).
** Unfortunately it seems that it's the thumbnail creation for the few albums shown in shuffle all that causes the delay- removing the Amazon entry doesn't seem to change the speed at all.
* Change the sorting of the music app so that A, An, The in band names and album names are ignored and it sorts alphabetically using the next word [[Patch MediaPlayer Ignore 'A', 'An', and 'The' In Artist and Album names]] ~ Keegan99
* In the camera app, use the volume up/down buttons to snap a picture.
** [[Patch Camera Using Volume Buttons to Take a Picture|Take a picture using volume buttons]] ~ FXDemolisher
* When camera app loads, also load photos app (for quicker review). Even better, let user choose to "keep" or "delete" a picture, and keep the photo on the screen until a choice is made.
* Stop the alert noise from obnoxiously playing every single time you put the Pre back on the Touchstone.
** [[remove-charging-event-alerts]]
* Set up the center button to wake the Pre up, like an iPhone's home button wakes up the iPhone.
* Allow copy to work from google maps, so you can get a url of your current location to paste in chats/sms/mms //~ hemna//
* Light up Navi lights when a notification is received
* Setting to disable ring for Unknown Number
* When the clock's alarm goes off, it only turns on the screen for the customary ~2 seconds before shutting the screen off. Change this to keep the screen on as long as the alarm is playing, then go to sleep when the "snooze" button is pressed.
* Make "all-day" appointments show up in calendar month view (currently invisible)
** [[Patch Calendar Show All-Day Events in Month View]] //~ Sloloem//
* Allow the phone app to run in the background, without a visible card, (to speed up ringtone playing on incoming phone calls).
* Disable the end call sound and the low battery sound.
* Add the ability to snooze a calendar reminder for a certain amount of time that user can choose.
** [[Patch Clock Changing Alarm Button Order and Snooze Duration]] //~ HebrewzHammer//
* Add additional gstreamer plugins into the gstreamer plugin directory; should allow adding support for additional media formats pretty easily.
* Make Contacts app and Universal Search search ALL contact fields. Similar to Google Contacts.
* Provide for two different brightness levels, one (brighter) for while charging, with another for when the Pre is on battery // Proposed on irc by navinag //

=Development Ideas=
Get [[vnc | VNC]] input working with a mouse and keyboard driver. //~ ultraBlack//

Get [http://synergy2.sourceforge.net/ Synergy] working with a mouse and keyboard driver. :O Why not? :P //~ ultraBlack//

Develop a power calculator app for the Pre, with DIGIT-GROUPING, more functions, and possibly even a graphing mode. //~ ultraBlack//

Put [http://www.mozilla.com/en-US/products/download.html?product=firefox-3.0.11&os=linux&lang=en-US Firefox] on it. Definitely not practical. Maybe [http://portableapps.com/node/9364 Portable Firefox?] //~ ultraBlack//
* Consider [http://www.opera.com/mobile/ Opera Mobile] or [http://www.opera.com/mini/ Opera Mini] as more worthwhile alternatives. //~ ultraBlack//
* Opera Mobile can successfully upload files to web servers. (re: idea to upload via browser) //~ oc80z//

Work out a good backup solution, perhaps mrb or netapp like .snapshots, so updates/upgrades are easier. //~ Robi//

Look into setting up [[ad-hoc networking | ad-hoc networking]] for file sharing over WiFi and BitTorrent. //~ Robi//

Put [http://www.apache.org/ Apache] on it. //~ ultraBlack// Done. http://predev.wikidot.com/apache //~nebula//
* Consider [http://www.lighttpd.net/ Lighttpd] or [http://www.cherokee-project.com/ Cherokee] as more worthwhile alternatives. //~ Robi//
* For limited needs thttpd + php as shown in [[ajaxphpterm]] seems to work fine with minimal resource usage. //~ djbclark//
* Sprint blocks connections to the Pre on port 80, but port 2222 and 8080 has been tested and work //~ smashman// 8000 also works //~nebula//

Make LunaSysMgr run without exclusive access to I/O, so it can be run alongside [[DirectFB]] applications (and since directfb can run GTK, QT, and X11 applications directly, also those). Some ideas on how to do this are on the [[DFBTerm DirectFB Terminal Emulator]] page's "Virtual Keyboard-Video-Monitor (KVM) Switch" section, however if LunaSysMgr source code becomes available the best method would probably be to just change it to run against directfb instead of using /dev/fb* and /dev/input/* directly. //~ djbclark//

Confirm that the device is free of Digital Restrictions Management (DRM) by installing Linux compiled from source. There is a /proc/config.gz, and palm has released the patches they used at http://opensource.palm.com/packages.html (search for "linux kernel"). This may also be useful as linux patches may be needed for some of the other ideas on this page. //~ djbclark//
* Done by //~ rwhitby// and //~ tonycpsu// at [[Custom Kernels]]

Possibly easier accessing linux procedure - create an .ipk (ipkg) file that does the accessed linux setup; have user execute either by emailing them the file (it has been confirmed that you can install ipkg files via the email client), and/or by having them temporarily manually set their DNS to a DNS server that would direct the app store somewhere else. //~ djbclark//

Make directfb (via tslib - http://tslib.berlios.de/ - or gpm - http://unix.schottelius.org/gpm/ ) work with the palm pre's /dev/touchscreen (new driver CONFIG_TOUCHSCREEN_CY8MRLN=y (cypress touchscreen) included in http://palm.cdnetworks.net/opensource/1.0.1/linux-2.6.24-patch.gz) - see [[vala-terminal]] for more details. //~ djbclark//

Add more Bluetooth profiles/support such as HID so that BT keyboards can be used.

Enable printing - my testing of CUPS install failed on the 'insmod' file missing, could not installed printer driver, CUPS-DOC worked and the web interface was functioning well on localhost from the Pre browser. //~ dld121//

Implementing a learning autocorrect system. Perhaps just a process that monitors keyboard input and removes //word// from the dictionary when //word//<space><backspace>//nextword// is found.

Create or port a Usenet news reader under WebOS

Figure out how to add custom gestures to the screen/gesture area. (I'd really like to tap around the center button to emulate a 5-way pad.)

RSS Reader (Importable Feeds, Subscription to podcasts) //~ oc80z//

Get [http://www.freesmartphone.org/ (FSO) ]working on the Palm Pre as an alternative platform to the nonfree [http://www.freesmartphone.org/index.php/HardwareInteresting_Targets LunaSysMgr GUI] - http://laforge.gnumonks.org/weblog/2009/06/20/20090620-palm_pre_wanted //~ djbclark// [http://www.freesmartphone.org/index.php/Palm_Pre Links and community organizing.]

TASK application - add categories column A-B-C like, and priority column 1-2-3-4-5, like the Treo755p Task application. Make them sortable by clicking on column header. Additional development: maybe some way to sync the Tasks with desktop or web based interface