-
Notifications
You must be signed in to change notification settings - Fork 824
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
/dev/null is a weird file #10
Comments
Maybe the whole idea behind the Linux/Ubuntu subsystem hasn't been fully implemented yet. The UNIX philosophy is that EVERYTHING is a file. For example, /dev/null is a virtual device file. This means that nothing, is something, and that something is represented in userland as a file. On my Debian system, I get the following: john@phobos:~$ stat /dev/null It looks like the Ubuntu subsystem doesn't see /dev/null as a "character special file" which I would think would redirect to >NUL on Windows. |
/dev/null should be a character device with major 1 and minor 3, but it isn't in lxss, so tests like this fail:
|
Shouldn't it be fine if /dev/null was simply a symlink to \Device\Null? |
One side-effect of this breaks sshd (openssh-server), as also mentioned here: MicrosoftDocs/WSL#17 |
The weird file is a known issue and something we intend to fix. It is currently on our backlog. |
Another side-effect: I can't build a different version of Perl, either manually or using the perlbrew package, because its configure script checks for /dev/null's usability. |
anybody want to take a guess at why this is in all of the binaries? https://gist.github.com/cloudkitsch/6f8bcb05f4006b5ea168eb6169ecbf12#file-gistfile1-txt-L335 quality control? |
That's precisely what stat says:
And it's causing problems with some programs (I don't remember what exactly was tripped by this in original userland, but I'm trying to run gentoo userland, and emerge fails sanity checks due to this).
Additionally, it appears there's no way to modify /dev - it always results in Operation not permitted.
The text was updated successfully, but these errors were encountered: