Two Months with Powershell on a Unix
code.joejag.com
Two Months with Powershell on a Unix
1–10 of 113 posts
Re: Two Months with Powershell on a Unix
#2I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux.
I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest.
Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
Re: Two Months with Powershell on a Unix
#3Dude has more patience than me. I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux. I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest. Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
If you want to do anything that would be windows only then you're right, it probably won't work.
That said, I usually have a tmux window ssh'd into a windows machine for powershell. It would be nice to be able to manage ad and exchange from a linux machine with powershell.
Re: Two Months with Powershell on a Unix
#4Dude has more patience than me. I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux. I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest. Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
Re: Two Months with Powershell on a Unix
#5Dude has more patience than me. I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux. I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest. Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
I would not invite it onto a *nix machine voluntarily where there are established patterns and solutions which have matured over the space of 40 odd years now.
Re: Two Months with Powershell on a Unix
#6Dude has more patience than me. I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux. I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest. Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
Invoke-WebRequest most certainly runs on linux.
So is creating secure strings.
Cool!
Re: Two Months with Powershell on a Unix
#7 POWERSHELL_TELEMETRY_OPTOUT=1
in your environment before launching PowerShell!Re: Two Months with Powershell on a Unix
#8Here's my notes: https://github.com/mikemaccana/powershell-profile/
Last few weeks I've been going back to bash, mainly to try out WSL/Ubuntu's defaults, but will probably move to pwsh there too. I like the consistent naming (which means I can guess commands) and avoiding the scraping that's inherent in text-only shells.
nushell looks like one to watch too. It's a lot further behind than pwsh but has a faster growing community.
Re: Two Months with Powershell on a Unix
#9That worked well enough -- exactly as on Windows, AFAICT -- but I can't imagine ever trying to replace my "daily shell" (zsh, in my case) with it.
Re: Two Months with Powershell on a Unix
#10Dude has more patience than me. I tried running powershell on linux a few times, and every single time the second command I run is not supported on linux. I don't even remember what the commands were, PSremoting was one for sure and I think another was Invoke-WebRequest. Powershell on linux is a nice idea but in the current form it is in name only, as nearly nothing works.
I’m not sure I could cope with that. I have enough problems with it on windows. Literally every corner you turn something punches you in the balls or turns to dust in your hands. It’s one of the most frustrating things I’ve ever used and I avoid it where I can. I would not invite it onto a *nix machine voluntarily where there are established patterns and solutions which have matured over the space of 40 odd years now…
In my experience with PowerShell on Windows, you have to approach it more like interactive python with shortcuts rather than a regular shell, and once you’re accustomed it works fine. The main issue is that it doesn’t work like a classic shell, it just has some affordances to look like a classic shell in common use cases.