@Carnival-Boy
There are a few things wrong with powershell but complex no. All commands are always in the form of verb-noun, and on all commands you can always use get-help to see the syntax and examples of the command. What the author fails to realize is that everything returned from the shell (even though it looks like text) is an object. It is something those unfamiliar with powershell don't understand. In that regard it is more reliable than BASH and easier to work with. Having worked in both environments - I prefer powerhsell over BASH any day. There are a few times when BASH can come to the rescue but those are far and few between. When I need to manage linux - I of course use Bash and then retreat from there as quickly as possible.Give me objects - not text.
Posts made by pdearmen
-
RE: What BASH and SSH Mean for Windows Systems Administration
-
RE: What BASH and SSH Mean for Windows Systems Administration
@Dashrender Winrm uses encryption - and uses secure kerebros authentication - its a great remote administration tool actually.
-
RE: What BASH and SSH Mean for Windows Systems Administration
Forgot to mention - the SSH subsystem will be available without needing to activate/install the linux subsystem. Again through powershell.
-
RE: What BASH and SSH Mean for Windows Systems Administration
"Windows Server continues to suffer from a culture push to use the GUI"
This is actually 100% wrong. If you talk to the server team or have installed server since 2012 r2 at all, the default option in 2012 r2 is no gui. The default in 2016 will be heavily pushed no gui. And the core technology that will be driving all the configuration of the servers?Powershell.
I agree with this statement
"This may be the move that prepares Microsoft to recycle its ecosystem, to dump the existing global pool of administrators and shake up IT bringing their own culture in line with their competition, making themselves far more viable for the world of cloud computing and removing decades of kruft that has collected around their culture and ecosystem."Except the tool that they will build all their admins on is powershell.
Have you looked at any one program from microsoft in the past few years? The exchange team has made it so you MUST use powershell. You cannot manage exchange without it. DSC is powered by powershell. Server configuration and automation - again - powershell.
Even AD tools are now powershell based.Remote management through winrm is a reality and many many admins use it. It is those admins that refuse to use it that are becoming extinct - because most people realize that doing things the old manual way is a waste of time and resources.
The linux subsystems will be great - for managing linux devices. Outside of that it's just another shell to use to interface with the hard drive. Since the bash system itself will NOT be able to interface with the rest of the system.
Oh and the SSH capabilities that were being touted about - that is a powershell feature in server 2016 (and powershell 5.1) as well.
This linux subsystem on windows will be useful in certain situations only - and only in the right environments.