From owner-freebsd-questions@FreeBSD.ORG Thu May 6 21:34:18 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7256106568E for ; Thu, 6 May 2010 21:34:18 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 798908FC25 for ; Thu, 6 May 2010 21:34:18 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o46LYBjv065473 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 6 May 2010 16:34:11 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4BE335D6.3030500@tundraware.com> Date: Thu, 06 May 2010 16:34:14 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Mailing List References: <4BE32DE4.20206@tundraware.com> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (ozzie.tundraware.com [75.145.138.73]); Thu, 06 May 2010 16:34:11 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o46LYBjv065473 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Accessing file from windows or to windows X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 21:34:18 -0000 On 5/6/2010 4:30 PM, Modulok wrote: > In order to 'provide' shares to a windows network you would need to > run a daemon on FreeBSD which provides such services. The most popular > solution is 'samba'. I think the package is called 'samba3'. You > install it, edit its config file, which specifies what to share and > how to share it. You then run the daemon and poof, your windows > machines can access the shares you've configured. > This is entirely correct, however, judging from the OP's question, this sounds like real overkill. mount_smbfs is in the base FBSD system and does not require a port install to use. Just my .00001 cents worth. > On the other hand, if the windows machines are providing a shared > folder you want to access, you can just mount that share via the > 'mount_smbfs' command. For example, if I had a windows computer named > 'apollo' with username 'guest' and a folder named 'shared' I wanted to > access, I could do this from my FreeBSD machine: > > # As root: > mount_smbfs //guest@apollo/shared /mnt > > I would now have the contents of apollo's 'shared' folder available in > my '/mnt' directory. See 'mount_smbfs(8)' for more. > > Other options could involve setting up an SSH client/server on the two > machines and use 'sftp' or 'scp' to transfer files, among others. > -Modulok- > ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/