Slashdot Mirror
Windows 10 Gets Core Console Host Enhancements (nivot.org)
x0n writes: As of Windows 10 TH2 (10.0.1058), the core console subsystem has support for a large number of ANSI and VT100 escape sequences. This is likely to prepare for full Open SSH server/client integration, which is already underway over on github. It looks like xterm is finally coming to Windows. OpenSSH was previously announced (last year) by the very forward-looking PowerShell team. The linked article provides some context, and explains that the console host isn't the same as either cmd.exe or powershell.exe, but there is a lot of overlap in functionality.
Is it just me, or is this actually news for nerds?
So let me get this straight. Windows is getting the kind of terminal support *nix has had for nearly 50 years? Wow, I mean, how fucking innovative of MS.
Fuck fuck fuck.
The world's burning. Moped Jesus spotted on I50. Details at 11.
I can only hope you can run a native version of Bash with a set of GNU or Posix versions of the toolset, and I can send Powershell to the shithole that horrible scripting language belongs.
The world's burning. Moped Jesus spotted on I50. Details at 11.
For those of us that have no choice but to manage Windows and *nix boxes, it's a pain in the ass to have to context switch between RDP and ssh'ing. This will make our job much easier. Between all the open source software, github, and stuff like this, I love the new MS. Of course our real servers will always run FreeBSD.
This is.
Powershell has some great features and ideas. And whilst it can be great to script in, it is very long winded to just type and use in an adhoc fashion. Sure there's aliases but its still a bit tedious.
The other thing power shell needs is more social interaction and perhaps just a bit more fun. I guess it's still quite new and evolving. Bash is ancient relatively speaking.
I'd like to see stuff like figlet, write, wall, mutt natively in powershell so it becomes more of a destination than a mere dull workhorse of productivity.
I'd like to see stuff like figlet, write, wall, mutt natively in powershell so it becomes more of a destination than a mere dull workhorse of productivity.
Be patient - they have to get the keylogger working correctly first.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
DOSBox?
Microsoft stopped shipping MSDOS (via Windows Millennium Edition) a long time ago. If you've had 15 years to transition off DOS and Win16 applications that worked only via a compatibility mode of XP then I don't think you can blame MS for not giving your customers ample time to update.
Slashdot needs ones. Seriously, for a community that claims to hate FUD, the OSS types sure like spreading it when it is about the "right" groups. If you actually care about what kinds of things the telemetry communicates back at various settings, the information is all out there for you. No, SSH data isn't one of them. However I am going to imagine you don't, and this is just crap you want to fling at "the bad guys" because you can.
Also a thought for you: Your OS, by definition, has access to anything any program on the system is doing. What would stop it from looking in at any 3rd party SSH server you ran, if you think it does that?
Backwards compatibility isn't one of the important goals, and in some cases, incompatibility is the goal.
And yet the link you supplied to support this theory states that the AARD code only affected a particular beta version of the operating system. That situation was more about targeting tests than lack of backwards compatibility.
A lot of code that stopped working (for example in the change to Vista) was because the developers did things that were outside the published API and often specifically discouraged by the official documentation. Despite what a lot of people say, Microsoft does work hard to ensure backwards compatibility. I have been able to run programs written for Windows 3.1 on my Windows 7 system. It would probably work on the 32-bit version of Windows 10 too, but I haven't tested that.
And you can get a bash shell.....
SSH into windows to get a powershell? No thanks.
Pity there isn't a -1; Conspiracy Theory mod
Modding should really be happening along more than one dimension. With a nerd crowd you could easily have multiple scoring systems side-by-side. For example, a 543 might be 5 (insightful or informative), 4(funny), 3(mainstream v. conspiracy). Someone can have an insightful comment that is a bit conspiracy theorist--like most accurate comments about spying that would have been made pre-Snowden, for example.
I've been wanting Windows to get full Unix emulation, and even better, built in compiler support like a Unix box. I want to be able to test and run python scripts that will run on Unix vms on my box through pycharm without having to use a remote vm environment. Right now, it's easier to use a macbook pro. You'd think some monkey in marketing would have caught on to this fact.
Of course ntfs file permissions behave differently than Unix file permissions but I think that is reconcilable. I know there is cygwin but that's not the same, it's more effort with that, and a lot if things can't live in both worlds.
I've done a lot of neat stuff with powershell, for example I created a powershell script that gathered information about one system (using the Get-WmiObject Win32_SystemEnclosure to retrieve i.e. a computer's brand name, serial number, bios version, etc) and opened a TCP socket to feed that information to another system across the network that had a listening server which was also written in powershell.
But yeah, it totally violates the KISS principle. It's hard as fuck to look up certain information about the system because the way it's stored and retrieved is almost never intuitive (for example, you literally have to generate an XML file and then parse said file in order to get some stuff.)
It's also very hard to figure out how to do something you might not have done before, or have done very rarely, because the command names are so long that they're difficult to remember. There are shorter aliases, but they don't have any consistent naming (for example, Get-WmiObject can be shorthanded as gwmi, whereas a command like Add-PSSnapIn is shorthanded as asnp) making them also harder to remember.
I would much rather just have bash, and do that server stuff I did with tools like netcat, which although uses a separate binary, is FAR simpler than the method I used with powershell, while also having tools like dd to be able to manipulate binary blobs, and dummy block devices like /dev/zero, /dev/random, and even the ability to directly read/write to hard disks as if they were ordinary files.
If Microsoft did that, and had a good package manager for command line tools with the ability to add third-party repositories (like aptitude does) with options to compile from source (like portage does) I might actually consider using it for servers now and then. But because it doesn't, I only use it for servers either when an application requires it (as in, no Linux version available, but this is quite rare for applications meant for servers) or for active directory (also only occasionally needed.)
I've done a lot of neat stuff with powershell, for example I created a powershell script that gathered information about one system (using the Get-WmiObject Win32_SystemEnclosure to retrieve i.e. a computer's brand name, serial number, bios version, etc) and opened a TCP socket to feed that information to another system across the network that had a listening server which was also written in powershell.
You work for Microsoft on Windows 10 then?
This. I'd love the ability to provision a Windows box, toss a SSH key on it and have it ready to be managed via Ansible.
On the development side, being able to Vagrant up a Windows box as easily as I do other boxes would be nice, and make life a -lot- easier when it comes to testing. If I need to create a Windows box to make sure a certain set of Registry settings works, it would be nice to create a base box, boot it, have Vagrant provision it, and have it ready to go. Then, when I want to prove my stuff works to another developer, I point them to the repository with my Vagrantfile and provisioning scripts.
Vagrant is a wonderful tool for testing in the UNIX environment. It (pretty much) guarantees that I will have the exact same environment for testing as the developer, and if their code works in a Vagrant box, it will work in mine. I'd love to have the same ease of use on the Windows side. The closest I can come to this is a WIM image and a directory full of MSI files.
What do you mean no rhyme or reason? The basic toolset; cat, sh, mv, rm, and so forth are mnemonics. The point being to make the commands as short as possible while retaining some semblance of meaning. For me Powershell's absurdly verbose naming scheme is as good a sign as any that Microsoft has never really understood CLI work.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Not sure why anyone would care ... the whole "Windows 10 experience" is such a horrific platform to try and do any work done on ... fixing the shell is a noble step indeed, but there are so many other show stoppers on that system, that its just a drop in the ocean.
Fifteen mentions of Windows on the front page. Is this how slashot is going to re-connect with the technology sector?
They haven't. When I first tried to use PowerShell it frustrated me so much I wrote an entire article about it. Calling PowerShell a shell is a huge stretch: it's really just a strange and verbose scripting language.
When Windows NT first made an appearance all the Unix people were told your obsession with terminals is so outmoded that we haven't put support into NT.
I think the Unix guys are getting the last laugh...
The basic toolset; cat, sh, mv, rm, and so forth are mnemonics.
Funny you used those examples. Three out of the four of those work out of the box in PowerShell because MS included them as aliases. You can be as sleek and incomprehensible as you would like in PS. Nobody is stopping you.
For me Powershell's absurdly verbose naming scheme is as good a sign as any that Microsoft has never really understood CLI work.
Again... see comment re: aliases. New-Alias [alias] [cmdlet].
Having both the long name when you are trying to discover commands and shorter aliases for day to day work is convenient. I use PowerShell day in and day out at work, and there are lots of problems with it. The uniform naming convention is a strength, not handicap.
The Daddy casts sleep on the Baby. The Baby resists!
Hey, buddy, don't come crying to me when you come home one day and discover that Clippy has gone through your underwear and sock drawers, neatly folded and organized all the above, discarded the ones with holes in them, ordered replacements, and emailed you a recommendation for brands of non-chlorine bleach to get those nasty stains out of the crotch of your tighty-whities.
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!