<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.webos-internals.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cerealklr</id>
	<title>WebOS Internals - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.webos-internals.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cerealklr"/>
	<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/wiki/Special:Contributions/Cerealklr"/>
	<updated>2026-04-24T11:50:53Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.1</generator>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Running_mysqld_in_chroot&amp;diff=21685</id>
		<title>Running mysqld in chroot</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Running_mysqld_in_chroot&amp;diff=21685"/>
		<updated>2012-02-20T23:46:16Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Added two forgotten steps in section two.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please be careful when following the instructions on this page. They are entirely from memory. If you'd like assistance along the way, have a specific reason for wanting to run mysqld, and are knowledgeable enough about linux/WebOS to help me help you work remotely on any issues that arise, I can be reached at cerealklr@&amp;lt;humans.should.remove.this.token&amp;gt;gmail.com. This guide assumes mysqld and its dependencies have already been installed, and that you are operating in a debian based chroot.&lt;br /&gt;
&lt;br /&gt;
* Create the user 'mysql' for the daemon to run as.&lt;br /&gt;
** Create the user itself. &amp;lt;pre&amp;gt;adduser --system mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Create a group for the user. &amp;lt;pre&amp;gt;addgroup --system mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the user to the group. &amp;lt;pre&amp;gt;adduser mysql mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Create boilerplate my mysql's locking mechanisms.&lt;br /&gt;
** Create its /var/run directory. &amp;lt;pre&amp;gt;mkdir /var/run/mysqld&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Create the socket lock file. &amp;lt;pre&amp;gt;touch /var/run/mysqld/mysqld.sock&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Give the mysql group ownership of the run directory. &amp;lt;pre&amp;gt;chown -r root:mysql /var/run/mysqld&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Ensure corrent permissions on the run directory. &amp;lt;pre&amp;gt;chmod 775 /var/run/mysqld &amp;amp;&amp;amp; chmod 644 /var/run/mysqld/mysqld.sock&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Install the database &amp;lt;pre&amp;gt;mysql_install_db&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the above does not work, I've forgotten a step. Please email your terminal log to me so I can figure out what I forgot and amend the wiki.&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Running_mysqld_in_chroot&amp;diff=21683</id>
		<title>Running mysqld in chroot</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Running_mysqld_in_chroot&amp;diff=21683"/>
		<updated>2012-02-20T23:30:56Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Initial Entry&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please be careful when following the instructions on this page. They are entirely from memory. If you'd like assistance along the way, have a specific reason for wanting to run mysqld, and are knowledgeable enough about linux/WebOS to help me help you work remotely on any issues that arise, I can be reached at cerealklr@&amp;lt;humans.should.remove.this.token&amp;gt;gmail.com. This guide assumes mysqld and its dependencies have already been installed, and that you are operating in a debian based chroot.&lt;br /&gt;
&lt;br /&gt;
* Create the user 'mysql' for the daemon to run as.&lt;br /&gt;
** Create the user itself. &amp;lt;pre&amp;gt;adduser --system mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Create a group for the user. &amp;lt;pre&amp;gt;addgroup --system mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the user to the group. &amp;lt;pre&amp;gt;adduser mysql mysql&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Create boilerplate my mysql's locking mechanisms.&lt;br /&gt;
** Create its /var/run directory. &amp;lt;pre&amp;gt;mkdir /var/run/mysqld&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Create the socket lock file. &amp;lt;pre&amp;gt;touch /var/run/mysqld/mysqld.sock&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Install the database &amp;lt;pre&amp;gt;mysql_install_db&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the above does not work, I've forgotten a step. Please email your terminal log to me so I can figure out what I forgot and amend the wiki.&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=UbuntuChroot&amp;diff=21681</id>
		<title>UbuntuChroot</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=UbuntuChroot&amp;diff=21681"/>
		<updated>2012-02-20T22:29:05Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Added section for recommended power user utilities&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists.  '''If you have not already done so you should setup the ext3fs partition to mount at bootup.'''  (Failure to do so will cause you to run out of disk space)  Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.&lt;br /&gt;
