Shell Speeds, Bash and PowerShell
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
What do you do in BASH to manage Windows typically... (that isn't just calling PS anyways).
Of course you are CALLING PowerShell. The question was only about calling it. Whether you have PowerShell on Linux or Bash on Linux, when you manage Windows you are just calling PowerShell.
Same as managing from one Linux box to another. That's Bash or PowerShell calling Bash or PowerShell remotely.
This whole thing in my mind was about you using solely Bash to interface with Windows and MS products and services , no PowerShell involved in any way or fashion on either end. What a god damn waste of time.
-
See this is the thing, PowerShell on Linux doesn't do Bash's job locally as well as Bash. Nor does it do Bash's job remotely as well as Bash. But the logic that no one would put PS on Linux for the former, because it sucks, should then be applied to the latter because the logic matches.
But clearly, MS is making PS for Linux and people are deploying it for some reason. The logic being provided can't be used consistently, so it can't be correct. There must be a desire for PS... either because it does something actually well. Or a hope that it will.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
This whole thing in my mind was about you using solely Bash to interface with Windows and MS products and services , no PowerShell involved in any way or fashion on either end. What a god damn waste of time.
Shells don't work that way. What we use on Linux implies nothing about what we use on Windows or vice versa. In fact, we use PowerShell from Windows to manage Bash on Linux 10,000% more than we use Bash on Windows for that.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Would you use BASH on a Linux box to get some local users from a mobile windows device and put that data into AD and set some Outlook policies in Group Policy.... whatever I didn't give much thought.
Absolutely. I talk about this all of the time. that we do specifically similar stuff to this via bash because we have found it to be dramatically simpler and faster than PowerShell. So this, 100%, this is where bash shines.
No, Bash doest directly interface natively with many MS products and services without help. You are using PowerShell or other packages to do it. This isn't what the conversation was supposed to be about, somehow you slipped that in there.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
What a god damn waste of time.
This is why I asked over and over and over why you kept stating that using PowerShell on Linux mattered. Why would we ever talk about that and mean PowerShell on Windows? That would make no sense.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
No, Bash doest directly interface natively with many MS products and services without help.
Neither does PowerShell when it is remote. Hence why you chain of logic isn't making sense. What it interfaces with has no relevance here.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
No, Bash doest directly interface natively with many MS products and services without help.
Neither does PowerShell when it is remote. Hence why you chain of logic isn't making sense. What it interfaces with has no relevance here.
Maybe it's 2am and and I've not much sleep the past week. But still, I thought I was clear in that there was Zero powershell involved when referring to using Bash instead. I think you switched things up or mixed things around just to screw with me.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
You are using PowerShell or other packages to do it. This isn't what the conversation was supposed to be about, somehow you slipped that in there.
Actually it is the only thing it can be about. Since PowerShell can't do it either. In both cases the shell on Linux has to request that a shell on Windows do something on its behalf. You kept saying that PS on Linux had advantages when calling PS on Windows to do things for it. That seemed completely crazy since ALL functionality is determined by PS on Windows. Hence why I kept asking for clarification.
So back to the beginning...
Since we've now established for everyone that PS on Linux has no advantages whatsoever.... why do you feel it is totally impossible that people want it on Linux to manage Linux rather than solely for managing Windows when you've not clarified that you understand what we all thought was assumed... that the choice of shells on X doesn't affect ability to control Y.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
But still, I thought I was clear in that there was Zero powershell involved when referring to using Bash instead. I think you switched things up or mixed things around just to screw with me.
You kept answering a question that could only make sense the one way. I'm not sure why you thought that the status of PS on Windows would be changed just because we want to use Bash on Linux.
The question keeps being... why do you feel PS on Linux has a purpose? It seems now that you've established that it has no purpose under any conditions (on Linux.) Which I don't agree with, I think it's poor but people want it because they want to use it to manage Linux.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Nobody puts PowerShell on Linux to manage only Linux. It's put there to automate MS/Windows management or to automate MS/Windows and Linux management together more efficiently from the same tool.
You kicked off with this statement. But this makes no sense given your understanding now that whatever is on Linux is just calling whatever is on Windows. Do you see how this led us into a discussion specifically about Bash on Linux controlling PS on Windows? That's the only logical place to go when this statement is where you started.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
The idea that PS is on Linux to manage Windows makes no sense to me, why would anyone do that?
And now you see why I stated this. Since both Bash and PS on Linux equally call PS on Windows, using PS on Linux for this purpose doesn't make sense on its own.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
But still, I thought I was clear in that there was Zero powershell involved when referring to using Bash instead. I think you switched things up or mixed things around just to screw with me.
You kept answering a question that could only make sense the one way. I'm not sure why you thought that the status of PS on Windows would be changed just because we want to use Bash on Linux.
The question keeps being... why do you feel PS on Linux has a purpose? It seems now that you've established that it has no purpose under any conditions (on Linux.) Which I don't agree with, I think it's poor but people want it because they want to use it to manage Linux.
Would you rather spend money on a Windows server license to run PowerShell automation, or would you rather run PowerShell automation from a Linux server for free?
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Would you rather spend money on a Windows server license to run PowerShell automation, or would you rather run PowerShell automation from a Linux server for free?
And we are back again. Why do you feel that this relates to the conversation? We are back to the same confusion. We've established that Bash and PowerShell both work from Linux to automate PS on Windows.
So do you see how there is no possible answer to your question that won't cause confusion since it is either a worthless question, or implies that, again, you think that PS on Linux does something that you aren't saying and is what I keep asking about?
So let's ask .... why are you asking this question?
-
Or to state it in the clearest way I can possibly think of....
When calling PS on Windows from Linux, what do you feel that PS on Linux does that Bash on Linux doesn't do just as well, or better?
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Nobody puts PowerShell on Linux to manage only Linux. It's put there to automate MS/Windows management or to automate MS/Windows and Linux management together more efficiently from the same tool.
You kicked off with this statement. But this makes no sense given your understanding now that whatever is on Linux is just calling whatever is on Windows. Do you see how this led us into a discussion specifically about Bash on Linux controlling PS on Windows? That's the only logical place to go when this statement is where you started.
That was in reference to what you said in the video. You said something along the lines of putting powershell on Linux just to manage Linux. I thought that's silly and responded as such.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
That was in reference to what you said in the video. You said something along the lines of putting powershell on Linux just to manage Linux. I thought that's silly and responded as such.
Yes, but it's not silly, hence the problem. You are injecting somethings that cause problems.
-
You think that using PowerShell to manage Linux is silly. It's not, there are solid reasons for it and it works fine. So making weird, confusing statements as a round about way to try to state that this is silly won't work. It just makes you not make sense. It's fine to not agree with the reasons that people have for wanting this, but acting like it isn't desired doesn't work.
-
Given the logic that you are using for point 1, it would also automatically rule out using PowerShell on Linux to manage Windows remotely for the same reason - that it is silly and not as good at it as Bash. But that you rule out one scenario based on that logic, and not the other, means that you must be holding some belief or knowledge about PS' abilities that I can't get you to state and that's what I've been asking for this entire time.
-
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
Or to state it in the clearest way I can possibly think of....
When calling PS on Windows from Linux, what do you feel that PS on Linux does that Bash on Linux doesn't do just as well, or better?
You mean running double PowerShell?
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
Or to state it in the clearest way I can possibly think of....
When calling PS on Windows from Linux, what do you feel that PS on Linux does that Bash on Linux doesn't do just as well, or better?
You mean running double PowerShell?
When managing a remote system, any remote system, there are always two shells involved minimum. One shell from which you call, and one shell to which you call. There is no way to have fewer as shells are required to present the OS from one OS to the other.
So yes, when is double PowerShell better then Bash + PowerShell?
-
And when it comes to wanting PowerShell on Linux, that's something that we at NTG really wanted. So it's not a theoretical case, it's because PS has some features that we want and don't want on Windows. But sadly, right now, PS on Linux isn't as complete as PS on Windows and we have to use Bash on Linux to call PowerShell on Windows to get as close to this as possible. It's still better than PS to PS, and better than using Windows directly, but not even close to as good as fully functional PS on Linux would be and we hope will be someday.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
You think that using PowerShell to manage Linux is silly.
That is not what I said at all. I said using PowerShell to solely manage Linux, from Linux with no other purpose is silly. That's what I meant. If I want to only manage Linux, I'll use Bash. If there are other services or software in the mix that would make running PowerShell on Linux worth it, then sure. But that was never mentioned. All you said was there was Linux, and to run PowerShell on Linux with no other purpose or reason for powershell.
