I’m a bit late posting this (for all the people who don’t read my blog?), but PowerShell is now open source! What does this mean? Well for starters it means more community updates, and forks to this already extremely powerful scripting language for Windows. The other thing that makes this great is that, since Microsoft’s reason for going open source was because they had to rebuild PowerShell to run on Nano Server, which only runs Microsoft DotNet Core, it meant that now all other systems that run DotNet Core (such as Linux and MacOS), can also run PowerShell! Or, I suppose I should say, will eventually be able to properly run PowerShell.
This is exciting news, because as a PowerShell guy, I now have become a bit more relevant in the Linux and MacOS worlds. I use a Mac and have admin’d Linux before, but my “bash” scripting is a bit less mature than my PowerShell.
I have to mention though, that I’ve tried PowerShell on both Linux and Mac, and there are some pieces of functionality that aren’t available yet that I use day-to-day, such as the ability to use remote PSSessions. These are coming, and I even saw a working demo of this at Ignite on an Ubuntu box (running in Azure of course).
I’m extremely pleased to see Microsoft continuing to embrace open source, and bringing something as proprietary as PowerShell to the cross-platform stage.
I ran into this issue today trying to copy a file from one of my Raspberry Pi devices (running Raspbian) to another. Turns out that its related to the space in the path. Now, I know that you can’t have spaces in Linux file names and/or paths, so I escaped it with a backslash like a good boy; however this did not help. It turns out, it also needs to be in quotes. Who knew?
Apparently this guy did: Mike’s Tech Blog
I couldn’t find anywhere to easily get in touch with him to thank him, so I’ll say it here. Thanks Mike!
Microsoft just announced that they’re pulling back in the reins for their OneDrive offerings: Read about it here.
I don’t disagree that the people using upwards of 75TB to store their Blu-ray collection, or whatever it was, were abusing the limitless storage. What I disagree with is a company using very limited instances of abuse as an excuse to remodel it’s entire offering. I agree with limiting the bottomless Office 365 plan, that probably wasn’t the best idea anyway, but to rein in current, legitimate users when you’ve already given that space, forcing them to have to pare down the data they are storing there to meet your requirements (albeit with 12 months grace to do so) is something else.
Also, Microsoft is said to be changing the free offering as well, from 15GB down to just 5GB. Can someone explain to me how someone, in a paid service, using an impressive amount of disk space, needs to have an impact on the free service? If you want to change your service offering, do it without the excuse. It’s your right to change it whenever and however you feel, but don’t try to make it about a tiny minority of your paid user base.
Anyway, I’m personally getting out of dodge until I see how this plays out. I’m going to look into moving my files into an OwnCloud solution. That way, I’m only limited to the amount of disk I have available, and I can have better control of my files and data overall.
Ever wished you could have a shell account to play with? Maybe you don’t want to install Linux on your own, or you don’t have a school or work system you get to “practice” your Linux skills on. For those who want to learn, there is SDF.org.
This is my first post on my new Blog. Keep an eye out here for updates on what’s going on in my life!