On Mo, 07.09.26 16:54, Skye Soss ([email protected]) wrote: > From: Lennart Poettering <[email protected]> > Date: Mon, 07 Sep 2026 11:50:47 -0500 > > Huh, what's the usecase for this? why would you want to combine that? > > i don't get it? > > > > I'd normally expect people to either use subuids and the stuff that > > comes with it, or uses nsresoured stuff, but i fail to see why you'd > > want both for the same container? > > This isn't for containers, but instead for programs like Disk Usage Analyzer > or trash-utils that work on > arbitrary files owned by users. A user should be able to create a user > namespace where they have access > to all of "their own" files for management, organization, searching, > indexing, etc.
Uh, that's not really how nsresourced is designed. And I don't get what the purpose of this is? I can see that it might be useful to get access to a specific OS tree to make modifications/create them/delete them. But why do you have to have access to *all* of them from the *same* process at the *same* process? I'd always expect you fork off workers that join the processes individually, operate on one of them each, and exit when done? Lennart -- Lennart Poettering, Berlin
