On 2013/11/19 1:51 AM, Mick wrote:
On Monday 18 Nov 2013 05:29:04 Mark Filipak wrote:
My setup is a virtual machine environment.
Host OS: Windows-7, 64bit, without an Internet connection.
Guest OS: Linux Mint 14, with an Internet connection.
Shared folder #1: The download directory (Net > Guest > Host).
Shared folder #2: The maildir directories.
Problem: Maildir filenames use characters that are illegal in Windows.
Solution: Samba? How? I'm ignorant of Samba.
There isn't much to it and the Samba documentation is excellent. Just to try
things out quickly you can enable guest users.
Problem: Windows permissions can create problems for Linux.
Solution: Make the shared folders a separate, ext3 partition - I think that
Samba comes into play here also.
I don't know what permissions problems you are talking about...
Windows kept saying "Hey! That came from an alien system. I'm not going to let
you install it." It would lock stuff and laugh at me.
...but you have three main options that I can think of:
1. A Linux fs, which MSWindows can read. There are MSWindows drivers for
ext2, but I don't know if they work for 64bit systems, how ACLs translate
across OS' etc.;
2. A Linux only fs that MSWindows cannot read, e.g. ext4 and use something
like SAMBA to serve the files across the OS boundary.
3. A MSWindows fs like NTFS and use ntfs-3g to mount it from Linux. The same
would apply with VFAT, although NTFS is more robust.
However, although 1 and 3 above will work nicely when dual booting, with
concurrent access to the same fs from two different OS' you are asking for
trouble. File locks may be violated if you try to write to the same file and
data become corrupted.
That will never happen. Windows will never write to either the shared download
directory or the shared maildir. Why? Because the Windows Host has no Internet.
No Internet, no download. No Internet, no email. Get it? Download and Email
only from Linux, but accessible to Windows - just not writable in Windows.
You may be able to set up special file or directory
locking through some shell script in Linux, or EMCO MoveOnBoot on MSWindows,
but I would leave this as an exercise for a rainy day.
Not needed.
This leaves option 2, SAMBA as a plausible solution - application rather than
fs level access from MSWindows. However, I have never used SAMBA in this
operating context...
Errmmm... I thought that Samba WAS the file system interface to Windows. Isn't
Samba an SMB compatible interface for Linux filesystems? You know: Looks like a
Linux user to the Linux filesystem, looks like an SMB server to the Windows OS.
...and don't know what would happen if both OS tried to write
to a file concurrently
Again, that will never happen. Don't worry about it. To Windows, the shared
stuff might as well be read-only.
- Linux at fs level and MSWindows at an application
level. I would think that application level locks would manage access to it.
Better try it out first before you trust your data to it.
