From: Bob McGowan <ramjr0915@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Looking for explanation
Date: Fri, 17 Jul 2020 15:52:08 -0700 [thread overview]
Message-ID: <28bad3eb-a354-b9f3-9dfb-ba135cb8d6eb@gmail.com> (raw)
In-Reply-To: <1dc80f24-face-8794-848c-e2f062746e79@bellsouth.net>
On 7/17/20 3:33 PM, Robert McBroom wrote:
> On 7/17/20 12:27 PM, Eliot Moss wrote:
>> On 7/17/2020 12:16 PM, Robert McBroom wrote:
>> > Directory listing shows a number of new features that I don't
>> remember being introduced.?? I see
>> > s,t,+ etc. other than the expected wxr. Where would I look for an
>> explanation?
>>
>> Dear Robert:
>>
>> s and t are usual from Posix and Cygwin tries to come as close to
>> Posix as it can under Windows.?? s is for setuid/setgid and t is the
>> "sticky" bit.?? The + indicates that there
>> are more refined access modes present.
>>
>> You might want to read up on ls, chmod, getfacl, etc.
>>
>> What _can_ get funky and confusing is the mapping from Windows ACLs to
>> what Cygwin
>> reports and Cygwin's manipulation of ACLs.?? There is online Cygwin
>> documentation about that as well.
>>
>> None of this is new.?? Maybe something changed the file permissions,
>> and now they show up this way for you??? Not sure what your real
>> question is ...
>>
> UNIX use predates posix. Don't see any of these designations on Fedora
> even on ntfs file systems. Haven't dived into them because my objective
> is to run scientific calculations, but curiosity got the better of me.
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Actually, the 's' and 't' designators predate POSIX.
I have an old Bell Laboratories "UNIX programmer's manual", copyright
1983, 1979 (for UNIX 7th Edition), and it mentions both the 's' and 't'
in the 'ls' man page.
Bob
next prev parent reply other threads:[~2020-07-17 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d23e7aeb-1600-cb72-28d6-f0a758d91ff6.ref@bellsouth.net>
2020-07-17 16:16 ` Robert McBroom
2020-07-17 16:27 ` Eliot Moss
2020-07-17 22:33 ` Robert McBroom
2020-07-17 22:52 ` Bob McGowan [this message]
2020-07-17 22:59 ` Eliot Moss
2020-07-17 19:59 ` Marco Atzeri
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=28bad3eb-a354-b9f3-9dfb-ba135cb8d6eb@gmail.com \
--to=ramjr0915@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).