Slashdot Mirror
Windows 10 Upgrade Bug Disabled Cntrl-C In Bash (infoworld.com)
An anonymous reader quotes InfoWorld:
A massive set of changes to the Windows Subsystem for Linux (WSL) was rolled into Windows Insider build 15002... If this is any hint, Microsoft's goal is nothing short of making it a credible alternative to other Linux distributions... Some of the fixes also implement functionality that wasn't available before to Linux apps in WSL, such as support for kernel memory overcommit and previously omitted network stack options. Other changes enhance integration between WSL and the rest of Windows...
[O]ne major issue in build 15002 is that Ctrl-C in a Bash session no longer works. Microsoft provided an uncommon level of detail for how this bug crept in, saying it had to do with synchronization between the Windows and Bash development teams. The next Insider build should have a fix. But for people doing serious work with Linux command-line apps, not having Ctrl-C is a little like driving a car when only the front brakes work.
[O]ne major issue in build 15002 is that Ctrl-C in a Bash session no longer works. Microsoft provided an uncommon level of detail for how this bug crept in, saying it had to do with synchronization between the Windows and Bash development teams. The next Insider build should have a fix. But for people doing serious work with Linux command-line apps, not having Ctrl-C is a little like driving a car when only the front brakes work.
Computers running OSX have substantial developer mindshare. Microsoft wants those developers using Windows PCs. Putting WSL/Bash on Windows so that it's a credible alternative to the 'nix tools available on OSX gives those developers one less reason to avoid using a Windows based OS.
How are these people thinking they are qualified to write an OS-like subsystem, let alone a full OS?
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
You know, some of us use windows since it's quite client facing. This might blow your mind. Anything either side can do to bridge the gap of best of both worlds is a good thing.
"Old man yells at systemd"
will remap the interrupt key to any thing you want. Try using DEL, as it was mapped on some Unix systems. It was only changed to ctrl-C to make it easier for DOS users moving to Linux.
My ism, it's full of beliefs.
WSL is better than cygwin. It is a lot faster and it has apt-get instead of that dreadful install wizard that cygwin has.
However, the console in windows is stuck in the 80's. It is the same DOS command prompt that we saw in windows 3.1. The terminal emulators in linux or macOS support multiple tabs, text selection that reaches the end of the line instead of a rectangular shape, split panes, your default directory is your home directory.
Now someone will raise their hand and say "PowerShell ISE". It looks promising, but at this point it is unusable because console programs cannot read input in PowerShell ISE
Until they have a console from this century, WSL is worth using only when you don't have linux or macOS available.
Check this piece on ars technica:
http://arstechnica.com/securit...
Most available satellite-based Internet remains almost as limited now as when it was introduced two decades ago. It's slow and provides users only with a unidirectional download link. But there's something about the connections that made them highly attractive to Turla members: most satellite links are unencrypted and can be intercepted by anyone within a radius of more than 600 miles. That means a connection between someone located in, say, a remote location in Africa and a satellite-based ISP can be monitored or even hijacked by an attacker.
lucm, indeed.
Microsoft has been working quite hard to make windows a good development platform for linux. Between WSL and the changes to Visual Studio it has gotten pretty easy to do writing, compiling and debugging of linux software from windows.
For me this is really important since linux has never run well on this laptop. I have optimus which means I have a dedicated gpu + integrated gpu and with windows it seamlessly switches between them and everything works. Under linux there are commands to make one or the other run but it is not remotely seamless and it is really buggy. I have also run into problems with ubuntu and fedora where an update will sometimes break x entirely where the default output gets set to the device that is not activated and then having to deal with debugging that.
I also write C++ simulation software and I have found no better IDE that VisualStudio so far. With eclipse under linux once I upgraded to an SSD I sometimes had issues to compile multiple times to compile without errors about files not being found. If I compiled from the command line that never happened. Debugging is MUCH worse in eclipse vs visual studio. The worse thing though is profiling. I have no idea what happened to it on linux since I have done linux development for almost 20 years now and we used to have some of the best profilers out there but no it seems most of them just do a horrible job. Trying to profile a program that uses shared libraries in linux mostly ends up with no, poor or inconsistent results even when the program behavior is highly consistent. I ended up trying the proprietary vtune from intel and that worked great on linux and windows.
In the end it is easier to do development on windows where all the desktop type stuff works and get the software running completely correctly and debugged and then deploy it to linux servers, clusters, supercomputers etc for actual running. At this point I pretty much use windows for desktop work and linux for all the server work and the WSL system has made life much simpler.
Computer modeling for biotech drug manufacturing is HARD!