Next steps

2009-08-05T13:53:34Z

Hoxworth: /* Finishing */

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes an SSH program (''dropbear'') and an sftp program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

'''If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].'''

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
sh optware-bootstrap.sh
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address with [http://checkmyip.com/ CheckMyIP.com]
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Avahi

2009-08-05T13:52:00Z

Hoxworth: New page: =Avahi= [http://avahi.org Avahi] is a Linux service for providing multicast-DNS/DNS-SD (also known as [http://en.wikipedia.org/wiki/Bonjour_%28software%29 Bonjour] or mDNS/DNS-SD). Avahi a...

=Avahi=
[http://avahi.org Avahi] is a Linux service for providing multicast-DNS/DNS-SD (also known as [http://en.wikipedia.org/wiki/Bonjour_%28software%29 Bonjour] or mDNS/DNS-SD). Avahi allows for simple service discovery and advertisement on a local network and provides name resolution for all hosts running a mDNS/DNS-SD service.

Using Avahi allows for easy SSH access over a local wireless network. Once installed and started, users can ssh to their device using their mDNS assigned hostname.

==Avahi Installation==

First, mount the root filesystem as writable and install the Avahi ipkg.

$> sudo mount -o remount,rw /
$> sudo /opt/bin/ipkg-opt install avahi

Avahi currently attempts to access a different dbus system socket than the one provided by the Pre's dbus, so we need to turn off dbus access for the time being. Edit <tt>/opt/etc/avahi/avahi-daemon.conf</tt> and make the following change:

Replace this line:
#enable-dbus=yes

With this line:
enable-dbus=no

At this point, the Avahi daemon can be started with the following command:

$> sudo /opt/sbin/avahi-daemon -D

If you would like Avahi to start up at boot, create the following two files:

'''/opt/etc/init.d/S60avahi''':
!/bin/sh

[ -e /opt/etc/default/avahi ] && . /opt/etc/default/avahi

if [ "$AVAHI_ENABLE" = "no" ]; then
exit
fi

if [ -n "`pidof /opt/sbin/avahi`" ]; then
killall /opt/sbin/avahi 2>/dev/null
fi

/opt/sbin/avahi-daemon -D

'''/opt/etc/default/avahi''':
AVAHI_ENABLE=yes

Make sure you set the startup script to executable:

$> sudo chmod 755 /opt/etc/init.d/S60avahi

==Connecting via SSH using mDNS==

mDNS uses the system's hostname and appends it to the <tt>local.</tt> domain. Using the Pre's default <tt>castle</tt> hostname, the following command would be used to SSH to your Pre on port 222:

$> ssh -P 222 castle.local.

'''Note: The system that you are connecting from MUST have a mDNS service also running, else the hostname will not resolve'''

==Current Issues==

* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I haven't investigated tying these two together too much, but the expanded functionality of accessing mDNS via dbus is preferred.
* The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.

WebOS Internals - User contributions [en]

Next steps

Avahi