BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Windows Subsystem for Linux
- Subject: [Discuss] Windows Subsystem for Linux
- From: bill.n1vux at gmail.com (Bill Ricker)
- Date: Sun, 7 Aug 2016 11:15:57 -0400
- In-reply-to: <CAMdng5swuGZOeQPmFpcoQtPEJY_+Ga+F==bkgrettq2jaTjdFQ@mail.gmail.com>
- References: <60879513-9276-0912-1fbf-bdb6aa25b979@gmail.com> <CAMdng5swuGZOeQPmFpcoQtPEJY_+Ga+F==bkgrettq2jaTjdFQ@mail.gmail.com>
On Sun, Aug 7, 2016 at 12:17 AM, Shirley M?rquez D?lcey <mark at buttery.org> wrote: > I can see it becoming a big hit with system administrators. Not just > to run Linux applications, but also to use bash as a shell rather than > PowerShell. Admins who work with both Windows and Linux will > appreciate being able to work on both platforms with a single shell. Having used both Cygwin and MKS TK shells & Gnu utils on Win in prior decades, my question would be how well does this shell integrate with windoes EXEs ? I found i Cygwin shell didn't pass WIN ENV vars through to Win EXEs but MKS had an interoperable choice at install that made scripting execution of MS's own EXEs from MKS quite practical. (Although for Office/OLE remote control, perl Win32 modules beat shell or VB.) -- Bill Ricker bill.n1vux at gmail.com https://www.linkedin.com/in/n1vux
- Follow-Ups:
- [Discuss] Windows Subsystem for Linux
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Windows Subsystem for Linux
- References:
- [Discuss] Windows Subsystem for Linux
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Windows Subsystem for Linux
- From: mark at buttery.org (Shirley Márquez Dúlcey)
- [Discuss] Windows Subsystem for Linux
- Prev by Date: [Discuss] Windows Subsystem for Linux
- Next by Date: [Discuss] Windows Subsystem for Linux
- Previous by thread: [Discuss] Windows Subsystem for Linux
- Next by thread: [Discuss] Windows Subsystem for Linux
- Index(es):