WSL: Missing source code - GPL compliance?

As far as I can tell, bash.exe is under the GPLv3 license.

C:\Users\VM>bash.exe --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
root@localhost:~# bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

I wasn’t able to locate the source code; if the file(s) or link could be shared here that would be appreciated.

About this issue

  • Original URL
  • State: closed
  • Created 11 years ago
  • Reactions: 4
  • Comments: 24 (13 by maintainers)

Most upvoted comments

@Manouchehri. The Windows Subsystem for Linux (WSL) doesn’t modify or derive any GPL code: It runs native, unmodified ELF binaries by loading them into a lightweight process created by the Windows Kernel, binding the ELF binary’s imports to our syscall implementation and then executing as normal.

Bash.exe is a simple Windows app that binds a console (i.e. terminal) window to a process that loads and runs the native /bin/bash from the Ubuntu image you downloaded when you first enabled the WSL. Bash.exe performs no other significant actions, and, in fact, passes all command-line parameters, unmodified, to /bin/bash, which is why, when you run bash --help, you see the help text generated by /bin/bash:

C:\Users\richturn>bash --help
GNU bash, version 4.3.11(1)-release-(x86_64-pc-linux-gnu)
Usage:  /bin/bash [GNU long option] [option] ...
        /bin/bash [GNU long option] [option] script-file ...
GNU long options:
        --debug
        --debugger
        --dump-po-strings
        --dump-strings
        --help
        --init-file
        --login
        --noediting
        --noprofile
        --norc
        --posix
        --rcfile
        --restricted
        --verbose
        --version
Shell options:
        -ilrsD or -c command or -O shopt_option         (invocation only)
        -abefhkmnptuvxBCHP or -o option
Type `/bin/bash -c "help set"' for more information about shell options.
Type `/bin/bash -c help' for more information about shell builtin commands.
Use the `bashbug' command to report bugs.

It was named Bash.exe as a convenience since, in end-user testing, most users expected bash to run when bash was entered into the command-line or start menu.

HTH.

@dethoma But when I run bash.exe --version, it doesn’t give me the Windows EULA.

Running bash on a non-UNIX seems feels derived to me, not sure though.

Since WSL doesn’t ship any distro binaries, you find/view the sources via the distro publisher themselves - i.e. Canonical/Ubuntu, SUSE, Debian, Kali, etc.

Here’s Ubuntu’s bash package.

I’ve already taken a peak at the binary and it doesn’t look too complex, so I don’t see why there would be a lot of objections to releasing it.

@Manouchehri currently bash.exe is the only publicly documented entrypoint. We are working on others. If you have ideas or opinions on the topic please share feedback on our user voice page: http://aka.ms/winbashuv

That’s my point though, you are running the real GNU bash, it is not derived in any shape or form.

Just because you happen to run a program called bash.exe that makes a Windows system call to execute the GNU bash binary(I’m guessing at how this actually works) does not mean that bash.exe is derived from GNU bash.

If MSFT were taking GNU bash, recompiling it for Win32 ala Cygwin, then yes, they would need to publish the source code for it, but as it stands all the source code for all the Linux binaries being executed are available directly from the upstream Ubuntu.