Video: Everything you need to know about Linux in Windows Get ready to sudo apt-get Ubuntu, openSUSE, and Fedora from inside Windows. Nick Heath explains how and why tech professionals will use Linux commands in this fall's Windows 10 Creators Update.When Windows 10 was released, it seemingly broke the ability to easily connect to Linux Samba shares. Considering how many businesses rely on Samba for the sharing of folders, this was a bad move on the part of Microsoft. Fortunately, the ability to connect to Samba shares wasn't actually removed from the Windows platform, it was merely tucked a bit out of sight.I want to walk you through the process of making that connection between Windows 10 and your Linux shares.I will assume you have both Windows 10 installed on a machine (or multiple machines) and a Samba share at the ready from your data center.
I am using the prebuild 10166 on my home network computers. My wife's laptop and my desktop. I finally got them to connect via smb, however, I have to type the name in.
With that said, let's connect. Connecting to your serverOpen up File Explorer and then right-click on This PC (in the left pane). From the resulting context menu, select Add a network location ( Figure A).
Win 10 Pro now has NFS Client Services:There is a good tutorial here:(to get rid of '-2 mapping id's):after addingAnonymousUidAnonymousGidas per above links instructions, I left their 'Data' value default, '0x0000.' And after rebooting my Win10 Pro Client, I used the 'mount -o anon.' Cmd, as per above link.It should grab the uid/gid of your NFS server shares automatically for r/w ability.In your Win10 pro (Clients) File Manager, right-click on the 'Drive:' nfs mounted share,select 'Properties', and look in 'NFS Attributes' which will show you the permissions, uid, gid.Also, there is more details here:(NFS Client services have been added to Win10 Pro, so the above should apply now as well).NFS is king,and I can't stand all that other bloated mess of Samba/CIFS/AFP/.
Hey I'm sorry haven't been on this BBS in a while. I'm also not using that setup any more, things constantly evolving in my homelab. The short answer is I don't really know or have a similar working environment I can test for you ATM, but I'll try and help the best I can.I didn't use nolock, but I did mount as anon (uid/gid 0) which is root user. I may have also used norootsquash on the NFS server (/etc/export flag)Here's how I set up Windows for root NFS mount:If you're concerned about security and you're using the share with other people (like in a work environment) this might not be a good idea.re: Nolock, though, I don't think there's any problem mounting the share using the nolock flag. Just be careful not to edit the same file from two different places at the same time.Obviously nolock is going to be a bad idea if you're using the share at work, too.
Hope that helps!