I made a surprise observation today...
I found out that I could both read & write data files on an MSDOS-ext4 formatted data partition on my PC, using a Win7 VM, mounted as guest in an LL3.2 host. "Surprised", because I didn't think ext4 was normally accessible from Windows OS, unless special software was employed.
Is the above only seen when Windows OS is installed as a VM?
It means I'll have to adjust the shared folder settings in Oracle VM VirtualBox Manager to 'read only', to avoid any potential security issues, e.g. the possibility that Microsoft updates might over-write parts of the PC's data files or OS files.
Recently, I had to abandon a Win7 / LL3.2 legacy dual-boot, because following a recent patching of Win7 with Microsoft security updates, the PC failed to boot. It even failed to detect the SSD drives on setup1 - they weren't even listed in the boot device list.
As a consequence of this, I've now returned to a Linux-only setup (setup1 in sig): LL3.2 as the main workhorse OS, dual-booted with Linux Mint 18 (XFCE) as a back-up, in case anything happened to LL.
And of course Win7 (& any Windows OS in general) is now relegated to VM status, following the unfortunate experience that I've just described above...
Cheers
Mike
I found out that I could both read & write data files on an MSDOS-ext4 formatted data partition on my PC, using a Win7 VM, mounted as guest in an LL3.2 host. "Surprised", because I didn't think ext4 was normally accessible from Windows OS, unless special software was employed.
Is the above only seen when Windows OS is installed as a VM?
It means I'll have to adjust the shared folder settings in Oracle VM VirtualBox Manager to 'read only', to avoid any potential security issues, e.g. the possibility that Microsoft updates might over-write parts of the PC's data files or OS files.
Recently, I had to abandon a Win7 / LL3.2 legacy dual-boot, because following a recent patching of Win7 with Microsoft security updates, the PC failed to boot. It even failed to detect the SSD drives on setup1 - they weren't even listed in the boot device list.
As a consequence of this, I've now returned to a Linux-only setup (setup1 in sig): LL3.2 as the main workhorse OS, dual-booted with Linux Mint 18 (XFCE) as a back-up, in case anything happened to LL.
And of course Win7 (& any Windows OS in general) is now relegated to VM status, following the unfortunate experience that I've just described above...
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) ~ [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