Retire administrative exact-entry adapters #34
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/ramfsd!34
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/administrative-entry-retirement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove administrative RAM entry adapters after retained acquisition and source-free effects take ownership. The provider selects the retained-only IPC interface; retired operation numbers remain unassigned. Handle metadata and generic directory reads remain available.
Depends on #33. Related: #8, erix/vfsd#16, erix/integration#65. Cross-provider rollout and release-image acceptance remain separate work.
WIP: Retire administrative exact-entry adaptersto Retire administrative exact-entry adaptersThe RAM provider now uses the retained-only IPC interface throughout native acquisition and mutation. The final changes remove obsolete scaffolding and correct stale documentation; original-key cleanup, invalid-frame refusal and live handle metadata remain covered. This component is ready for review. Native release-image acceptance remains open.