WebOS Internals - User contributions [en]

User:Ragingmind

2011-03-30T14:18:05Z

Ragingmind: Created page with "I am also RagingMind on #webos-internals"

I am also RagingMind on #webos-internals

Accessing Linux Debian

2011-03-30T14:08:54Z

Ragingmind: took out emails so that I don't get spam every time an email scraper reads the page

Though the Ubuntu packages that Palm distributes will install on most linux systems, unless you have converted your Debian system to use the upstart daemon novacomd will not start automatically when your computer does. This can be fixed quite easily by installing a sysv style init script and adding it to the boot process.

These steps must be run as root

1. Download the palm-novacom package for your system (only tested with the 32bit package so far)

2. Switch to root and install the package

3. Save this script as /etc/initd.d/novacomd and be very careful to not touch any other files in this directory

<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: novacomd
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: palm novacom daemon
# Description: Daemon for connecting to palm devices
### END INIT INFO

# Based on /etc/init.d/skeleton
# Edited by Members of the MTU LUG. lug.mtu.edu

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/opt/Palm/novacom
DESC="Palm daemon to connect to webOS devices"
NAME=novacomd
DAEMON=/opt/Palm/novacom/$NAME
DAEMON_ARGS="--daemonize"
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --quiet --exec $DAEMON --test > /dev/null \
|| return 1
start-stop-daemon --start --quiet --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
}

#
# Function that stops the daemon/service
#
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
# Wait for children to finish too if this is a daemon that forks
# and if the daemon is only ever run from this initscript.
# If the above conditions are not satisfied then add some other code
# that waits for the process to drop all resources that could be
# needed by services started subsequently. A last resort is to
# sleep for some time.
start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
[ "$?" = 2 ] && return 2
# Many daemons don't delete their pidfiles when they exit.
rm -f $PIDFILE
return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
#
# If the daemon can reload its configuration without
# restarting (for example, when it is sent a SIGHUP),
# then implement that here.
#
start-stop-daemon --stop --signal 1 --quiet --name $NAME
return 0
}

case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
#reload|force-reload)
#
# If do_reload() is not implemented then leave this commented out
# and leave 'force-reload' as an alias for 'restart'.
#
#log_daemon_msg "Reloading $DESC" "$NAME"
#do_reload
#log_end_msg $?
#;;
restart|force-reload)
#
# If the "reload" option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
#echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac

:
</pre>

4. Run:

<pre>
update-rc.d novacomd defaults
</pre>

Building a Debian chroot image

2011-03-30T14:06:32Z

Ragingmind: Fixing some minor gramar oops-es and updating some wording to be more clear

Building your own image for a chroot can be quite handy especially if you would like to customize what comes pre-installed. The following steps should work as-is on a Debian Squeeze system. They should also work for Ubuntu, but the name of the qemu package that provides the necessary binary is different. Please see [[Debian chroot]] for instruction on how to actually use this image on the Pre.

Required packages: debootstrap, qemu-user-static, binfmt-support

==Creating the image file==
Pick a directory to work in on your desktop/laptop computer. All the commands are relative to the current directory so it shouldn't matter where, so long as you have write access.
<source lang="bash">
dd if=/dev/zero of=DebianSqueeze_armel.img bs=1M count=512
mkdir build
</source>

Now to put an ext2 file system in that blank file. '''The rest of these steps require being run as root.''' Note the loop device output by the first command, it will probably be ''loop0'' and in the examples below this is what you'll put in for ''[device]''
<source lang="bash">
losetup -f
losetup -f DebianSqueeze_armel.img
mkfs.ext2 /dev/[device]
</source>

==Building a system==
Now we can fill the image with Magic *cough* I mean Debian 6.0.x "squeeze"
<source lang="bash">
mount /dev/[device] build/
debootstrap --arch armel --foreign squeeze build/ http://ftp.us.debian.org/debian
</source>

At this point the system is only partially setup. This next step with debootstrap would have to be preformed on the Pre, but with the help of qemu and binfmt we can do that on our desktop as well.
<source lang="bash">
cp /usr/bin/qemu-arm-static build/usr/bin/
chroot build/
/debootstrap/debootstrap --second-stage
</source>

Now that the base system is installed and set up there is some minor housekeeping that we can do before transferring everything to the Pre. First we will clear apt's cache and then add a default mirror to sources.list

<source lang="bash">
apt-get clean
echo "deb http://ftp.us.debian.org/debian squeeze main" > /etc/apt/sources.list
</source>

