ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Understanding BASH on Windows

    Scheduled Pinned Locked Moved IT Discussion
    27 Posts 8 Posters 2.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • zuphzuphZ
      zuphzuph Banned @scottalanmiller
      last edited by

      @scottalanmiller said in Show me the $PowerShell.:

      @zuphzuph said in Show me the $PowerShell.:

      @travisdh1 said in Show me the $PowerShell.:

      What if I work in Bash instead of PowerShell?

      Can't fault you for that. But I'd call you bleeding edge. 😛

      BASH via CygWin on Windows is like 20 years old.

      I was throw with the release of the BASH shell in 10, my b.

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @zuphzuph
        last edited by

        @zuphzuph said in Show me the $PowerShell.:

        @scottalanmiller said in Show me the $PowerShell.:

        @zuphzuph said in Show me the $PowerShell.:

        @travisdh1 said in Show me the $PowerShell.:

        What if I work in Bash instead of PowerShell?

        Can't fault you for that. But I'd call you bleeding edge. 😛

        BASH via CygWin on Windows is like 20 years old.

        I was throw with the release of the BASH shell in 10, my b.

        That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

        zuphzuphZ DashrenderD thwrT 3 Replies Last reply Reply Quote 2
        • zuphzuphZ
          zuphzuph Banned @scottalanmiller
          last edited by

          @scottalanmiller said in Show me the $PowerShell.:

          @zuphzuph said in Show me the $PowerShell.:

          @scottalanmiller said in Show me the $PowerShell.:

          @zuphzuph said in Show me the $PowerShell.:

          @travisdh1 said in Show me the $PowerShell.:

          What if I work in Bash instead of PowerShell?

          Can't fault you for that. But I'd call you bleeding edge. 😛

          BASH via CygWin on Windows is like 20 years old.

          I was throw with the release of the BASH shell in 10, my b.

          That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

          Good to know.

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender @scottalanmiller
            last edited by

            @scottalanmiller said in Show me the $PowerShell.:

            @zuphzuph said in Show me the $PowerShell.:

            @scottalanmiller said in Show me the $PowerShell.:

            @zuphzuph said in Show me the $PowerShell.:

            @travisdh1 said in Show me the $PowerShell.:

            What if I work in Bash instead of PowerShell?

            Can't fault you for that. But I'd call you bleeding edge. 😛

            BASH via CygWin on Windows is like 20 years old.

            I was throw with the release of the BASH shell in 10, my b.

            That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

            What exactly is the difference?

            scottalanmillerS 1 Reply Last reply Reply Quote 1
            • scottalanmillerS
              scottalanmiller @Dashrender
              last edited by

              @Dashrender said in Show me the $PowerShell.:

              @scottalanmiller said in Show me the $PowerShell.:

              @zuphzuph said in Show me the $PowerShell.:

              @scottalanmiller said in Show me the $PowerShell.:

              @zuphzuph said in Show me the $PowerShell.:

              @travisdh1 said in Show me the $PowerShell.:

              What if I work in Bash instead of PowerShell?

              Can't fault you for that. But I'd call you bleeding edge. 😛

              BASH via CygWin on Windows is like 20 years old.

              I was throw with the release of the BASH shell in 10, my b.

              That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

              What exactly is the difference?

              One is a shell on Windows, one is not. It's the difference between a steering wheel attached to the wheels of your car... and a LittleTykes plastic steering wheel on the child seat in the back seat that isn't attached to the car.

              That Windows put BASH on Windows is a joke on the users. It's not what people mean, it's not a shell attached to Windows, it's no different than if you install Linux in a VM and that has BASH on it... you can't actually say that that is BASH on Windows with a straight face... and yet, they did.

              DashrenderD 1 Reply Last reply Reply Quote 1
              • DashrenderD
                Dashrender @scottalanmiller
                last edited by

                @scottalanmiller said in Show me the $PowerShell.:

                @Dashrender said in Show me the $PowerShell.:

                @scottalanmiller said in Show me the $PowerShell.:

                @zuphzuph said in Show me the $PowerShell.:

                @scottalanmiller said in Show me the $PowerShell.:

                @zuphzuph said in Show me the $PowerShell.:

                @travisdh1 said in Show me the $PowerShell.:

                What if I work in Bash instead of PowerShell?

                Can't fault you for that. But I'd call you bleeding edge. 😛

                BASH via CygWin on Windows is like 20 years old.

                I was throw with the release of the BASH shell in 10, my b.

                That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

                What exactly is the difference?

                One is a shell on Windows, one is not. It's the difference between a steering wheel attached to the wheels of your car... and a LittleTykes plastic steering wheel on the child seat in the back seat that isn't attached to the car.

                That Windows put BASH on Windows is a joke on the users. It's not what people mean, it's not a shell attached to Windows, it's no different than if you install Linux in a VM and that has BASH on it... you can't actually say that that is BASH on Windows with a straight face... and yet, they did.

                I'm trying to understand what is really wanted? Do you want to run Linux compiled code on a Windows box? Wouldn't you need a Linux version of WINE on Windows for that?

                I never really understood the desire for BASH on Windows - you SSH into a Linux box and there's your BASH - go to town. I suppose what MS was missing was good built in SSH client.
                MS has Powershell instead of BASH to control Windows things. I suppose you want BASH so you can control Linux boxes from Windows, I guess that makes sense. It's lost in translation to me.

                MattSpellerM bbigfordB scottalanmillerS 6 Replies Last reply Reply Quote 1
                • MattSpellerM
                  MattSpeller @Dashrender
                  last edited by

                  @Dashrender said in Show me the $PowerShell.:

                  I suppose what MS was missing was good built in SSH client.

                  Try out Putty if you have not already

                  http://www.chiark.greenend.org.uk/~sgtatham/putty/

                  DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @MattSpeller
                    last edited by

                    @MattSpeller said in Show me the $PowerShell.:

                    @Dashrender said in Show me the $PowerShell.:

                    I suppose what MS was missing was good built in SSH client.

                    Try out Putty if you have not already

                    http://www.chiark.greenend.org.uk/~sgtatham/putty/

                    Of course, but MS still doesn't have one included.. that was my point. But I guess they do now with their sudo BASH 😉

                    scottalanmillerS 1 Reply Last reply Reply Quote 2
                    • bbigfordB
                      bbigford @Dashrender
                      last edited by

                      @Dashrender said in Show me the $PowerShell.:

                      @scottalanmiller said in Show me the $PowerShell.:

                      @Dashrender said in Show me the $PowerShell.:

                      @scottalanmiller said in Show me the $PowerShell.:

                      @zuphzuph said in Show me the $PowerShell.:

                      @scottalanmiller said in Show me the $PowerShell.:

                      @zuphzuph said in Show me the $PowerShell.:

                      @travisdh1 said in Show me the $PowerShell.:

                      What if I work in Bash instead of PowerShell?

                      Can't fault you for that. But I'd call you bleeding edge. 😛

                      BASH via CygWin on Windows is like 20 years old.

                      I was throw with the release of the BASH shell in 10, my b.

                      That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

                      What exactly is the difference?

                      One is a shell on Windows, one is not. It's the difference between a steering wheel attached to the wheels of your car... and a LittleTykes plastic steering wheel on the child seat in the back seat that isn't attached to the car.

                      That Windows put BASH on Windows is a joke on the users. It's not what people mean, it's not a shell attached to Windows, it's no different than if you install Linux in a VM and that has BASH on it... you can't actually say that that is BASH on Windows with a straight face... and yet, they did.

                      I'm trying to understand what is really wanted? Do you want to run Linux compiled code on a Windows box? Wouldn't you need a Linux version of WINE on Windows for that?

                      Yes, you would. The reason the advertising was misleading prior to the release is because it was implied you wouldn't need any of that. Then during the release it became more clear it was nothing more than lack of compatibility.

                      scottalanmillerS 1 Reply Last reply Reply Quote 1
                      • scottalanmillerS
                        scottalanmiller @Dashrender
                        last edited by

                        @Dashrender said in Show me the $PowerShell.:

                        I never really understood the desire for BASH on Windows - you SSH into a Linux box and there's your BASH - go to town.

                        I'm confused. No connection between SSH and BASH.

                        1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @Dashrender
                          last edited by

                          @Dashrender said in Show me the $PowerShell.:

                          I suppose what MS was missing was good built in SSH client.

                          No, PowerShell has had that.

                          1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @Dashrender
                            last edited by

                            @Dashrender said in Show me the $PowerShell.:

                            I never really understood the desire for BASH on Windows

                            Exact same reason as wanting it anywhere else. What is there to understand? People want a mature, well known shell on Windows that is standard on EVERY other system.

                            1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @Dashrender
                              last edited by

                              @Dashrender said in Show me the $PowerShell.:

                              MS has Powershell instead of BASH to control Windows things. I suppose you want BASH so you can control Linux boxes from Windows, I guess that makes sense. It's lost in translation to me.

                              BASH does nothing like that. You are confusing BASH with SSH. BASH has no remote capabilities, it's a shell. We want BASH instead of PS. PS can control Linux remotely via SSH, no BASH needed.

                              We've had BASH on WIndows for 20 years and people use it because it's mature and well known.

                              1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @bbigford
                                last edited by

                                @BBigford said in Show me the $PowerShell.:

                                @Dashrender said in Show me the $PowerShell.:

                                @scottalanmiller said in Show me the $PowerShell.:

                                @Dashrender said in Show me the $PowerShell.:

                                @scottalanmiller said in Show me the $PowerShell.:

                                @zuphzuph said in Show me the $PowerShell.:

                                @scottalanmiller said in Show me the $PowerShell.:

                                @zuphzuph said in Show me the $PowerShell.:

                                @travisdh1 said in Show me the $PowerShell.:

                                What if I work in Bash instead of PowerShell?

                                Can't fault you for that. But I'd call you bleeding edge. 😛

                                BASH via CygWin on Windows is like 20 years old.

                                I was throw with the release of the BASH shell in 10, my b.

                                That's BASH on a Linux pseudo-VM running on top of Windows, not BASH on Windows itself. It's useless. Only working BASH is in Cygwin.

                                What exactly is the difference?

                                One is a shell on Windows, one is not. It's the difference between a steering wheel attached to the wheels of your car... and a LittleTykes plastic steering wheel on the child seat in the back seat that isn't attached to the car.

                                That Windows put BASH on Windows is a joke on the users. It's not what people mean, it's not a shell attached to Windows, it's no different than if you install Linux in a VM and that has BASH on it... you can't actually say that that is BASH on Windows with a straight face... and yet, they did.

                                I'm trying to understand what is really wanted? Do you want to run Linux compiled code on a Windows box? Wouldn't you need a Linux version of WINE on Windows for that?

                                Yes, you would. The reason the advertising was misleading prior to the release is because it was implied you wouldn't need any of that. Then during the release it became more clear it was nothing more than lack of compatibility.

                                Actually, it implied that it WAS that. They make it sound like this was the WINE equivalent. But it isn't, it's just a worthless container.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller @Dashrender
                                  last edited by

                                  @Dashrender said in Show me the $PowerShell.:

                                  @MattSpeller said in Show me the $PowerShell.:

                                  @Dashrender said in Show me the $PowerShell.:

                                  I suppose what MS was missing was good built in SSH client.

                                  Try out Putty if you have not already

                                  http://www.chiark.greenend.org.uk/~sgtatham/putty/

                                  Of course, but MS still doesn't have one included.. that was my point. But I guess they do now with their sudo BASH 😉

                                  Yes, they do and it has zero connection to BASH.

                                  1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller @MattSpeller
                                    last edited by

                                    @MattSpeller said in Show me the $PowerShell.:

                                    @Dashrender said in Show me the $PowerShell.:

                                    I suppose what MS was missing was good built in SSH client.

                                    Try out Putty if you have not already

                                    http://www.chiark.greenend.org.uk/~sgtatham/putty/

                                    Putty is way better than the built in one. But they have their own as well. Their own SSH server, too.

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      Jason Banned
                                      last edited by

                                      ^ Way to derail a thread....

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        There we go, forked it all out.

                                        1 Reply Last reply Reply Quote 0
                                        • MattSpellerM
                                          MattSpeller
                                          last edited by

                                          0_1475624754734_upload-cea277a0-637d-487b-b788-d026351d3fd6

                                          Epic typo or intentional awesome?

                                          1 Reply Last reply Reply Quote 1
                                          • scottalanmillerS
                                            scottalanmiller
                                            last edited by

                                            Fixed

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 2 / 2
                                            • First post
                                              Last post