From: sl@9front.org
To: 9front@9front.org
Subject: hjfs enforces less restrictions on user none
Date: Tue, 19 May 2015 11:55:29 -0400 [thread overview]
Message-ID: <9107c50a0119b3cb047c882720ac13a8@u2.sfldmibb.det.wayport.net> (raw)
Through non-exhaustive trial and error I observed that my machine
running hjfs allows user none to write to chmod g+w files that are
chgrp none, while my machine running cwfs does not.
Is this discrepancy intentional?
sl
reply other threads:[~2015-05-19 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9107c50a0119b3cb047c882720ac13a8@u2.sfldmibb.det.wayport.net \
--to=sl@9front.org \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).