[EMAIL PROTECTED] writes: > Jeff, I'm not sure I understand it completely, but I thought Karl's use of > Samba was for communications with VMware not access to Windows > filesystems in general. > When I've used Samba to, for example, serve files from a Windows > diskette across that network from a Linux server to a Windows client, > I've mounted the Windows f/s as "vfat". So I think that implies that > Samba is using the vfat file system code to > access the Windows media under Linux. Thus it seems to me that > a Windows partition on > your local hard drive could be mounted "vfat" and accessed the same as it > would be > remotely using Samba. <snip> Samba doesn't use vfat file system code. It uses the SMB protocol, just as you would use the NFS protocol to mount another file system. Mounting it as vfat may let Linux know not to try things that vfat doesn't understand. The main difference between the Samba solution, and just mounting the file sytem, is that windows under vmware, doesn't know anybody else is accessing the file system, and corruption can happen easily. The windows SMB driver coordinates with windows. > That Samba trick looks like a nice one. Thanks, Karl! > --Bruce > This was also mentioned in the panel last nite in Concord. Bob Sparks Linux guru wannabe ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
