> кстати, кто объяснит разницу между линуксовым ядерным CIFS и простым samba-пакетом. заделитесь
> ссылочкой, если не сложно.Ну как бы они не должны отличаться, по этому и назвали протокол - заранее обговорённый
набор правил и условий. Иначе коннекта не будет. То есть, на сетевом уровне они равны,
разница есть на прикладном уровне, типа авторизация, права, атрибуты, статистика и т.д.
Чуть подробнее тут: http://pserver.samba.org/samba/ftp/cifs-cvs/linux-cifs-clien... (PDF 145k )
Differences between cifs and the older Linux client smbfs
In versions of the Linux kernel prior to 2.6, an older implementation of an SMB/CIFS client, smbfs was
used which will be deprecated starting in Linux kernel 2.6.20. The newer cifs virtual filesystem
introduced various new features, but also introduced some changes which can be confusing for former
smbfs users. Some commonly encountered differences include:
1) configuration
Unlike smbfs and smbclient, configuration for the cifs vfs does not depend on smb.conf. CIFS
configuration is done using /proc (modifying pseudofiles in /proc/fs/cifs) and by specifying module
install parameters (module options passed to /sbin/insmod or modprobe). In addition the cifs vfs does
not use the Samba utilities smbmnt or smbmount as smbfs did. Most of the cifs vfs is implemented in
kernel, although cifs vfs has a small userspace mount helper (mount.cifs)
2) mount syntax:
mounting to older servers (those prior to1997) may require specifying two additional fields beyond
those which smbfs required:
a) The server's netbios (RFC1001) name AND the server's tcp (or ip ) address. CIFS does not
assume, as smbfs did, that the tcp name and the netbios name of the server are the same. The netbios
name of the server is specified by passing the mount option “servern=SERVERNAME” and is not
assumed to be necessarily the same as the tcp name of the server (also note that the netbios name is
usually capitalized). Both tcp/ip name and netbios name have to be specified for mounts for most old
lanman servers. For example:
mount -t cifs //tcp-name-of-server/sharename /mnt -o user=username,sec=lanman,servern=SERVERNAME
b) A security option allowing weaker password hashes to be used. Specifying “sec=lanman” in the
mount options allows the client to send weaker lanman hashes to the server. Older servers such as
Windows 98 require this.
Mounting to more current servers with stronger authentication (ntlmv2) typically requires an additional
mount option (unless the security flags are changed in /proc/fs/cifs) “sec=ntlmv2”
3) Default UID/GID/mode for remote files
For mounts to servers which can report uids and gids (the number representing the user and group
names) such as Samba server, it may be necessary to disable the unix extensions if uids and gids do
not match between cifs client and Samba server. For servers which do not support Unix modes directly
(e.g. Most versions of Windows), the default mode for files differs from that reported by smbfs. The
default mode can be overridden by mount options “file_mode” and “dir_mode”for these server types.
