Please, anybody reply if they know of problems that could arise out of
this "fixed" premission problems.
What I ended up doing, is to set create mask and directory mode to 0777
(even with public = yes) for the samba side and for NFS, I (big gulp
here) ran the command umask 000 from my p.c. - what
On Wed, 29 Jan 2003 12:04:36 +
Anne Wilson <[EMAIL PROTECTED]> wrote:
Yes, that thought came to mind recently about not using smbusers as a
name for a group but then again alot of things have passed thru my mind
and am sort of feeling overwelmed about all this!
When I create smbusers group on
On Wednesday 29 Jan 2003 3:42 am, Steve Jeppesen wrote:
> On Tue, 28 Jan 2003 08:56:26 +
>
> Anne Wilson <[EMAIL PROTECTED]> wrote:
> > I don't know anything about nfs really, but I just wondered if this
> > suggestion would help. Why not make a group for those users and make
> > your default
On Tue, 28 Jan 2003 08:56:26 +
Anne Wilson <[EMAIL PROTECTED]> wrote:
> I don't know anything about nfs really, but I just wondered if this
> suggestion would help. Why not make a group for those users and make
> your default group to be that one? I would have thought that all of
> them would
On Monday 27 Jan 2003 11:33 pm, Steve Jeppesen wrote:
> I think the problem is since I am not using samba for my linux p.c. to
> connect to the linux server, NFS is keeping my permissions on anything I
> create into the shared directory - thus no one using samba can add
> anything or change what I
On 27 Jan 2003 16:25:43 +1100
Stephen Kuhn <[EMAIL PROTECTED]> wrote:
> If you want a truly open/public share, you can do like this:
>
> [ddrive]
> comment = D Drive
> path = /mnt/d-drive
> read only = No
> public = Yes
I changed that share to this;
[shared]
writa
I have just searched thru about a year and a half worth of posts
concerning this subject, but have not found a simple way of fixing this.
We have a "trusted" home network, 3 Win98 clients, 1 WinME client, 1 MD
9.0 client and a MD 9.0 server/router/firewall setup. You can guess
whom the MD 9.0 cli
