
Originally Posted by
Ardvaark
I followed ncinerates guide on page 17 of this thread to install ubuntu. I did everything correct and it all went well and installed everything up until I got to >apt-get install ldxe, it said package not found.
Most likely it should have been:
apt-get install lxde

Originally Posted by
Ardvaark
I'm not concerned right now with continuing from this point right now. I have deleted the ubuntu chroot package using the rm command and would like to remove the ext3fs partition I made in this process to get my 2gb memory back. How do I do this?
Thank you, I'll probably in the near future go for the full ubuntu install but for now I just want to undo what I've done so far.
Ardvaark
It is probably a good idea to remove the ubuntu chroot package, rather than just using the rm command... regarding the ext3fs removal, I've posted some instructions in another thread. The procedure is the reverse of the one for creating the extra ext3fs logical volume - the one you can find here:
UbuntuChroot - WebOS Internals
First, I assume you really do have a ext3 partition and not a loopback file. You should be able to see the logical volume with lvscan. This is for a 32GB touchpad.
# lvscan
ACTIVE '/dev/store/root' [568.00 MB] inherit
ACTIVE '/dev/store/var' [64.00 MB] inherit
ACTIVE '/dev/store/update' [16.00 MB] inherit
ACTIVE '/dev/store/log' [24.00 MB] inherit
ACTIVE '/dev/store/mojodb' [256.00 MB] inherit
ACTIVE '/dev/store/filecache' [136.00 MB] inherit
ACTIVE '/dev/store/media' [18.00 GB] inherit
ACTIVE '/dev/store/swap' [400.00 MB] inherit
ACTIVE '/dev/store/ext3fs' [9.64 GB] inherit
Now assuming you have removed (and made a backup if needed) ubuntu and anything else that might use /media/ext3fs - for example optware can use the ext3fs too - now we can continue.
Close any apps running on the touchpad. Connect with Novaterm - the following should all be done via novaterm. First unmount and remove the ext3fs logical volume.
Code:
umount /dev/mapper/store-ext3fs
lvremove /dev/mapper/store-ext3fs
Now remove the line in /etc/fstab that mounts /dev/mapper/store-ext3fs at boot time. There might be a line in /etc/fstab that looks a bit like this:
Code:
/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0
If you have that line you need to remount root in read-write mode before you can edit /etc/fstab.
Code:
mount -o remount,rw /
Then remove that line from /etc/fstab and save the file (note: making backups of files before you change them is a good idea).
Now make root fs read-only again.
Code:
mount -o remount,ro /
So now we have no ext3fs logical volume and some empty space. Now umount these filesystems before resizing (I'm not sure if the pkill is needed, but I don't think it does any harm).
Code:
pkill -SIGUSR1 cryptofs
umount /media/cryptofs
umount /media/internal
Check the umount was successful (should return nothing because these filesystems should no longer be mounted).
Code:
mount | grep cryptofs
mount | grep internal
Then when these have been unmounted, extend the size of your logical volume. We have to increase the size of the logical volume before we increase the size of the filesystem. First check the file system is clean.
Code:
/usr/sbin/****.vfat /dev/mapper/store-media
Opps... the forum thinks I'm trying to post a bad word. 
Please go here for the correct command (instead of ****) to check you have a clean filesystem:
UbuntuChroot - WebOS Internals
So now we have a clean file system, we can resize it. The following should make it take all the remaining free space in the volume group.
Code:
lvresize -l +100%FREE /dev/mapper/store-media
Please check with 'lvscan' and/or 'lvdisplay' as above.
Now we can resize the fat32 file system on that logical volume.
Code:
resizefat /dev/mapper/store-media 26G
The example above is for making it 26GB, but the size you need might be different… please check these links for more info.
http://forums.precentral.net/hp-touc...u-install.html
gadgetXplorer: #webOS: How to remove EXT3FS partition
Now you should be able to remount your fat32 fs.
Check with df command and it should be the same size as original before you created the ext3fs volume. Reboot and make sure everything is working as it should.