&lt;br /&gt;
Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Instructions ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Intro: What you need to know===&lt;br /&gt;
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer. &lt;br /&gt;
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.&lt;br /&gt;
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.&lt;br /&gt;
&lt;br /&gt;
* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do end up messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''&lt;br /&gt;
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''&lt;br /&gt;
**'''You must remove Optware before beginning this process.  Failure to do so will most likely cause you issues!'''&lt;br /&gt;
&lt;br /&gt;
===Step 1: Creating a WebOS Doctor===&lt;br /&gt;
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.&lt;br /&gt;
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)&lt;br /&gt;
**[[Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Step 1: |Application:MetaDoctor - Setting up Meta-Doctor Step 1:]]&lt;br /&gt;
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says &amp;quot;# EXT3FS_PARTITION_SIZE = 2GB&amp;quot;. Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. '''BUT BE AWARE THAT THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU.''' Now save the file still with no file extension. &lt;br /&gt;
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.&lt;br /&gt;
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.&lt;br /&gt;
&lt;br /&gt;
===Alternative Step 1: Re-partitioning by hand===&lt;br /&gt;
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:&lt;br /&gt;
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.&lt;br /&gt;
&lt;br /&gt;
# connect with novaterm (not via quicklaunch as you can't see dialogs)&lt;br /&gt;
First determine how much actual space is being used by /media/internal (not whats allocated to it)&lt;br /&gt;
#&amp;lt;code&amp;gt; df -h | grep internal&amp;lt;/code&amp;gt;&lt;br /&gt;
Remember this as you will need to keep that in mind when you resize&lt;br /&gt;
Disconnect cryptofs:&lt;br /&gt;
# &amp;lt;code&amp;gt;pkill -SIGUSR1 cryptofs&amp;lt;/code&amp;gt;&lt;br /&gt;
Unmount /media/internal: &lt;br /&gt;
# &amp;lt;code&amp;gt;umount /media/internal&amp;lt;/code&amp;gt;&lt;br /&gt;
verify you have a clean filesystem *before* you resize it:&lt;br /&gt;
# &amp;lt;code&amp;gt;/usr/sbin/fsck.vfat /dev/mapper/store-media&amp;lt;/code&amp;gt;&lt;br /&gt;
Then verify how much space /media/internal is using&lt;br /&gt;
#&amp;lt;code&amp;gt; lvscan | grep media&amp;lt;/code&amp;gt;&lt;br /&gt;
For a 16GB TP you should only reduce the size by 4GB and for a 32GB TP you can safely reduce by 8GB&lt;br /&gt;
So this means if the size is 23GB on a 32GB TP your final space that you would resize to is ie: 23GB-8GB=15GB&lt;br /&gt;
# &amp;lt;code&amp;gt;resizefat /dev/mapper/store-media {size you determined it to be}G&amp;lt;/code&amp;gt; - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation will delete your data if you make it too small.&lt;br /&gt;
# &amp;lt;code&amp;gt;lvresize -L 4G /dev/mapper/store-media&amp;lt;/code&amp;gt;&lt;br /&gt;
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises &amp;lt;code&amp;gt;pkill -SIGUSR2 cryptofs&amp;lt;/code&amp;gt; here.&lt;br /&gt;
# &amp;lt;code&amp;gt; lvcreate -l 100%FREE -n ext3fs store &amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mkfs.ext3 /dev/mapper/store-ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -o remount,rw /&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;echo &amp;quot;/dev/mapper/store-ext3fs /media/ext3fs auto noatime 	0	0&amp;quot; &amp;gt;&amp;gt; /etc/fstab&amp;lt;/code&amp;gt;&lt;br /&gt;
# check to make sure nothing already exists under mount point: &amp;lt;code&amp;gt;ls -l /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
## If above shows files/dirs under /media/ext3fs, you will need to copy it and then move it back after mounting:&lt;br /&gt;
## &amp;lt;code&amp;gt;cd /media/ext3fs; tar -cf /tmp/ext3fs-files.tar .&amp;lt;/code&amp;gt;&lt;br /&gt;
## and then &amp;lt;code&amp;gt;rm -rf /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mkdir /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -o remount,ro /&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -a&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;reboot&amp;lt;/code&amp;gt;&lt;br /&gt;
# If files existed under /media/ext3fs before mounting, recreate them with:&lt;br /&gt;
## &amp;lt;code&amp;gt;cd /media/ext3fs ; tar xvf /tmp/ext3fs-files.tar ; rm /tmp/ext3fs-files.tar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.&lt;br /&gt;
&lt;br /&gt;
===Step 2: Mounting the ext3fs partition===&lt;br /&gt;
*Follow the intructions of the Chrooting wiki page.&lt;br /&gt;
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]&lt;br /&gt;
&lt;br /&gt;
===Step 3: Installing UbuntuChroot, Xecutah, and XServer===&lt;br /&gt;
* Open up Preware and tap List Of Everything.&lt;br /&gt;
* Search for and install the following: UbuntuChroot, Xecutah, and XServer&lt;br /&gt;
* Now opened Xecutah and tap XServer and a new card will come up.&lt;br /&gt;
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.&lt;br /&gt;
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:&lt;br /&gt;
&lt;br /&gt;
===Step 4: What's Next?===&lt;br /&gt;
* Now to have some fun after all that work you put in!&lt;br /&gt;
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.&lt;br /&gt;
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]&lt;br /&gt;
* Type the below and it will update the program lists.&lt;br /&gt;
&amp;lt;pre&amp;gt;apt-get update&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Now type the following in the box to install what ever you wish! &lt;br /&gt;
&amp;lt;pre&amp;gt;/***type the below for LibreOffice&lt;br /&gt;
apt-get install LibreOffice&lt;br /&gt;
&lt;br /&gt;
/***type the below for the Chromium Browser&lt;br /&gt;
apt-get install chromium-browser&lt;br /&gt;
&lt;br /&gt;
/***type the below for GIMP&lt;br /&gt;
apt-get install gimp&lt;br /&gt;
&lt;br /&gt;
/***type the below for Eclipse&lt;br /&gt;
apt-get install eclipse&lt;br /&gt;
&lt;br /&gt;
/***type the below for LXDE&lt;br /&gt;
apt-get install lxde&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Power User Utilities ====&lt;br /&gt;
As a power user, you may wish to install the following packages.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/***Adds add-apt-repository command, for adding ppas and other alternative package sources.&lt;br /&gt;
apt-get install python-software-properties&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Upgrading Ubuntu ====&lt;br /&gt;
If you'll be relying on binary packages in your Ubuntu chroot, it can be beneficial to upgrade to the latest distribution. This is actually a fairly easy process, and should be familiar to anyone who has upgraded their Ubuntu servers before.&lt;br /&gt;
&lt;br /&gt;
The first step is to install the &amp;quot;update-manager-core&amp;quot; package, which will handle all of the dependencies of upgrading for you.&lt;br /&gt;
&amp;lt;pre&amp;gt;apt-get install update-manager-core&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, simply run the updater.&lt;br /&gt;
&amp;lt;pre&amp;gt;do-release-upgrade -d&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Follow any instructions it gives you along the way.&lt;br /&gt;
&lt;br /&gt;
== How to remove the ext3fs partition ==&lt;br /&gt;
&lt;br /&gt;
*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=UbuntuChroot&amp;diff=21679</id>
		<title>UbuntuChroot</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=UbuntuChroot&amp;diff=21679"/>
		<updated>2012-02-20T21:43:11Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Added information on live distribution upgrades.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists.  '''If you have not already done so you should setup the ext3fs partition to mount at bootup.'''  (Failure to do so will cause you to run out of disk space)  Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.&lt;br /&gt;
&lt;br /&gt;
Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Instructions ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Intro: What you need to know===&lt;br /&gt;
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer. &lt;br /&gt;
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.&lt;br /&gt;
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.&lt;br /&gt;
&lt;br /&gt;
* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do end up messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''&lt;br /&gt;
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''&lt;br /&gt;
**'''You must remove Optware before beginning this process.  Failure to do so will most likely cause you issues!'''&lt;br /&gt;
&lt;br /&gt;
===Step 1: Creating a WebOS Doctor===&lt;br /&gt;
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.&lt;br /&gt;
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)&lt;br /&gt;
**[[Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Step 1: |Application:MetaDoctor - Setting up Meta-Doctor Step 1:]]&lt;br /&gt;
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says &amp;quot;# EXT3FS_PARTITION_SIZE = 2GB&amp;quot;. Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. '''BUT BE AWARE THAT THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU.''' Now save the file still with no file extension. &lt;br /&gt;
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.&lt;br /&gt;
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.&lt;br /&gt;
&lt;br /&gt;
===Alternative Step 1: Re-partitioning by hand===&lt;br /&gt;
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:&lt;br /&gt;
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.&lt;br /&gt;
&lt;br /&gt;
# connect with novaterm (not via quicklaunch as you can't see dialogs)&lt;br /&gt;
First determine how much actual space is being used by /media/internal (not whats allocated to it)&lt;br /&gt;
#&amp;lt;code&amp;gt; df -h | grep internal&amp;lt;/code&amp;gt;&lt;br /&gt;
Remember this as you will need to keep that in mind when you resize&lt;br /&gt;
Disconnect cryptofs:&lt;br /&gt;
# &amp;lt;code&amp;gt;pkill -SIGUSR1 cryptofs&amp;lt;/code&amp;gt;&lt;br /&gt;
Unmount /media/internal: &lt;br /&gt;
# &amp;lt;code&amp;gt;umount /media/internal&amp;lt;/code&amp;gt;&lt;br /&gt;
verify you have a clean filesystem *before* you resize it:&lt;br /&gt;
# &amp;lt;code&amp;gt;/usr/sbin/fsck.vfat /dev/mapper/store-media&amp;lt;/code&amp;gt;&lt;br /&gt;
Then verify how much space /media/internal is using&lt;br /&gt;
#&amp;lt;code&amp;gt; lvscan | grep media&amp;lt;/code&amp;gt;&lt;br /&gt;
For a 16GB TP you should only reduce the size by 4GB and for a 32GB TP you can safely reduce by 8GB&lt;br /&gt;
So this means if the size is 23GB on a 32GB TP your final space that you would resize to is ie: 23GB-8GB=15GB&lt;br /&gt;
# &amp;lt;code&amp;gt;resizefat /dev/mapper/store-media {size you determined it to be}G&amp;lt;/code&amp;gt; - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation will delete your data if you make it too small.&lt;br /&gt;
# &amp;lt;code&amp;gt;lvresize -L 4G /dev/mapper/store-media&amp;lt;/code&amp;gt;&lt;br /&gt;
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises &amp;lt;code&amp;gt;pkill -SIGUSR2 cryptofs&amp;lt;/code&amp;gt; here.&lt;br /&gt;
# &amp;lt;code&amp;gt; lvcreate -l 100%FREE -n ext3fs store &amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mkfs.ext3 /dev/mapper/store-ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -o remount,rw /&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;echo &amp;quot;/dev/mapper/store-ext3fs /media/ext3fs auto noatime 	0	0&amp;quot; &amp;gt;&amp;gt; /etc/fstab&amp;lt;/code&amp;gt;&lt;br /&gt;
# check to make sure nothing already exists under mount point: &amp;lt;code&amp;gt;ls -l /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
## If above shows files/dirs under /media/ext3fs, you will need to copy it and then move it back after mounting:&lt;br /&gt;
## &amp;lt;code&amp;gt;cd /media/ext3fs; tar -cf /tmp/ext3fs-files.tar .&amp;lt;/code&amp;gt;&lt;br /&gt;
## and then &amp;lt;code&amp;gt;rm -rf /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mkdir /media/ext3fs&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -o remount,ro /&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt;mount -a&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;reboot&amp;lt;/code&amp;gt;&lt;br /&gt;
# If files existed under /media/ext3fs before mounting, recreate them with:&lt;br /&gt;
## &amp;lt;code&amp;gt;cd /media/ext3fs ; tar xvf /tmp/ext3fs-files.tar ; rm /tmp/ext3fs-files.tar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.&lt;br /&gt;
&lt;br /&gt;
===Step 2: Mounting the ext3fs partition===&lt;br /&gt;
*Follow the intructions of the Chrooting wiki page.&lt;br /&gt;
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]&lt;br /&gt;
&lt;br /&gt;
===Step 3: Installing UbuntuChroot, Xecutah, and XServer===&lt;br /&gt;
* Open up Preware and tap List Of Everything.&lt;br /&gt;
* Search for and install the following: UbuntuChroot, Xecutah, and XServer&lt;br /&gt;
* Now opened Xecutah and tap XServer and a new card will come up.&lt;br /&gt;
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.&lt;br /&gt;
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:&lt;br /&gt;
&lt;br /&gt;
===Step 4: What's Next?===&lt;br /&gt;
* Now to have some fun after all that work you put in!&lt;br /&gt;
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.&lt;br /&gt;
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]&lt;br /&gt;
* Type the below and it will update the program lists.&lt;br /&gt;
&amp;lt;pre&amp;gt;apt-get update&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Now type the following in the box to install what ever you wish! &lt;br /&gt;
&amp;lt;pre&amp;gt;/***type the below for LibreOffice&lt;br /&gt;
apt-get install LibreOffice&lt;br /&gt;
&lt;br /&gt;
/***type the below for the Chromium Browser&lt;br /&gt;
apt-get install chromium-browser&lt;br /&gt;
&lt;br /&gt;
/***type the below for GIMP&lt;br /&gt;
apt-get install gimp&lt;br /&gt;
&lt;br /&gt;
/***type the below for Eclipse&lt;br /&gt;
apt-get install eclipse&lt;br /&gt;
&lt;br /&gt;
/***type the below for LXDE&lt;br /&gt;
apt-get install lxde&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Upgrading Ubuntu ====&lt;br /&gt;
If you'll be relying on binary packages in your Ubuntu chroot, it can be beneficial to upgrade to the latest distribution. This is actually a fairly easy process, and should be familiar to anyone who has upgraded their Ubuntu servers before.&lt;br /&gt;
&lt;br /&gt;
The first step is to install the &amp;quot;update-manager-core&amp;quot; package, which will handle all of the dependencies of upgrading for you.&lt;br /&gt;
&amp;lt;pre&amp;gt;apt-get install update-manager-core&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, simply run the updater.&lt;br /&gt;
&amp;lt;pre&amp;gt;do-release-upgrade -d&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Follow any instructions it gives you along the way.&lt;br /&gt;
&lt;br /&gt;
== How to remove the ext3fs partition ==&lt;br /&gt;
&lt;br /&gt;
*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Ubuntu_Netbook_Remix&amp;diff=17949</id>
		<title>Ubuntu Netbook Remix</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Ubuntu_Netbook_Remix&amp;diff=17949"/>
		<updated>2011-08-27T05:08:44Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Incorrect version number for Upstart support of chrooting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a placeholder page, which will document the process for installing the Ubuntu Netbook Remix graphical interface on top of the [[UbuntuChroot]]. The eventual goal is to automate this into an installable package as well. For more information or assistance, you can /msg Cerealklr in #webos-internals or reach me by email at cerealklr&amp;lt;ignore.everything.in.the.arrow.brackets.if.you're.human&amp;gt;@gmail.com.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation Process ==&lt;br /&gt;
''Note: This is incomplete and almost entirely untested. Do not attempt this. I can almost guarantee your device will spontaneously combust if you do.''&lt;br /&gt;
&lt;br /&gt;
1. Enter Ubuntu chroot.&lt;br /&gt;
&lt;br /&gt;
2. Run the commands under &amp;quot;Upstart jobs cannot be run in a chroot&amp;quot; at https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes&lt;br /&gt;
&lt;br /&gt;
3. run &amp;quot;sudo apt-get install ubuntu-netbook&amp;quot;&lt;br /&gt;
&lt;br /&gt;
4. Confirm all prompts and accept the defaults for all configuration (unless you know what you are doing).&lt;br /&gt;
&lt;br /&gt;
5. Paste the contents of the latest snapshot from http://git.balabit.hu/?p=gyp/upstart-dummy.git;a=summary into your /sbin folder, inside the chroot. NOTE: failure to do this while within the chroot will probably necessitate a doctoring, at minimum.&lt;br /&gt;
&lt;br /&gt;
6. once this is done, execute the following commands:&lt;br /&gt;
&lt;br /&gt;
- sudo /etc/init.d/rcS start&lt;br /&gt;
&lt;br /&gt;
- sudo /etc/init.d/rc 2 start&lt;br /&gt;
&lt;br /&gt;
7. Unfortunately, the upstart replacement can't handle dbus by default, so you need to create your own script to do so. In order to remedy this, we'll slightly modify the command it normally would have run, without messing with the faux upstart.&lt;br /&gt;
&lt;br /&gt;
- touch start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
- chmod +x start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
- echo &amp;quot;start-stop-daemon --start --pidfile /var/run/upstart-dummy-pids/dbus.pid --exec /bin/dbus-daemon -- --system --fork --activation=upstart&amp;quot; &amp;gt;&amp;gt; start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
8. Execute your new script with &amp;quot;sudo ./start-dbus.sh&amp;quot;&lt;br /&gt;
&lt;br /&gt;
9. You should not be ready to create a new gnome-session manually. To do so, type &amp;quot;sudo gnome-session&amp;quot; The session will start up, reducing the terminal you were typing it to a window. Do NOT close that window, or it will kill the session! I cannot predict what will happen then. Everything ever everywhere might spontaneously corrupt. Just don't do it. In order to exit, you can type ctrl-C in the window first, and then close the card. If you want to go back to using that terminal, it is recommended that you maximize it first, or it will remain wherever the window had been before closing the session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Future Work ==&lt;br /&gt;
As shown here, https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart, Upstart 0.9 and newer support children chroots. If we can ugprade Upstart on WebOS to 0.9.x or later, few to none of the hackarounds will be necessary, and the implementation will likely be less buggy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes&lt;br /&gt;
&lt;br /&gt;
http://gyp.blogs.balabit.com/2011/01/using-upstart-in-a-chroot&lt;br /&gt;
&lt;br /&gt;
http://git.balabit.hu/?p=gyp/upstart-dummy.git;a=summary&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While I've done the work of assembling bits and pieces, this could never have been accomplished without valuable input from, in no particular order, dtzWill, PatrickC, Pdunny, dwc-, and a few other people i'm too tired to think to credit.&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Ubuntu_Netbook_Remix&amp;diff=17947</id>
		<title>Ubuntu Netbook Remix</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Ubuntu_Netbook_Remix&amp;diff=17947"/>
		<updated>2011-08-27T03:47:58Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: Created page with &amp;quot;This is a placeholder page, which will document the process for installing the Ubuntu Netbook Remix graphical interface on top of the UbuntuChroot. The eventual goal is to au...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a placeholder page, which will document the process for installing the Ubuntu Netbook Remix graphical interface on top of the [[UbuntuChroot]]. The eventual goal is to automate this into an installable package as well. For more information or assistance, you can /msg Cerealklr in #webos-internals or reach me by email at cerealklr&amp;lt;ignore.everything.in.the.arrow.brackets.if.you're.human&amp;gt;@gmail.com.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation Process ==&lt;br /&gt;
''Note: This is incomplete and almost entirely untested. Do not attempt this. I can almost guarantee your device will spontaneously combust if you do.''&lt;br /&gt;
&lt;br /&gt;
1. Enter Ubuntu chroot.&lt;br /&gt;
&lt;br /&gt;
2. Run the commands under &amp;quot;Upstart jobs cannot be run in a chroot&amp;quot; at https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes&lt;br /&gt;
&lt;br /&gt;
3. run &amp;quot;sudo apt-get install ubuntu-netbook&amp;quot;&lt;br /&gt;
&lt;br /&gt;
4. Confirm all prompts and accept the defaults for all configuration (unless you know what you are doing).&lt;br /&gt;
&lt;br /&gt;
5. Paste the contents of the latest snapshot from http://git.balabit.hu/?p=gyp/upstart-dummy.git;a=summary into your /sbin folder, inside the chroot. NOTE: failure to do this while within the chroot will probably necessitate a doctoring, at minimum.&lt;br /&gt;
&lt;br /&gt;
6. once this is done, execute the following commands:&lt;br /&gt;
&lt;br /&gt;
- sudo /etc/init.d/rcS start&lt;br /&gt;
&lt;br /&gt;
- sudo /etc/init.d/rc 2 start&lt;br /&gt;
&lt;br /&gt;
7. Unfortunately, the upstart replacement can't handle dbus by default, so you need to create your own script to do so. In order to remedy this, we'll slightly modify the command it normally would have run, without messing with the faux upstart.&lt;br /&gt;
&lt;br /&gt;
- touch start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
- chmod +x start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
- echo &amp;quot;start-stop-daemon --start --pidfile /var/run/upstart-dummy-pids/dbus.pid --exec /bin/dbus-daemon -- --system --fork --activation=upstart&amp;quot; &amp;gt;&amp;gt; start-dbus.sh&lt;br /&gt;
&lt;br /&gt;
8. Execute your new script with &amp;quot;sudo ./start-dbus.sh&amp;quot;&lt;br /&gt;
&lt;br /&gt;
9. You should not be ready to create a new gnome-session manually. To do so, type &amp;quot;sudo gnome-session&amp;quot; The session will start up, reducing the terminal you were typing it to a window. Do NOT close that window, or it will kill the session! I cannot predict what will happen then. Everything ever everywhere might spontaneously corrupt. Just don't do it. In order to exit, you can type ctrl-C in the window first, and then close the card. If you want to go back to using that terminal, it is recommended that you maximize it first, or it will remain wherever the window had been before closing the session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Future Work ==&lt;br /&gt;
As shown here, https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart, Upstart 9 and newer support children chroots. If we can ugprade Upstart on WebOS to 0.9.x or later, few to none of the hackarounds will be necessary, and the implementation will likely be less buggy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes&lt;br /&gt;
&lt;br /&gt;
http://gyp.blogs.balabit.com/2011/01/using-upstart-in-a-chroot&lt;br /&gt;
&lt;br /&gt;
http://git.balabit.hu/?p=gyp/upstart-dummy.git;a=summary&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While I've done the work of assembling bits and pieces, this could never have been accomplished without valuable input from, in no particular order, dtzWill, PatrickC, Pdunny, dwc-, and a few other people i'm too tired to think to credit.&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9376</id>
		<title>Application talk:Qt</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9376"/>
		<updated>2010-03-14T18:23:11Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: /* Porting Qt apps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Has anyone started porting apps over the WebOS yet? &lt;br /&gt;
&lt;br /&gt;
I am going to try and port over VLC [http://qt-apps.org/content/show.php/VLC+media+player?content=93073 QT VLC]. I am not promising anything and if you are interested in helping out please let me know.&lt;br /&gt;
--[[User:Elpollodiablo1|Elpollodiablo1]] 17:22, 14 March 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Porting Qt apps ==&lt;br /&gt;
&lt;br /&gt;
I've been bugging the developer on and off for weeks to get some porting information. He hasn't written anything official yet, but so far it looks like it may be as simple as adding a like of code to specify that the main app should be fullscreen, any child windows should stay on top, and then compiling it in the Palm Pre or Pixi environment (SB2). I've yet to try it though I plan to as soon as he gets us some actual doc info. You're more than welcome to try your hand before that obviously. If it works let me know and i'll start porting too. --[[User:Cerealklr|Cerealklr]] 18:20, 14 March 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
EDIT:&lt;br /&gt;
Just recalled that you'll need to point the app to the QT library. I can't recall where it is stored but a little file browsing and some patience will show you. In the previous revision there used to be an environment var for it, but it's been removed so that the library wouldn't require any preerm or postinst scripts. --[[User:Cerealklr|Cerealklr]] 18:23, 14 March 2010 (UTC)&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9375</id>
		<title>Application talk:Qt</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9375"/>
		<updated>2010-03-14T18:22:54Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: /* Porting Qt apps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Has anyone started porting apps over the WebOS yet? &lt;br /&gt;
&lt;br /&gt;
I am going to try and port over VLC [http://qt-apps.org/content/show.php/VLC+media+player?content=93073 QT VLC]. I am not promising anything and if you are interested in helping out please let me know.&lt;br /&gt;
--[[User:Elpollodiablo1|Elpollodiablo1]] 17:22, 14 March 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Porting Qt apps ==&lt;br /&gt;
&lt;br /&gt;
I've been bugging the developer on and off for weeks to get some porting information. He hasn't written anything official yet, but so far it looks like it may be as simple as adding a like of code to specify that the main app should be fullscreen, any child windows should stay on top, and then compiling it in the Palm Pre or Pixi environment (SB2). I've yet to try it though I plan to as soon as he gets us some actual doc info. You're more than welcome to try your hand before that obviously. If it works let me know and i'll start porting too. --[[User:Cerealklr|Cerealklr]] 18:20, 14 March 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
EDIT:&lt;br /&gt;
Just recalled that you'll need to point the app to the QT library. I can't recall where it is stored but a little file browsing and some patience will show you. In the previous revision there used to be an environment var for it, but it's been removed so that the library wouldn't require any preerm or postinst scripts.&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
	<entry>
		<id>http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9374</id>
		<title>Application talk:Qt</title>
		<link rel="alternate" type="text/html" href="http://wiki.webos-internals.org/index.php?title=Application_talk:Qt&amp;diff=9374"/>
		<updated>2010-03-14T18:20:54Z</updated>

		<summary type="html">&lt;p&gt;Cerealklr: New section: Porting Qt apps&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Has anyone started porting apps over the WebOS yet? &lt;br /&gt;
&lt;br /&gt;
I am going to try and port over VLC [http://qt-apps.org/content/show.php/VLC+media+player?content=93073 QT VLC]. I am not promising anything and if you are interested in helping out please let me know.&lt;br /&gt;
--[[User:Elpollodiablo1|Elpollodiablo1]] 17:22, 14 March 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Porting Qt apps ==&lt;br /&gt;
&lt;br /&gt;
I've been bugging the developer on and off for weeks to get some porting information. He hasn't written anything official yet, but so far it looks like it may be as simple as adding a like of code to specify that the main app should be fullscreen, any child windows should stay on top, and then compiling it in the Palm Pre or Pixi environment (SB2). I've yet to try it though I plan to as soon as he gets us some actual doc info. You're more than welcome to try your hand before that obviously. If it works let me know and i'll start porting too. --[[User:Cerealklr|Cerealklr]] 18:20, 14 March 2010 (UTC)&lt;/div&gt;</summary>
		<author><name>Cerealklr</name></author>
	</entry>
</feed>