Samba continued . . .

[Ed Allen]

Forwarded message:
>Date: Sat, 27 Jul 2002 10:44:08 -0500
>From: A Duston <hald at sound.net>
>To: kclug at kclug.org
>Subject: Re: Samba continued . . .
>
>Bradley Miller wrote:
>> 
>> Actually I was looking through some thing online and I don't know why for
>> sure it couldn't work for writing.  Actually, let me re-phrase that.  I can
>> read/write/modify when I'm logged in as root on that partition.  It's weird
>> I can't chown anyhing on there as root . . . so it goes.
>
>You can't chown anything on there as root, _because_ it's a vfat32 filesystem
>vfat32 doesn't have anyplace to store the owner/group/mode items.  The 
>user/group is set globally at mount time, and the mode is generated on 
>the fly.
>
>> >Although I wasn't aware that the file system used for 'doze98 was one of
>> >the ones that mounted read only.
>
>vfat32 _is_ read/write from Linux.
>
>Hal
>
To be a little more newbie friendly:

DESCRIPTION
       smbmount  mounts a SMB filesystem. It is usually invoked as
       mount.smbfs from the mount(8) command when using the "-t smbfs"
       option. The kernel must support the smbfs filesystem.

So the 'man' page you need to puzzle over is 'smbmount'.

     username=<arg>
                   specifies  the  username  to  connect  as. If this
                   is not given then the environment variable USER is
                   used. This option can also take the form user%password
                   or user/workgroup or  user/workgroup%password to
                   allow the password and workgroup to be specified as
                   part of the username.

So the "owner" of the mount defaulted to root but can be set to any user
on your system if that user has access to the Win* share. (connect as)