Announcement

Collapse
No announcement yet.

Microsoft Developer Shows Linux Commands Seamlessly Integrated Within Windows PowerShell

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ryad
    replied
    Wow, this hate against MS is still real, even in 2019.
    Guys grow up, this news is good news for everybody!
    As an Arch user for over 10 years now, I really respect and appreciate the WSL efforts.

    Leave a comment:


  • Xaero_Vincent
    replied

    Originally posted by tildearrow View Post

    It is Xaero_Vincent's pseudo-Linux Windows OS install.
    ​​​​​It is basically Windows with the shell replaced by a full-screen instance of VMWare running a Linux distro with some scripts to run Windows games from that Linux virtualized instance.
    This way he thinks he can get support for all Windows games while having a Linux desktop running.

    What is surprising is that he somehow got the Linux terminal window to appear as if it were part of the desktop instead of being always underneath (which was the case in 2017).
    That was the old setup but was an interesting use case at the time. I wrote several programs to manage the environment and make it more seamless. Now I have the exact opposite. :P

    I've since upgraded to using native, bare-metal Arch Linux. Proton & Wine have improved vastly enough to play most games I want. At the time in 2017, Direct3D 9 was the best Wine could do. I use In-Home Streaming from a separate Windows box when I want to play any EAC/BattlEye protected or UWP/Windows Store games.

    This is Arch Linux with a headless/invisible Windows 10 VM running locally on the same machine and using RemoteApp to run individual apps and a VM file share to share/access files between them. I made a simple script so that I can launch any Windows apps from Linux desktop launchers or shell scripts in this way. It's quite useful for dealing with UWP apps.

    Considering that WSL2 is using a headless Hyper-V virtual machine, my new set-up is actually very similar, just using Windows rather than Linux guests. It's also similar in behavior to Chrome OS's Crostini.
    Last edited by Xaero_Vincent; 27 September 2019, 01:44 AM.

    Leave a comment:


  • lowflyer
    replied
    Why on earth would somebody want to use powershell when you can use bash instead
    .

    Leave a comment:


  • mos87
    replied
    Haha classic. Embrace extend extinguish)

    Leave a comment:


  • tildearrow
    replied
    Originally posted by robojerk View Post
    If you just want grep, run bash scripts and stuff like that couldn't you just install git on Windows?
    They're doing this so that you don't have to.

    Leave a comment:


  • robojerk
    replied
    If you just want grep, run bash scripts and stuff like that couldn't you just install git on Windows?

    Leave a comment:


  • ElectricPrism
    replied
    Originally posted by zxy_thf View Post
    This is Great. The only problem is

    I want bash instead of powershell, even on Windows....
    This is great just replace all the Windows bits with all the Linux bits and we'll call it perfect.

    Leave a comment:


  • zxy_thf
    replied
    This is Great. The only problem is

    I want bash instead of powershell, even on Windows....

    Leave a comment:


  • tildearrow
    replied
    Originally posted by Templar82 View Post

    What am I looking at here?
    It is Xaero_Vincent's pseudo-Linux Windows OS install.
    ​​​​​It is basically Windows with the shell replaced by a full-screen instance of VMWare running a Linux distro with some scripts to run Windows games from that Linux virtualized instance.
    This way he thinks he can get support for all Windows games while having a Linux desktop running.

    What is surprising is that he somehow got the Linux terminal window to appear as if it were part of the desktop instead of being always underneath (which was the case in 2017).
    Last edited by tildearrow; 26 September 2019, 08:32 PM.

    Leave a comment:


  • chithanh
    replied
    How about Microsoft works on actual interoperability. Stopping to hijack wget and curl commands on Windows PowerShell, and not aliasing them to Invoke-WebRequest would be a start. Similar to other Unix commands like ls and rm.
    They block use of the commonly used command line tools without providing even an attempt to offer the same functionality. They serve no purpose for PowerShell users but cause confusion and problems...

    Leave a comment:

Working...
X