Dual Booting LL 2.0 with other Ubuntu (14.04) based distros

[gold_finger]

What should I see when I reboot & open the  '/home'  folder? I don't see the DATA folder , when I open the File Manager.

The 13 folders in the above .conf file have been created in the subfolder 'DATA' within the folder 'mnt', as I saw them under file system  (there is also an additional one called lost+found there).

You won't see the DATA folder in /home/m-ll2.  You bound the 13 sub-folders of DATA to your home, but you didn't bind the DATA folder itself to home.

The "lost+found" is normal.  It will be automatically generated to allow you to use the Trash function on the partition.


Your "bind-home.conf" file looks good except for a few lines.  The lines I have in red below are most likely not currently working properly:

mount --bind /mnt/DATA/Documents /home/m-ll2/Documents
mount --bind /mnt/DATA/Downloads /home/m-ll2/Downloads
mount --bind /mnt/DATA/Linux ISOs /home/m-ll2/Linux ISOs
mount --bind /mnt/DATA/Music /home/m-ll2/Music
mount --bind /mnt/DATA/Photos family /home/m-ll2/Photos family
mount --bind /mnt/DATA/Photos general /home/m-ll2/Photos general
mount --bind /mnt/DATA/Pictures /home/m-ll2/Pictures
mount --bind /mnt/DATA/Public /home/m-ll2/Public
mount --bind /mnt/DATA/Templates /home/m-ll2/Templates
mount --bind /mnt/DATA/TV /home/m-ll2/TV
mount --bind /mnt/DATA/Videos /home/m-ll2/Videos
mount --bind /mnt/DATA/VirtualBox VMs /home/m-ll2/VirtualBox VMs
mount --bind /mnt/DATA/Wallpapers /home/m-ll2/Wallpapers

Having spaces in the names of your files and/or folders can cause problems when you try to run commands like those in the bind-home.conf file.  For example, when the system tries to run the command mount --bind /mnt/DATA/Linux ISOs /home/m-ll2/Linux ISOs, it will interpret that as you trying to bind /mnt/DATA/Linux to a place called ISOs because of the space that it encounters between the two words.

You have a choice to make.  Either rename those folders in both /mnt/DATA and /home/m-ll2 and change their respective lines in bind-home.conf file; or either "escape" the spaces or quote the folder names with spaces in them in your bind-home.conf file.

Eg. To change the names, simply use a ".", "-", or "_" in place of the spaces.  Change Linux ISOs to Linux_ISOs, for example.

Eg.  If you keep the spaces in the names, you need to remember to either escape the spaces by putting a backslash character before each space in the name, or put the entire name within quote marks when running commands on those files.  Example of escaping same file as above would be Linux\ ISOs.  Or quote the whole thing, "Linux ISOs"

Personally, I find it much easier to not have names with spaces and just use ".", "-", or "_" in place of a space.  That way I don't have to remember to escape or quote things.

NOTE:  If you change the name of "VirtualBox VMs" folder to "VirtualBox_VMs", you will need to follow my instructions here to tell the VirtualBox program its new default machine folder.  Otherwise it will keep looking for things in "VirtualBox VMs", which will no longer exist.

After I've created the upstart job, should I be doing anything else, e.g. with the terminal?

No need to do any more with terminal.  The bind-home.conf file should be saved (as root) to the /etc/init directory.  To check ownership of the file, open a terminal and enter:

Code:

ls -l /etc/init

You'll get a long output of lines.  Scroll back to beginning of the output to find the line for bind-home.conf and make sure it shows that it is owned by root (you'll see "root  root" on the line).  Output should look similar to mine shown here:

I have just rebooted after saving & closing the above file. I get this message in the terminal whenever I open, save and close the above file....(gedit:2270): IBUS-WARNING **: The owner of /home/m-ll2/.config/ibus/bus is not root! ...maybe there is a problem here.

I'm not sure what that error message is.  I'm assuming you installed gedit and are using that instead of leafpad.  Exactly how did you try opening the bind-home.conf file?  Through the file manager, or with a terminal command?

If you used a terminal command, did you use sudo gedit /etc/init/bind-home.conf or gksu gedit /etc/init/bind-home.conf?  When you open GUI programs (like the text editor) as root, you should use gksu instead of sudo.  Maybe that is what caused the error message.