Nick Rout wrote:
I have never actually served up windows partition mounted in linux over
samba - at least i don't recall doing it. There seems to ba a LOT of
layers of permissions and ownerships to check.
I have a linux machine that can share a win2k NTFS partition using samba:
The machine that can dual-boot to Win2k or mandrake. The win2k partition
is a read-only NTFS partition (see (1)). Samba is installed on this
machine. See (2) for the config file; it is much shorter than yours. My
home directory (/home/ironss) is shared and has a slink to /mnt/win2k:
/home/ironss/win2k -> /mnt/win2k
From a different windows machine, I can connect to
\\ws1709\ironss\win2k. So, from Win2K CMD prompt, I can do
C:> dir \\ws1709\ironss\win2k
and get a directory listing.
I used to have a slink
/home/ironss/root -> /
but that seemed a little insecure... There might still be any number of
gaping security holes in the system.
I have absolutely no idea what the entries in samba.conf actually do;
our resident linux guru created a template file for our group at work,
and I just modified the appropriate bits. I hope he did his homework.
I seem to remember having to set up a password somewhere, although I
cannot remember whether it was on the linux machine or the windows
client or both.
In short, samba can serve an NTFS partition, but I have the partition
mounted read-only so I cannot write to it.
Stephen
(1) /etc/fstab has the following entry
/dev/hda1 /mnt/win2k ntfs users,iocharset=iso8859-1,ro,umask=0 0 0
(2) /etc/samba/samba.conf
[global]
workgroup = TEL
netbios name = WS1709
server string = Samba Server %v
encrypt passwords = Yes
map to guest = Bad User
log level = 1
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# printcap name = cups
dns proxy = No
# printer admin = @adm
hosts allow = 172.25. 127. 192.168.
# printing = cups
local master = no
[homes]
comment = Home Directories
read only = No
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
