@torreydale & @wirezfreeze...
Many thanks to you both - I have now got host LL & guest LL 'talking' to each other through /media/sf_ [name of directory].
One difficulty was that Host already had its directories (Documents, Downloads, Music etc...) symlinked to a separate data partition (shared with Win8.1).
When I tried to link them all collectively with Guest under Shared Folders in the Virtual Box Manager as /home/mike, they would appear with double crosses when I opened File System (under File Manager) on Guest.
However I got round this problem by linking the directories individually under Shared Folders in Virtual Box Manager, i.e. as /home/mike/Documents; /home/mike/Downloads; home/mike/Music; etc... It works just fine now so I will mark this thread as SOLVED.
However, is there a way of making /media/sf_ [name of directory] more accessible in Guest, rather than having to go through the File Manager each time? Maybe I could mount them collectively in a folder on the Desktop - how do I do that?
Many thanks again for your help guys.
Cheers
Mike
Many thanks to you both - I have now got host LL & guest LL 'talking' to each other through /media/sf_ [name of directory].
One difficulty was that Host already had its directories (Documents, Downloads, Music etc...) symlinked to a separate data partition (shared with Win8.1).
When I tried to link them all collectively with Guest under Shared Folders in the Virtual Box Manager as /home/mike, they would appear with double crosses when I opened File System (under File Manager) on Guest.
However I got round this problem by linking the directories individually under Shared Folders in Virtual Box Manager, i.e. as /home/mike/Documents; /home/mike/Downloads; home/mike/Music; etc... It works just fine now so I will mark this thread as SOLVED.
However, is there a way of making /media/sf_ [name of directory] more accessible in Guest, rather than having to go through the File Manager each time? Maybe I could mount them collectively in a folder on the Desktop - how do I do that?
Many thanks again for your help guys.
Cheers
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) ~ Arm710@1.2GHz - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ i3-3110M@2.4GHz - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom N455@1.66GHz - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel T3200@2.0GHz - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel T7100@1.8GHz - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ Arm710@1.2GHz - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ i3-3110M@2.4GHz - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom N455@1.66GHz - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel T3200@2.0GHz - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel T7100@1.8GHz - LL4.6, works well with kernel 4.4; 4.15 doesn't work