Slashdot Mirror
Microsoft Releases PowerShell DSC For Linux
jones_supa writes: Microsoft is announcing that PowerShell Desired State Configuration (DSC) for Linux is available for download in form of RPM and DEB packages. DSC is a new management platform that provides a set of PowerShell extensions that you can use to declaratively specify how you want your software environment to be configured. You can now use the DSC platform to manage the configuration of both Windows and Linux workloads with the PowerShell interface. Microsoft says that bringing DSC to Linux is another step in the company's "broader commitment to common management of heterogeneous assets in your datacenter or the public cloud." Adds reader benjymouse: DSC is in the same space as Chef and Puppet (and others); but unlike those, Microsofts attempts to build a platform/infrastructure based on industry standards like OMI to allow DSC to configure and control both Windows, Linux and other OSes as well as network equipment like switches, etc.
Developers! Developers! Developers!
Is there ANY technical benefit of PowerShell compared to a modern shell?
Microsoft has done a lot right lately, but PowerShell isn't one of those things. It's just so ugly. PowerShell's syntax is just plain bad, like Perl's. And it still feels so much like using CMD.EXE. Then there is some stupid security setting I remember always running into whenever I want to use it. All in all, PowerShell is awful to use. Microsoft should have gone with IronPython instead for scripting that has integration with .NET.
It's been nice knowing ya. Who am I kidding, no it hasn't. I am SO glad Microsoft is bringing professional-grade software to Linux. I've suffered too long with shit developed by high school students.
It is a lot easier to embrace an "open standard" when you developed it yourself, then donated it to a consortium.
http://en.wikipedia.org/wiki/O...
It's a trap!
It's a M$ "standard".
Now Linux users can revel in the marvel that ooooozes POWER! Join the revolution!
Powershell is a shell written by programmers who have no understanding of what you want when administering a box. I remember when it surprised me the first time by being clever and inheriting the size of the console and automatically inserting a CR/LF into the lines of the files I was trying to process.... morons. Just because you can do something doesn't mean that you should, yes OO is a powerful construct but it just gets in the way of a simple scripting tool. Powershell is littered with little gems like this that make it absolutely useless. If you find yourself doing too much with a shell script rewrite it in a more powerful programming language like python, it should take you all of 30 minutes.
Instead of trying to unreliably and painfully get out the data you want with a chain of cut, sed, awk, tr on a untyped text string etc you can just get what you want from a object.
All Unix shells are text-oriented. PowerShell is unique in that it is object-oriented and represents a big leap and innovation in shells.
Honestly, this 'new microsoft' is going to be the death of the Linux community.
I miss the days when they just stared at their navel and ignored Linux/Android etc
Their 'help' and 'openness' are pissing in our pool and going to confuse new kids when they choose the path of freedom
rule 314: If it has the word 'power' in it, its not.
I'll NEVER accept anything from MS as a solution unless it is imposed.
Yes.
What the hell kind of sadist is going to manage their machines from a Linux machine running PowerShell?
"Unsupported configuration" is the first hurdle that I'd foresee, followed by just being plain, unnecessarily painful.
What does powershell has that python or perl does not have?
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Worked with PowerShell for Exchange 2007 and it's just too damn tedious(too much work for little gain), syntax obscure and just plain confusing at times, and a steep learning curve. "$_.", I mean seriously WTF! couldn't they just call it VAR or VAR$ or VAR_T? It's a good thing they didn't call it !@#$%^&. I guess it's all about selling MS books.
At this rate, we'll see MS commit stuff to Wine not long before Christmas.
I'll start a collection for all the tormented souls in Hell, as they'll need lots and lots of warm clothing as the ice age dawns upon them.
Question for religious people: where do unrepentant masochists go when they die?
Does Microsoft think there are not enough vulnerabilities in Linux?
Nice.
I only see this causing issues.
1) Windows Admins writing power shell scripts to do stuff on linux boxes
a) setting permissions to 777 because they got in the way.
b) why will it not write the file to c:\?
c) A power shell script developed and tested on Windows, then pushed out to all the servers and crashing the Linux boxes.
c) Do you really believe that a Linux admin would allow a windows Admin to run a Power Shell script as root?
2) Linux Admins being asked to manage windows servers because "You know Power Shell" (If they can get the Linux admin to manage the 300 windows servers on top of the existing 500 Linux servers he manages, it saves them headcount and $$$)
Personally I see it going the way all the other Microsoft products have gone when they release a Linux version. It gets adopted by a few windows admins that are forced to work on linux. However the Linux admins and the bulk of Linux systems will never see it or use it. It will eventually get dropped because of the bugs, memory leaks, and issues that are found in it. Those that are never fixed because they concentrate on the Windows version and ignore the Linux version.
Judging from history it is another Embrace, Extend, Extinguish attempt. Microsoft is just pulling from it's old bag of tricks.
This is pretty misleading. OMI is Microsoft's pet 'standard'. They know the politics of DMTF to get things the 'standard' rubber stamp, but it has no bearing on actual applicability to the general environment. Basically going OMI means a pretty crappy set of flaky abstraction/instrumentation has to be put on the target that doesn't actually provide any more value than the open source competitors. CIM/WBEM has long languished for lack of anyone wanting to do it, and MS is trying to force the issue by doing OMI.
XML is like violence. If it doesn't solve the problem, use more.
Powershell works that way because MS controlled the development of the vast majority of components that normal people interact with. It delivers a framework to let third parties do it 'the right way', but there's a lot of missing stuff and when you interact with the few CLI friendly executables that existed, you are right back there.
Basically, you could use 'python' as a shell and have the same benefits, complete with the awkwardness of interacting with non-python executables. In MS world, this is less disastrous because non-python executables were pretty rare anyway and they did a good job of chaining instead to .Net stuff.
XML is like violence. If it doesn't solve the problem, use more.
I hate and mistrust Microsoft as much as the next guy, but let me say this:
* Mathematics is powerful because you take two numbers and an operator and as a result you get something that you can re-use in the same fashion
* Unix is powerful because you take text files and an operator and as a result you get something that you can re-use in the same fashion
* Relational DBMSs are powerful because you take two relations and an operator and as a result you get something that you can re-use in the same fashion
* Monad Shell (now called Power Shell) is powerful because you take object streams and an operator and as a result you get something that you can re-use in the same fashion
A Monad really is something where you put (typically) a constant into a function and get out a specialised function (like, you put 5 into your Monad and out comes a function that takes an integer and returns that same thing plus five).
The Unix world has Perl Shell, Python Shell, and something that the Power Shell is a copy of, the Haskell Shell.
https://github.com/chrisdone/h...
http://www.yesodweb.com/blog/2...
Best regards,
Oliver
Other organizations have tried and failed to do this sort of thing, simply because they are superimposing their own stuff on top of the stuff that really does the work. So you either have the code complexity of code managing the tooling that is really doing the work, or the code managing the work, doing the work, and some middleware that doesn't add meaningful value, but does add complexity. Having translation layers rarely does nice things for maintenance and stability, regardless of who is doing it and what the platform is.
XML is like violence. If it doesn't solve the problem, use more.
Several years ago why would I want any Microsoft pseudo product on my Linux servers?
Not as if Linux doesn't already have a Power Shell called BASH or Bourne Again SHell for you noobs.
This is a workaround to enable (ancient) management methods to be effective in an environment that *many* people have already abandoned.
Massive, heterogeneous, "Enterprisey" deployments benefit from far more complete tools than fucking PowerShell, and nobody I want to work with wants wholesale management of *any part of the thing* through a proprietary black box.
Why do I need another utility when I can just use the proper syntax?
Oh, that's right. You can't. It's not a PowerShell script.
Systemd will integrate powershell someday
aaaaaaa
Sorry, couldn't resist.
First : Office on a Linux Variant (Android)
Second : Code Text Editor
Third : PowerShell tools
(...)
[last step] Abandon the costly development of the unsecure and buggy Windows OS and use only some new library à la Wine and a Windows-like graphics shell on a Linux Base OS
(more profit less cost)
Ceci n'est pas une Signature !
WBEM is a decades old open standard implemented by just about every major software and hardware manufacturer out there. It's shipped with just about every OS. The computer you are using right now probably has CIM implementation built in or at least available in the core OS.
The standard is managed by the Distributed Management Task Force which includes most top software firms. Here is the Java JSR-48: WBEM Services Specification and Implementation for example.
What Microsoft is giving the open-source community is a CIMON ( CIM Object Manager ) implementation. This is fully standards based and Microsoft is just donating the code. But as mentioned earlier Ubuntu and most OSes already ship with a lightweight CIMON.
Try to concatenate big files... Powershell FIRST load them in RAM before to get them concatenated... If the files are too large, the process fails. Cygwin is a better replacement in his own platform.
Comment removed based on user account deletion
Part of SCCM is the DSC for Windows servers. What this allows is to validate (ie. scan) for changes to the default build for servers, desktops, and provides integrated reporting. While there are many tools to do this, it is free from MS (minus the OS and SQL DB). If adding Linux to this is a possibility, having your compliance and reporting in one tool, which can leave you from having to run tripwire enterprise or the like due to compliance requirements, might be a win.
I am not saying it is the best thing on the planet, but if it does what the theory states, that would be a huge deal to have 1 less tool to manage to provide compliance reports.
I don't see any D/L links of the pages that are referenced, only an MSI installer.
"I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
"DSC is in the same space as Chef and Puppet (and others); but unlike those, Microsofts attempts to build a platform/infrastructure based on industry standards"
:)
That one almost snuck through
Um, no. Keep your filthy Microsoft hands off of my system. Security! Security! Security!
Select from tblFriends where interesting >= 4;
"Those who don't understand UNIX are condemned to reinvent it, poorly."
I gave up with the idea of an useful sig...
Becoming proficient with the command line can take many months (if not years).
I like to make the habit of ensuring new users to the command line are exposed to these two commands: "apropos" and "man".
"apropos" is good for jogging your memory about what command you may be looking for.
http://en.wikipedia.org/wiki/Apropos_(Unix)