This next step is entirely optional and if you don't understand what it will do to the default choices made by apt when installing packages then '''I strongly recommend skipping it'''. It is only useful to keep space usage down, but at the cost of functionality.
<source lang="bash">
echo 'APT { Install-Recommends "false"; };' > /etc/apt/apt.conf.d/50no-recommends
</source>

Exit the chroot
<source lang="bash">
exit
</source>

==Cleaning up==
A few steps to clean up on your desktop.
<source lang="bash">
rm build/usr/bin/qemu-arm-static
umount build/
losetup -d /dev/[device]
</source>

==Tada!==
Now you have an image of Debian Squeeze that you can use on your Pre. This is where you transfer the image to the USB drive and there are several ways to do that.

==More Resources==
[http://wiki.debian.org/Debootstrap deboostrab on the debian wiki]

[http://wiki.debian.org/EmDebian/CrossDebootstrap information about cross debbootstrap on the debian wiki]

[http://www.digriz.org.uk/debootstrap-qemu helpful guide on digriz.org.uk]

Building a Debian chroot image

2011-03-30T02:29:29Z

Ragingmind: updating dirctory names to be consistant

Having a custom image for your chroot can be quite handy especially if you would like to customize what comes pre-installed. The following steps should work as-is on a Debian Squeeze system. They should also work for Ubuntu, but the name of the qemu package that provides the necessary binary is different. Please see [[Debian chroot]] for instruction on how to actually use this image on the Pre.

Required packages: debootstrap, qemu-user-static, binfmt-support

==Creating the image file==
Pick a directory to work in on your desktop/laptop computer. All the commands are relative to the current directory so it shouldn't matter where, as long as you have write access.
<source lang="bash">
dd if=/dev/zero of=DebianSqueeze_armel.img bs=1M count=512
mkdir build
</source>

Now to put an ext2 file system in that blank file. '''The rest of these steps require being run at root.'''
<source lang="bash">
losetup -f
</source>
Note the loop device output by this, it will probably be loop0 and in the examples below this is what you'll put in for [device]
<source lang="bash">
losetup -f DebianSqueeze_armel.img
mkfs.ext2 /dev/[device]
</source>

==Building a system==
Now we can fill the image with Magic *cough* I mean Debian 6.0.x "squeeze"
<source lang="bash">
mount /dev/[device] build/
debootstrap --arch armel --foreign squeeze build/ http://ftp.us.debian.org/debian
</source>

At this point the system is only partially setup. This next step would have to be preformed on the Pre, but with the help of qemu and binfmt we can do that on our desktop as well.
<source lang="bash">
cp /usr/bin/qemu-arm-static build/usr/bin/
chroot build/
/debootstrap/debootstrap --second-stage
</source>

Now that the base system is installed and set up there is some minor housekeeping that we can do before transferring everything to the Pre. First we will clear apt's cache and then add a default mirror to sources.list

<source lang="bash">
apt-get clean
echo "deb http://ftp.us.debian.org/debian squeeze main" > /etc/apt/sources.list
</source>

This next step is entirely optional and if you don't understand what it will do to the default choices made by apt when installing packages then I strongly recommend skipping it. It is only useful to keep space usage down, but at the cost of functionality.
<source lang="bash">
echo 'APT { Install-Recommends "false"; };' > /etc/apt/apt.conf.d/50no-recommends
</source>

Exit the chroot
<source lang="bash">
exit
</source>

==Cleaning up==
A few steps to clean up on your desktop.
<source lang="bash">
rm build/usr/bin/qemu-arm-static
umount build/
losetup -d /dev/[device]
</source>

==Tada!==
Now you have an image of Debian Squeeze that you can use on your Pre. This is where you transfer the image to the USB drive and there are several ways to do that.

==More Resources==
[http://wiki.debian.org/Debootstrap deboostrab on the debian wiki]

[http://wiki.debian.org/EmDebian/CrossDebootstrap information about cross debbootstrap on the debian wiki]

[http://www.digriz.org.uk/debootstrap-qemu helpful guide on digriz.org.uk]

Building a Debian chroot image

2011-03-30T02:20:54Z

Ragingmind:

Having a custom image for your chroot can be quite handy especially if you would like to customize what comes pre-installed. The following steps should work as-is on a Debian Squeeze system. They should also work for Ubuntu, but the name of the qemu package that provides the necessary binary is different. Please see [[Debian chroot]] for instruction on how to actually use this image on the Pre.

Required packages: debootstrap, qemu-user-static, binfmt-support

==Creating the image file==
Pick a directory to work in on your desktop/laptop computer. All the commands are relative to the current directory so it shouldn't matter where, as long as you have write access.
<source lang="bash">
dd if=/dev/zero of=DebianSqueeze_armel.img bs=1M count=512
mkdir build
</source>

Now to put an ext2 file system in that blank file. '''The rest of these steps require being run at root.'''
<source lang="bash">
losetup -f
</source>
Note the loop device output by this, it will probably be loop0 and in the examples below this is what you'll put in for [device]
<source lang="bash">
losetup -f DebianSqueeze_armel.img
mkfs.ext2 /dev/[device]
</source>

==Building a system==
Now we can fill the image with Magic *cough* I mean Debian 6.0.x "squeeze"
<source lang="bash">
mount /dev/[device] build/
debootstrap --arch armel --foreign squeeze mnt/ http://ftp.us.debian.org/debian
</source>

At this point the system is only partially setup. This next step would have to be preformed on the Pre, but with the help of qemu and binfmt we can do that on our desktop as well.
<source lang="bash">
cp /usr/bin/qemu-arm-static mnt/usr/bin/
chroot mnt/
/debootstrap/debootstrap --second-stage
</source>

Now that the base system is installed and set up there is some minor housekeeping that we can do before transferring everything to the Pre. First we will clear apt's cache and then add a default mirror to sources.list

<source lang="bash">
apt-get clean
echo "deb http://ftp.us.debian.org/debian squeeze main" > /etc/apt/sources.list
</source>

This next step is entirely optional and if you don't understand what it will do to the default choices made by apt when installing packages then I strongly recommend skipping it. It is only useful to keep space usage down, but at the cost of functionality.
<source lang="bash">
echo 'APT { Install-Recommends "false"; };' > /etc/apt/apt.conf.d/50no-recommends
</source>

Exit the chroot
<source lang="bash">
exit
</source>

==Cleaning up==
A few steps to clean up on your desktop.
<source lang="bash">
rm mnt/usr/bin/qemu-arm-static
umount mnt/
losetup -d /dev/[device]
</source>

==Tada!==
Now you have an image of Debian Squeeze that you can use on your Pre. This is where you transfer the image to the USB drive and there are several ways to do that.

==More Resources==
[http://wiki.debian.org/Debootstrap deboostrab on the debian wiki]

[http://wiki.debian.org/EmDebian/CrossDebootstrap information about cross debbootstrap on the debian wiki]

[http://www.digriz.org.uk/debootstrap-qemu helpful guide on digriz.org.uk]

Building a Debian chroot image

2011-03-30T01:16:49Z

Ragingmind: Created page with "I will fill this in within a few minutes."

I will fill this in within a few minutes.

Talk:Debian

2011-03-30T01:03:32Z

Ragingmind: moved Talk:Debian to Talk:Debian chroot: The previous title was too ambiguous.

#REDIRECT [[Talk:Debian chroot]]

Talk:Debian chroot

2011-03-30T01:03:32Z

Ragingmind: moved Talk:Debian to Talk:Debian chroot: The previous title was too ambiguous.

===Doing it all on-device===

This entire process can be done on-device (if you're patient), as both bunzip2 and resize2fs exist on the Pre.

time bunzip2 debsmall.img.bz2

''real 2m 26.53s''

time resize2fs debsmall.img 1G

''real 17m 49.56s''

Also took about 20% of my battery (including the download over 3G), but hey, it works!

Debian

2011-03-30T01:03:31Z

Ragingmind: moved Debian to Debian chroot: The previous title was too ambiguous.

#REDIRECT [[Debian chroot]]

Accessing Linux Debian

2011-02-27T16:22:12Z

Ragingmind: Created page with 'Though the Ubuntu packages that Palm distributes will install on most linux systems, unless you have converted your Debian system to use the upstart daemon novacomd will not star…'

Though the Ubuntu packages that Palm distributes will install on most linux systems, unless you have converted your Debian system to use the upstart daemon novacomd will not start automatically when your computer does. This can be fixed quite easily by installing a sysv style init script and adding it to the boot process.

These steps must be run as root

1. Download the palm-novacom package for your system (only tested with the 32bit package so far)

2. Switch to root and install the package

3. Save this script as /etc/initd.d/novacomd and be very careful to not touch any other files in this directory

<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: novacomd
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: palm novacom daemon
# Description: Daemon for connecting to palm devices
### END INIT INFO

# Based on /etc/init.d/skeleton
# Edited by Christian Jacobsen <cjjacobs@mtu.edu> with help from Brian McPherson <bamcpher@mtu.edu>

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/opt/Palm/novacom
DESC="Palm daemon to connect to webOS devices"
NAME=novacomd
DAEMON=/opt/Palm/novacom/$NAME
DAEMON_ARGS="--daemonize"
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --quiet --exec $DAEMON --test > /dev/null \
|| return 1
start-stop-daemon --start --quiet --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
}

#
# Function that stops the daemon/service
#
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
# Wait for children to finish too if this is a daemon that forks
# and if the daemon is only ever run from this initscript.
# If the above conditions are not satisfied then add some other code
# that waits for the process to drop all resources that could be
# needed by services started subsequently. A last resort is to
# sleep for some time.
start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
[ "$?" = 2 ] && return 2
# Many daemons don't delete their pidfiles when they exit.
rm -f $PIDFILE
return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
#
# If the daemon can reload its configuration without
# restarting (for example, when it is sent a SIGHUP),
# then implement that here.
#
start-stop-daemon --stop --signal 1 --quiet --name $NAME
return 0
}

case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
#reload|force-reload)
#
# If do_reload() is not implemented then leave this commented out
# and leave 'force-reload' as an alias for 'restart'.
#
#log_daemon_msg "Reloading $DESC" "$NAME"
#do_reload
#log_end_msg $?
#;;
restart|force-reload)
#
# If the "reload" option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
#echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac

:
</pre>

4. Run:

<pre>
update-rc.d novacomd defaults
</pre>