Re: [Samba] Linux smbfs differences
Hi, On 29-jul-04, at 14:44, Gabor Kiss [Bitman] wrote: but my 2.4 config is here: # # Network File Systems # ... CONFIG_SMB_FS=m CONFIG_SMB_NLS_DEFAULT=y CONFIG_SMB_NLS_REMOTE="utf8" CONFIG_SMB_UNIX=y I think your Linux vendor has patched your sources. Because if I look in the original sources I compile myself my kernels from original sources. (http://lxr.linux.no/source/arch/i386/defconfig?v=2.4.26) there is no such option. This because "CONFIG_SMB_FS is not set". Check the _original_ source: $ ls -l linux-2.4.26/fs/smbfs/proc.c -rw-r--r--1 root root 83490 Apr 14 15:05 linux-2.4.26/fs/smbfs/proc.c It 'should' be in the defconfig , but well it doesn't matter anything at all at the end so who am i to complain about that ;-))) such option. On the other hand, it doesn't make clear why several options need to be ignored. I've no inten^H^H^Hformation to answer this question. ;-) I just pointed out that you CAN achieve identical (however unwanted) behavior of 2.4 and 2.6 smbfs implementation. Thanks for your help so far, i've just found out that the pre-packaged 2.6 debian kernels don't have the SMB_UNIX parameter set, that explains why I've found this problem just a short time ago. Well, hopefully someone will answer my question. For other people who want to know how to force the shared files/directories: [data] force group = users force create mode = 0770 force directory mode = 0770 Met vriendelijke groet, Micha Kersloot http://www.mailwasserette.nl/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux smbfs differences
> > but my 2.4 config is here:
> > #
> > # Network File Systems
> > #
> > ...
> > CONFIG_SMB_FS=m
> > CONFIG_SMB_NLS_DEFAULT=y
> > CONFIG_SMB_NLS_REMOTE="utf8"
> > CONFIG_SMB_UNIX=y
>
> I think your Linux vendor has patched your sources. Because if I look
> in the original sources
I compile myself my kernels from original sources.
> (http://lxr.linux.no/source/arch/i386/defconfig?v=2.4.26) there is no
> such option.
This because "CONFIG_SMB_FS is not set".
Check the _original_ source:
$ ls -l linux-2.4.26/fs/smbfs/proc.c
-rw-r--r--1 root root 83490 Apr 14 15:05 linux-2.4.26/fs/smbfs/proc.c
$
Its content:
int
smb_newconn(struct smb_sb_info *server, struct smb_conn_opt *opt)
{
...
#ifndef CONFIG_SMB_UNIX
server->opt.capabilities &= ~SMB_CAP_UNIX;
#endif
if (server->opt.capabilities & SMB_CAP_UNIX) {
struct inode *inode;
VERBOSE("Using UNIX CIFS extensions\n");
install_ops(server->ops, &smb_ops_unix);
inode = SB_of(server)->s_root->d_inode;
if (inode)
inode->i_op = &smb_dir_inode_operations_unix;
}
linux-2.4.26/fs/smbfs/Changelog writes:
2004-01-24 John Newbigin <[EMAIL PROTECTED]>
* *.c: Implementation of CIFS Extensions for UNIX systems
> such option. On the other hand, it doesn't make clear why several
> options need to be ignored.
I've no inten^H^H^Hformation to answer this question. ;-)
I just pointed out that you CAN achieve identical (however unwanted)
behavior of 2.4 and 2.6 smbfs implementation.
Gabor
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux smbfs differences
Hi, On 29-jul-04, at 12:26, Gabor Kiss [Bitman] wrote: smbmount //server/share /mountpoint -o uid=100,gid=100 makes all the files owned by uid 100 on a 2.4 kernel. The same command on a 2.6 kernel makes the mountpoint owned by uid 100, the rest of the files have the uid's as set on the server. Is CONFIG_SMB_UNIX enabled in 2.4 kernels? | CONFIG_SMB_UNIX: | | Enabling this will make smbfs use the CIFS Unix Extensions if | supported by the server. These extensions allows use of unix user | ids, permissions, file modes, symlinks, etc that normally do not | work on smbfs. | | Samba 3.0 servers supports these extensions. No, that is not enabled, but I can't find the option in the .config of 2.4 or 2.6. This is true for 2.6 (I guess extensions are always enabled) but my 2.4 config is here: # # Network File Systems # ... CONFIG_SMB_FS=m CONFIG_SMB_NLS_DEFAULT=y CONFIG_SMB_NLS_REMOTE="utf8" CONFIG_SMB_UNIX=y I think your Linux vendor has patched your sources. Because if I look in the original sources (http://lxr.linux.no/source/arch/i386/defconfig?v=2.4.26) there is no such option. On the other hand, it doesn't make clear why several options need to be ignored. Greetings, Micha Kersloot http://www.kovoks.nl/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux smbfs differences
> >> smbmount //server/share /mountpoint -o uid=100,gid=100 > >> makes all the files owned by uid 100 on a 2.4 kernel. The same command > >> on a 2.6 kernel makes the mountpoint owned by uid 100, the rest of the > >> files have the uid's as set on the server. > > > > Is CONFIG_SMB_UNIX enabled in 2.4 kernels? > > > > | CONFIG_SMB_UNIX: > > | > > | Enabling this will make smbfs use the CIFS Unix Extensions if > > | supported by the server. These extensions allows use of unix user > > | ids, permissions, file modes, symlinks, etc that normally do not > > | work on smbfs. > > | > > | Samba 3.0 servers supports these extensions. > > No, that is not enabled, but I can't find the option in the .config of > 2.4 or 2.6. This is true for 2.6 (I guess extensions are always enabled) but my 2.4 config is here: # # Network File Systems # ... CONFIG_SMB_FS=m CONFIG_SMB_NLS_DEFAULT=y CONFIG_SMB_NLS_REMOTE="utf8" CONFIG_SMB_UNIX=y Gabor -- E-mail = m-mail * c-mail ^ 2 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux smbfs differences
Hoi, On 27-jul-04, at 12:43, Gabor Kiss [Bitman] wrote: For example: smbmount //server/share /mountpoint -o uid=100,gid=100 makes all the files owned by uid 100 on a 2.4 kernel. The same command on a 2.6 kernel makes the mountpoint owned by uid 100, the rest of the files have the uid's as set on the server. Is CONFIG_SMB_UNIX enabled in 2.4 kernels? | CONFIG_SMB_UNIX: | | Enabling this will make smbfs use the CIFS Unix Extensions if | supported by the server. These extensions allows use of unix user | ids, permissions, file modes, symlinks, etc that normally do not | work on smbfs. | | Samba 3.0 servers supports these extensions. No, that is not enabled, but I can't find the option in the .config of 2.4 or 2.6. But this makes my question why does the option CONFIG_SMB_UNIX makes some the configuration options and some of the command line options obsolete. Especially when they are so 'handy' when you want to share some files. Met vriendelijke groet, Micha Kersloot Voorzitter NLLGG http://www.nllgg.nl/ icq: 7153298 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux smbfs differences
> For example: > smbmount //server/share /mountpoint -o uid=100,gid=100 > makes all the files owned by uid 100 on a 2.4 kernel. The same command > on a 2.6 kernel makes the mountpoint owned by uid 100, the rest of the > files have the uid's as set on the server. Is CONFIG_SMB_UNIX enabled in 2.4 kernels? | CONFIG_SMB_UNIX: | | Enabling this will make smbfs use the CIFS Unix Extensions if | supported by the server. These extensions allows use of unix user | ids, permissions, file modes, symlinks, etc that normally do not | work on smbfs. | | Samba 3.0 servers supports these extensions. Gabor -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Linux smbfs differences
Hi, We are using samba in a mixed Linux/Windows environment. The server is a samba 3.0.2a PDC and the clients are Windows XP and Linux (debian). Debian version is unstable, a week old on all machines. The thing is that there seem to be several differences depending on which kernel we use on the clients. It looks like the differences are concentrated on the username / user rights part. I didn't find a list which describes this, but so far I've found at least the following options are working different, or are not working at all on a 2.6.5+ kernel(on the client): smb.conf - create mask = directory mask = inherit permissions = yes smbmount - uid= gid= fmask= dmask= For example: smbmount //server/share /mountpoint -o uid=100,gid=100 makes all the files owned by uid 100 on a 2.4 kernel. The same command on a 2.6 kernel makes the mountpoint owned by uid 100, the rest of the files have the uid's as set on the server. Are my conclusions right? Are there more options which work different and is there a list? The only way i've found to really share files is to use: force group = user force create mode = 0770 force directory mode = 0770 Is there an other way? I hope someone can help. Greetings, Micha Kersloot http://www.kovoks.nl/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
