Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build-support/vm: Use devtmpfs, not static device nodes #32390

Merged
merged 1 commit into from Dec 12, 2017

Conversation

dezgeg
Copy link
Contributor

@dezgeg dezgeg commented Dec 6, 2017

In 2017, there is no reason to create a static /dev.

I have tested this with:

nix-build nixos -I nixos-config=nixos/maintainers/scripts/ec2/amazon-image.nix -A config.system.build.amazonImage

and

nix-build release.nix -A rpm_fedora25i386

in Nix repository.

Do @edolstra and/or @copumpkin know anything else that might be using this?

In 2017, there is no reason to create a static /dev.
@copumpkin
Copy link
Member

I can't think of much else, no. The only reason I can think of for not doing it is that it could expose more impurities than the minimal set of device nodes we normally expose. Probably not a big deal though.

@dezgeg
Copy link
Contributor Author

dezgeg commented Dec 11, 2017

Well, I expect the dynamic device node list to be a smaller pain, since you don't need to hunt down missing device nodes that applications assume are "always" there (like in 9f74cf3). And I don't need to figure out how to manually create the serial device node on AArch64 (which is ttyAMA0 there).

@dezgeg dezgeg merged commit 0d27df2 into NixOS:master Dec 12, 2017
@copumpkin
Copy link
Member

Great, thanks 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants