docs: audit server information media stubs

This commit is contained in:
Mario Fetka
2026-06-02 17:39:27 +00:00
parent 7b51eb768e
commit 5038823aba
3 changed files with 60 additions and 4 deletions

21
AI.md
View File

@@ -746,3 +746,24 @@ Latest endpoint audit checkpoint from patch 0234:
include/WebSDK material surfaced the surrounding `nwfse` structs more clearly.
Next patch number should be `0235`.
Latest endpoint audit checkpoint from patch 0235:
- SDK `0x2222/123` / wire `0x7b` server information/statistics now records the
next Media Manager / volume selector run behind `MARS_NWE_4` in
`src/nwconn.c`: `123/30` Get Media Manager Object Information, `123/31` Get
Media Manager Objects List, `123/32` Get Media Manager Object Children's List,
`123/33` Get Volume Segment List, and `123/34` Get Volume Information by
Level.
- This block was checked against the local NDK/Core Protocols PDF plus the
uploaded WebSDK/include `nwfse` material. `123/34` has an internal
`InfoLevelNumber` payload selector for the returned volume-information
structure; do not treat those levels as separate wire subfunctions.
- Future ownership remains the `servermgmt`/information provider boundary, with
filesystem/namespace/volume-provider input for real volume/media state. Do
not invent a separate NetWare Media Manager database and do not route these
data-plane requests through `nwserv`.
- Remaining `123/40` and higher protocol-stack, router/SAP, server/set-command,
and compression information selectors still need later follow-up auditing.
Next patch number should be `0236`.

12
TODO.md
View File

@@ -277,10 +277,14 @@ SDK-listed blocks that do not currently show a top-level handler in
Information, `123/25` LSL Information, and `123/26` LSL Logical Board
Statistics. Patch 0234 completes the adjacent LAN/LSL/MLID selector run
with `123/24` LAN Name Information and `123/27` MLID Board Information after
rechecking the local NDK/Core Protocols PDF entries. The remaining `123/30`
and higher media-manager, protocol-stack, router/SAP, set-command, volume,
and compression information selectors still need follow-up auditing before
any additional stubs are added.
rechecking the local NDK/Core Protocols PDF entries. Patch 0235 adds the
Media Manager / volume selector run: `123/30` Get Media Manager Object
Information, `123/31` Get Media Manager Objects List, `123/32` Get Media
Manager Object Children's List, `123/33` Get Volume Segment List, and
`123/34` Get Volume Information by Level. The remaining `123/40` and higher
protocol-stack, router/SAP, set-command, server/source, and compression
information selectors still need follow-up auditing before any additional
stubs are added.
Follow-up:

View File

@@ -7693,6 +7693,37 @@ static int handle_ncp_serv(void)
* Current MARS_NWE_4 scope should model the
* 4.x layout only if this is ever enabled.
*/
case 0x1e: /* 123/30 Get Media Manager Object Information.
* Request selects ObjectNumber.
* Reply carries GenericInfoDef-style media
* manager object information. Future owner
* is servermgmt plus the filesystem/volume
* provider; do not invent a parallel media
* manager object graph.
*/
case 0x1f: /* 123/31 Get Media Manager Objects List.
* Request carries StartNumber and ObjectType.
* Reply carries nextStartNum, ObjectCount,
* and a list of media manager object IDs.
*/
case 0x20: /* 123/32 Get Media Manager Object Children's
* List. Request carries StartNumber,
* ObjectType, and ParentObjectNumber; reply
* uses the same list-window shape as 123/31.
*/
case 0x21: /* 123/33 Get Volume Segment List.
* Request selects VolumeNumber.
* Reply carries NumOfSegments followed by
* VolumeSegment records. Future work should
* bridge to the real namespace/volume layout.
*/
case 0x22: /* 123/34 Get Volume Information by Level.
* Request selects VolumeNumber plus
* InfoLevelNumber (0=VolInfo, 1=VolInfoDef,
* 2=VolInfo2Def in the NDK/include material).
* Treat InfoLevelNumber as a payload selector,
* not a separate wire subfunction.
*/
completition = 0xfb;
break;
default: completition = 0xfb;