Date: Wed, 30 Mar 2005 03:55:07 +0200 From: Danny Pansters <danny@ricin.com> To: freebsd-questions@freebsd.org Subject: Windows question :) SFU, nfsclient Message-ID: <200503300355.07829.danny@ricin.com>
next in thread | raw e-mail | index | archive | help
My partner uses a winxp box on my local net (behind a FreeBSD box who acts as gateway/firewall in front of out gbit switch). Now, we were wanting to upgrade the gateway box with two gigabit NICs and we did but the hard disk died (oh well it was 6 years old as is the box and mobo). I made a new system on another disk and set up pf and so on and everything works swell. In the old situation I had an NFS share for my desktop and other *NIX boxes and a samba share (server on the gateway, not on th windows box) as well. Having to reconfigure anyway, I decided to see if I could have the windows box be an nfs client. With the Services For Unix it does just that. So I installed it and mounted the gateway:/pub NFS share. Currently (it's -maproot) I can write to it from my desktop box as root or as my UID if I make a directory owned by my UID. I could do the same for the win box user using a passwordless and shell-less account on the gateway box for it. Everything works great so far, except that on startup of winxp there's a warning dialog that tells us to either have passwd and group files installed or use nis. I don't want either, but for the forner I guess I could use emtp or bogus (but correctly formatted files). But where would I put those and how are they supposed to be named? (I reckon passd m,eans our master.passwd syntax, not shadow) There must be some win2k/2k3/xp buff who knows this. Anthony? As an aside: seems like MS killed or is killing quite a few middleware companies with their SFU (from interix, isn't that ultimately SCO? ;-) Thanks, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503300355.07829.danny>