Skip to content

Inherit more of the environment #151

Open
@nrabulinski

Description

@nrabulinski

This is sort of related to #150 so I won't repeat the backstory here.

I'm creating a separate issue for this since this is a separate design decision - assuming I want to use muvm as basically a "thin compatibility layer" for programs which require 4K pages, the fact that each program starts in pretty much a "clean" environment with hardly any environment variables etc is undesirable. I get why it’s currently designed this way, but do you think having a mode in muvm where as much of the "outside world" as possible is inherited could be viable? Alternatively, what do you think the best approach would be?

Maybe I’m thinking about this the wrong way and instead of having muvm be the binfmt interpreter, I should put the nix daemon inside of muvm? Do you think that’d potentially solve this and #150?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions