08-19-2014, 06:06 AM
Gold_finger, the good news is that sda & sdb are now working cooperatively, with the OS files spread out between the two physical drives. With your help, I appear to have solved the problem I mentioned about failure to boot-up, following the LL's OS files being shared between the two hard drives.
The problem I had appears to be due to be me incorrectly using 'Y' in response to being asked to upgrade to the maintainer's newer version, instead of using the correct default option of 'N'. It now explains a lot of the instability I have experienced generally, since I came over to linux in April 2014.
I recommend that, within the installation guide, or even as a banner on LL's website home page, the use of default option of 'N' should be very clearly highlighted. I wonder how many newbies to linux have been tripped up with this inadvertent error? In the link you sent me about this issue, I thought very much the same way as the person in that forum posting who had this very same problem - I assumed (wrongly) that the maintainer's version was Valtam's Linux Lite - the idea of a throwback to Ubuntu never occurred to me.
I have a question on the size for separate /home/username partitions for LL & the other distro in a dual-boot set-up. Since all my usual folders will be in the separate DATA partition, I will, as you pointed out, only need small /home/username partitions. I noticed the files in the separate home appeared to take up around 60-70 MB, following a fresh install, so I set the size for each of the separate home partitions at 250 MB. This appeared too small, as subsequently some items were missing on panel bar following boot-up. Another time I used 1.8 GB, and this seemed to be okay. Maybe I should go for 5GB for as a safe bet, as I assumeg the amount of space taken up by config files in /home will increase over time. I have 1TB for sdb, so space is not an issue here. What do you think?
Also when I create the separate home partitions, should they be named /home/username or /home/username/ (slash also after 'username')
I know you don't use separate /home partitions, but I have found that the response of LL appears to be noticeably crisper/snappier with them, so would quite like to continue with this as long as it continues to work (!).
The problem I had appears to be due to be me incorrectly using 'Y' in response to being asked to upgrade to the maintainer's newer version, instead of using the correct default option of 'N'. It now explains a lot of the instability I have experienced generally, since I came over to linux in April 2014.
I recommend that, within the installation guide, or even as a banner on LL's website home page, the use of default option of 'N' should be very clearly highlighted. I wonder how many newbies to linux have been tripped up with this inadvertent error? In the link you sent me about this issue, I thought very much the same way as the person in that forum posting who had this very same problem - I assumed (wrongly) that the maintainer's version was Valtam's Linux Lite - the idea of a throwback to Ubuntu never occurred to me.
I have a question on the size for separate /home/username partitions for LL & the other distro in a dual-boot set-up. Since all my usual folders will be in the separate DATA partition, I will, as you pointed out, only need small /home/username partitions. I noticed the files in the separate home appeared to take up around 60-70 MB, following a fresh install, so I set the size for each of the separate home partitions at 250 MB. This appeared too small, as subsequently some items were missing on panel bar following boot-up. Another time I used 1.8 GB, and this seemed to be okay. Maybe I should go for 5GB for as a safe bet, as I assumeg the amount of space taken up by config files in /home will increase over time. I have 1TB for sdb, so space is not an issue here. What do you think?
Also when I create the separate home partitions, should they be named /home/username or /home/username/ (slash also after 'username')
I know you don't use separate /home partitions, but I have found that the response of LL appears to be noticeably crisper/snappier with them, so would quite like to continue with this as long as it continues to work (!).
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