I would also manually check /home to see if the files you places on the overlay are there as well - as that'll be a sign of whether it's behaved itself or not.
I'll try find some time to rework my guide to include mounting a home overlay tonight, if I get in early enough.
Actually, have some time to do it just now....
In the case of the mount info, you're looking for a line reading "aufs on /home type aufs ....."
Anyway, from the beginning!
Download Extend Utils and stick it somewhere in your pandora directory structure: http://stuckiegamez....ExtendUtils.pnd
Select "New Extend/Overlay/Swap"
Select "New Overlay"
Select a size ( for my purposes, I'm just testing so 256mb ) .. if you select custom, prepare for a long wait.
Place the file on your SD card and give it a name, we shall call it "homeMount"... you don't need to add .overlay or .extend, as it does it for you.
It'll now either extract a premade empty file, or it'll DD a new file, taking forever, and probably raping your SD in the process.. you have been warned
You'll be pushed back to the main menu now.
Select "New Pre-Mount"
Select "New Overlay Mount Script"
Select "Standard Home Overlay"
Choose your file that you saved on card in the previous stage.
Save the mount script anywhere you like, calling it anything you like.. for our purposes, on the SD card named "homeMount"
Back to the main menu.
Select "Mount Existing Pre-Mount"
Gotcha: As we've saved the script to a FAT32 filesystem, we can't actually run it directly from the Terminal. Normally, you can. You'll need to run it through Extend Utils or do /bin/bash /my/mount/script.preMount instead.
Choose the script you saved in the previous part.
Type your sudo password.
That should be it.
For checking purposes:
Launch a Terminal.
Look for a line at the bottom reading something like "aufs on /home type aufs (rw, si=67199377)" The number may be different... I didn't look much into it.
Type cd /tmp/NAMEOFOVERLAY.overlay for our example; cd /tmp/homeMount.overlay
We'll put a random file here to ensure it works touch MyTestFile
ls should show it up, as should ls ~
Now, Launch Debian Dev Extend.
Ok past the notifictions.
Select your Extend file.
Type your sudo password if prompted ( you may be quick enough to still be in the sudo cache that it doesn't ask )
In the Debian Dev Extend terminal, type gcc to ensure that works.
Type cd to jump directly to your home folder, and ensure our test file is there ls which if it is, you're good to go.
And now I gotta run!
If there's any issues, just post and I'll try and help
I can't remember why I split the thing between extend and overlay... that's confusing.. I'll get rid of that next release. I think it was because of OS Extends and having compressed versions of them, but that was a bit advanced and I don't think anyone uses them.
If you do, shout out! or I'll be removing them! Extends ARE Overlays, just that my menu system allows you to generate compressed Extends but not compressed Overlays. If you use Compressed Extends for whatever reason, let me know See, your head's probably exploded already with me mention Extend and Overlays so often they're the same thing.
Edited by Stuckie, 28 June 2011 - 08:30 AM.