Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 May 2010 15:36:53 -0600
From:      Modulok <modulok@gmail.com>
To:        Tim Daneliuk <tundra@tundraware.com>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: Accessing file from windows or to windows
Message-ID:  <m2n64c038661005061436l2b16b51aq4b6869fcc66dbbe1@mail.gmail.com>
In-Reply-To: <j2o64c038661005061430v68eb6394v5b4c5d5f9d37df24@mail.gmail.com>
References:  <AB2BC18AD166C948A0BC559E22CE9C9105DEC2CF@FCIEXCHANGE1.FCI> <4BE32DE4.20206@tundraware.com> <j2o64c038661005061430v68eb6394v5b4c5d5f9d37df24@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> "writing to an NTFS partition may corrupt the partition" - I'm guessing this is not the case anymore.

That's only when you have directly mounted an NTFS on the local
machine. Like if you jacked a hard drive out of a windows machine and
plugged it into your BSD machine. If you're accessing it across a
network you're never directly accessing the file system. There is
always an intermediary between you and it; the daemon which handles
file i/o requests. Notice: It handles your *requests*; you never
actually access the underlying file system.

On 5/6/10, Modulok <modulok@gmail.com> 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.
>
> 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-
>
> On 5/6/10, Tim Daneliuk <tundra@tundraware.com> wrote:
>> On 5/6/2010 3:47 PM, Jean-Paul Natola wrote:
>>>
>>> Hi all,
>>>
>>> I have a file I need in my bsd box, would it be easier, or is it
>>> possible,
>>> to mount an NTFS share , or should I try to "map" a directory from the
>>> windows box.
>>>
>>>
>>> TIA,
>>>
>>> I have
>>>
>>> Xp
>>> Win7
>>> Win2003
>>> Win2008
>>> Freebsd 6.4
>>>
>>> thanx
>>
>>
>> Same machine or two separate machines?
>>
>> Two separate machines is trivial - share
>> a directory on the Win machine and use smbfs
>> on FBSD to get to it.
>>
>> For same machine, boot FBSD, and do a mount
>> with -t ntfs as an arg .... well, I don't recall
>> if 6.4 supported this or not, now that I think about it.
>>
>>
>> One-time or frequent transfer?
>>
>> There are tons of other options, especially if you're running
>> separate machines.  Not all of these are elegant, but they
>> all will work and have their place for infrequent transfers:
>>
>> - Email the file to yourself from one OS and retrieve it
>>   from the other.
>>
>> - Copy the file to a thumbdrive
>>
>> - Copy the file to a private website which can then
>>   be subsequently retrieved by another machine/OS
>>   image.
>>
>>
>>
>>
>>
>> ----------------------------------------------------------------------------
>> Tim Daneliuk     tundra@tundraware.com
>> PGP Key:         http://www.tundraware.com/PGP/
>>
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"
>>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2n64c038661005061436l2b16b51aq4b6869fcc66dbbe1>