public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: DOS namespaces, accessible/walk-able as Admin via Cygwin?
Date: Thu, 25 Apr 2024 23:23:00 -0600	[thread overview]
Message-ID: <ad10d976-4342-4114-9319-03884ca26c30@SystematicSW.ab.ca> (raw)
In-Reply-To: <CAAvCNcByRFaUeWPhm4F_Mxbytw0W0xARymy+7Ch5kp02oszQsw@mail.gmail.com>

On 2024-04-25 19:45, Dan Shelton via Cygwin wrote:
> On Mon, 22 Apr 2024 at 07:01, Brian Inglis via Cygwin wrote:
>> On 2024-04-21 17:24, Dan Shelton via Cygwin wrote:
>>> On Sat, 20 Apr 2024 at 05:37, Brian Inglis via Cygwin wrote:
>>>>> 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.
>>
>>>> $ 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.
>>
>>> Now where does the "1" in /proc/sys/Sessions/1/BaseNamedObjects come
>>> from? Is there a Cygwin or Win32 API for that?
>>
>> It's the MS Windows session number for the first user session.
>> You can access them using Cygwin or MS Windows directory lookups or tree
>> browsers, as I said.
>> Search microsoft.com for Windows sessions for details about MS Windows APIs.
> 
> Windows has multiple session apis (terminal, logon, ...), which is
> used for the DOS namespace?

There really does not appear to be a "DOS" namespace, rather there are a bunch 
of legacy object names in the namespaces which may be used by console and GUI 
programs to access and operate on the underlying objects, possibly also using 
legacy APIs.

>>>> Under MS Windows you can use Sysinternals WinObj64 to browse the hierarchy and
>>>> objects.
>>>
>>> What is that?
>>
>> If you do not yet know that, perhaps you should not yet be digging into these MS
>> Windows Executive subsystem objects.
>>
>> Some of these questions seem very abstract - are these academic questions or
>> projects?
> 
> Building knowledge, learning, and debugging actual code.

Have a look at the object hierarchies either using a Cygwin tree browser or the 
winobj64 object browser to see what is actually out there and their properties.

The Cygwin all-volunteer spare time project's interest is in using newlib libc 
and Windows APIs to provide Unix functionality, to relevant POSIX standards if 
available and appropriate.

For anything else you should consult the available project documentation in the 
cygwin-doc package or online, in the newlib-cygwin/winsup/cygwin C++ source code 
providing the emulation, any MS Windows documentation that the vendor cares to 
make available, and perhaps other MS Windows emulation based open source 
projects like Wine, mingw64, msys2, etc.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

      reply	other threads:[~2024-04-26  5:23 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
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 [this message]

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=ad10d976-4342-4114-9319-03884ca26c30@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).