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.

Comments

Ha-Ha!

[Anonymous Coward]

But for people doing serious work with Linux command-line apps

...we use a Linux operating system.

Re:Ha-Ha!

[Princeofcups]

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.

You somehow missed 30 years of embrace, extend, and extinguish.

Re:Ha-Ha!

[JoeMerchant]

Programs trapping Ctrl-C as an exception are exceptionally lazy - there should be a more "front end" way to quit. Originally Ctrl-C was just to kill, not to gracefully shut-down.

I take exception to the summary's bad automotive analogy. I'd say that removing Ctrl-C functionality is like removing the standard brake pedal, leaving the driver to read the manual to discover where alternate brake controls might be found - naturally different locations in different programs.

Re: In other news

[loftarasa]

vi mode for Excel would be a dream come true...

Breaking News - beta software has bugs

[Quarters]

It isn't an "upgrade bug" as the upgrade isn't slated for release for months.The build in question has only been released to the fast ring for Insider testing. In other words, it's only been given to those on the extreme bleeding edgeof Windows testing.Is Slashdot going to start posting articles for every minor issue in Chrome canary releases also?

Subject to the whims and bugs of Microsoft....

[QuietLagoon]

Really ... who on this planet is looking forward to running some manner of Linux emulation that is subject to the whims and bugs of Microsoft's current design and development process? Any of Microsoft's Windows Updates could cripple the very environment you would depend upon.

.
Yeah, that sounds like a success story.

Re:so they give up

[lucm]

As their revenue dwindles let this be a lesson.

Microsoft revenue has grown in a more or less linear fashion since the 90s. Doesn't stop idiots from announcing their imminent doom for over 25 years.

Amazing since market share dropped from 98% to 38%

[raymorris]

Which is amazing considering that a few years ago, 98% of people used their flagship product, Windows, while now only 38% of people do (Netcraft, 2016). They've done a really good job pivoting to maintain revenue while customers have dumped their traditional products en masse.

Re:So, they do not even get signal handling right

[Billly Gates]

Keep in mind this is in a Windows 10 beta relase which is based on a very new version of Ubuntu. THe stable one uses Ubuntu 14.04 LTS.

I am not defending MS as I had to downgrade to WIndows 8.1 as my main OS due to bugs. In my opinion if you need to use both us a VM. This is 2017 and most any newish PC in the last couple of years can run each others OS as a VM for any IT professional.

Re:So, they do not even get signal handling right

[GerryGilmore]

Did Ctrl-C break between Ubuntu releases? No? Then WTF is your point?

Re:Yes, StatCounter, not Netcraft

[Stormwatch]

The tale of Windows Phone is one of absolute hubris. Let me tell you the ways.

Microsoft thought, just by planting a guy to make Nokia move to WP, they could steal Nokia's exceedingly loyal users. But those people were not blindly loyal to the brand, they were invested in the roadmap: Symbian now, MeeGo soon. Without these, might as well go a completely different way. Especially when many were angry for the loss of MeeGo.

Ditto about carriers and app developers, who were counting on that roadmap. They had put a lot of money and work in preparing for MeeGo. The move to WP cost them a lot, so they were enraged and went with anyone but Microsoft.

The Skype acquisition didn't help either. Calls and messages for free? Carriers saw it as an existential threat. Microsoft got promoted from "those people are a headache" to "those sons of bitches are actively trying to murder us".

And WP may be decent now, but it was originally rushed. When the first Lumias came out, it was an incomplete mess without a possible upgrade. This meant lots of returned phones, a headache to retailers. So they also hated WP and discreetly guided potential buyers to a less headache-inducing alternative.

Microsoft was so sure they could buy success, they ended up stepping on everyone's toes.

Re:Not an alternative to Linux, an alternative to

[drinkypoo]

WHen running multiple VMs, and IDEs on Windows on Macbook Pro hardware -- it simply outclasses the same setup on alternatives.

[citation needed]

Apples are made out of the same chipsets as everyone else's PCs. There's no reason why they would be better at anything, especially since they are usually made with last year's hardware.