From: Dan Shelton <dan.f.shelton@gmail.com>
To: cygwin@cygwin.com
Subject: Re: DOS namespaces, accessible/walk-able as Admin via Cygwin?
Date: Mon, 22 Apr 2024 01:24:21 +0200 [thread overview]
Message-ID: <CAAvCNcCufFgHRokmARNYnC22mCDk9LyUt2WCm-rRAo0wqsYDVg@mail.gmail.com> (raw)
In-Reply-To: <608a6fa5-22e0-4b46-b1c9-9074be3aa1e1@Shaw.ca>
On Sat, 20 Apr 2024 at 05:37, Brian Inglis via Cygwin <cygwin@cygwin.com> wrote:
>
> On 2024-04-19 17:09, Dan Shelton via Cygwin wrote:
> > 1. Windows has DOS namespaces per user, or per Logon.
> > Can anyone explain this from a Win32 API point of view how they are kept
> > separate?
>
> Ask on SuperUser *NOT* SO!
I cannot follow you. What should I do?
>
> > 2. If I have Administrator rights, is there a way in /proc where I can
> > /bin/ls -la or /bin/find -ls all those DOS namespaces and soft links
> > to the real devices?
>
> Cygwin exposes these MS Windows Executive Object Manager subsystem resource
> objects under /proc/sys/ and object namespaces are per session under
> /proc/sys/Sessions/ you have e.g.
*THANKS*
>
> $ ls -glo /proc/sys/Sessions/BNOLINKS/
> total 0
> lr--r--r-- 1 0 Apr 19 21:23 0 -> /proc/sys/BaseNamedObjects
> lr--r--r-- 1 0 Apr 19 21:23 1 -> /proc/sys/Sessions/1/BaseNamedObjects
>
> so each session has its own set of BaseNamedObjects, which you can list with
> appropriate permissions, or using a tree browser.
Thanks.
Now where does the "1" in /proc/sys/Sessions/1/BaseNamedObjects come
from? Is there a Cygwin or Win32 API for that?
> Under MS Windows you can use Sysinternals WinObj64 to browse the hierarchy and
> objects.
What is that?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
next prev parent reply other threads:[~2024-04-21 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 23:09 Dan Shelton
2024-04-20 3:37 ` Brian Inglis
2024-04-21 23:24 ` Dan Shelton [this message]
2024-04-22 0:02 ` Bill Stewart
2024-04-22 5:01 ` Brian Inglis
2024-04-26 1:45 ` Dan Shelton
2024-04-26 5:23 ` Brian Inglis
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=CAAvCNcCufFgHRokmARNYnC22mCDk9LyUt2WCm-rRAo0wqsYDVg@mail.gmail.com \
--to=dan.f.shelton@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).