Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta@hanzlici.cz>
To: "Alain M." <alainm@pobox.com>
Cc: dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: Multi-user and shared directories
Date: Fri, 31 Aug 2007 01:12:38 +0200	[thread overview]
Message-ID: <46D74EE6.2020600@hanzlici.cz> (raw)
In-Reply-To: <46D73C56.5080302@pobox.com>

"umod 002" -> "umask 002"

"you can only have one group to a file/directory" : it isn't very right,
at least ext2, ext3 and xfs filesystems supports POSIX Access Control Lists
(ACL - see "man acl", "man getfacl","man setfacl") and is possible set
different access rights (read, write, search/execute) on directories/files
for different users and different groups. And on directories is possible set
default ACL, again for different users and/or different groups, and new
objects inherits default ACL of the containing directory as its access ACL.

Frantisek Hanzlik

Alain M. wrote:
> I looks like your explanation "chmod 002" was meant "umod 002" and thus
> would be "chmod 775" which is correct.
> 
> But remember that you can only have one group to a file/directory, that
> is a Linux limitation. Maybe you need an extra group...
> 
> Alain
> 
> Roberto Bechtlufft escreveu:
>> Ok, question number 327 :-)
>>
>> Suppose I have users roberto and fatima. roberto is under the groups
>> roberto and dosemu, and fatima is under fatima and dosemu. When I do a
>> chmod 002 and as roberto create a new file all users under the group
>> roberto can read and write to it. However, I want my files to be
>> created under the dosemu group, and not roberto, so fatima can read
>> and write to it to. How can I do it?
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> !DSPAM:46d73b9562671804284693!
> 

  reply	other threads:[~2007-08-30 23:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 15:04 Multi-user and shared directories Roberto Bechtlufft
2007-08-29 15:37 ` Frank Cox
2007-08-29 15:52   ` Roberto Bechtlufft
     [not found] ` <1201128185-1188400615-cardhu_decombobulator_blackberry.rim.net-628304760-@bxe018.bisx.prod.on.blackberry>
     [not found]   ` <2c5c60460708290818s4d657d69w306467ee7dc582e6@mail.gmail.com>
     [not found]     ` <23846340-1188412261-cardhu_decombobulator_blackberry.rim.net-436384448-@bxe018.bisx.prod.on.blackberry>
2007-08-29 18:41       ` Roberto Bechtlufft
2007-08-29 18:48         ` Frank Cox
2007-08-30  4:06           ` Roberto Bechtlufft
     [not found]             ` <20070829225309.d960d881.theatre@sasktel.net>
2007-08-30 11:22               ` Roberto Bechtlufft
2007-08-30 20:38                 ` Roberto Bechtlufft
2007-08-30 21:06                   ` Frank Cox
2007-08-30 21:45                   ` Frantisek Hanzlik
2007-08-30 21:53                   ` Alain M.
2007-08-30 23:12                     ` Frantisek Hanzlik [this message]
2007-08-30 23:24                     ` Roberto Bechtlufft
2007-08-30  8:21 ` Frantisek Hanzlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D74EE6.2020600@hanzlici.cz \
    --to=franta@hanzlici.cz \
    --cc=alainm@pobox.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox