08-06-2014, 01:58 PM
Hi gold_finger,
This is to confirm that I tried your advice of 4th April in this thread on how to create & use a separate data partition for my dual boot set up (LL 1.0.8 with zorin 9) , and it worked! I used the symlink method for uniting both distros at a common data partition. As a linux newbie that felt a real achievement, especially as I had to modify one of your lines of code!
In LL 1.0.8, the Terminal rejected the term 'Documents' in the following line:
ln -s /mnt/DATA/Documents /home/yourusername (I didn't understand why you choose 'Documents' here especially as you had created several home folders in a previous line, i.e.
mkdir Documents Downloads Music Pictures Videos
So I changed it to..
ln -s /mnt/DATA /home/yourusername (this worked)
I notice that when I boot up in either distro of the dual-boot, I have to go to the DATA link in /home and open it with administrator's password in order to access it, that is access is not automatic. Otherwise it works really well.
Many thanks for this, gold_finger!
Kind regards
Mike
This is to confirm that I tried your advice of 4th April in this thread on how to create & use a separate data partition for my dual boot set up (LL 1.0.8 with zorin 9) , and it worked! I used the symlink method for uniting both distros at a common data partition. As a linux newbie that felt a real achievement, especially as I had to modify one of your lines of code!
In LL 1.0.8, the Terminal rejected the term 'Documents' in the following line:
ln -s /mnt/DATA/Documents /home/yourusername (I didn't understand why you choose 'Documents' here especially as you had created several home folders in a previous line, i.e.
mkdir Documents Downloads Music Pictures Videos
So I changed it to..
ln -s /mnt/DATA /home/yourusername (this worked)
I notice that when I boot up in either distro of the dual-boot, I have to go to the DATA link in /home and open it with administrator's password in order to access it, that is access is not automatic. Otherwise it works really well.
Many thanks for this, gold_finger!
Kind regards
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work