Perhaps if it came with a dose of humility.
Oh, and Bash.
Perhaps if it came with a dose of humility.
Oh, and Bash.
Gosh, what did we ever do before Windows 2000? Authentication by clay tablet?
It's the egocentric nature of MS's claims, that somehow computing couldn't be done without its products, that pisses me off the most. It denies an absolute vast amount of work done in these areas for decades before derivative technologies like AD even existed
Just like how Redmondites are doubtless cheering the innovation of giving Windows admins what everyone else has had for decades. This isn't a moment for pride at Redmond, but the moment when if fully recognizds just how shabbily it treated people stuck trying to do automation on its amazingly incoherent platform.
Well, whenever it appears on Server, and by that I'm assuming our Server 2012 seats won't have it, so what this amounts to is "Shell out a bunch more money in operating systems and CALs, and we'll give you this nifty feature (which every other server grade OS has had for a couple of decades now)
What do you mean no rhyme or reason? The basic toolset; cat, sh, mv, rm, and so forth are mnemonics. The point being to make the commands as short as possible while retaining some semblance of meaning. For me Powershell's absurdly verbose naming scheme is as good a sign as any that Microsoft has never really understood CLI work.
So essentially it took until 2009 for Microsoft to even begin to admit that RPC, a few rather crappy scripting host options and RDP were inadequate, but it took them over six more years to finally implement what is pretty much the gold standard of encrypted TTY interfaces.
Maybe this is part of the turning over a new leaf, but I can't help but imagine that the next version of Microsoft's coursework will announce how innovative all of this, much as it went around declaring how innovative Powershell was, when all it really is is an overly complicated descendant of Bash, inelegant, overly verbose and unnecessarily convoluted. But yes, it is the best solution MS has ever come up with to remotely administer servers in a programmatic way.
What a bloody pity they just didn't admit their long battle against *nix was idiotic, and just implement Bash and the standard toolset. But then, I guess the obfuscation which has been so much a part of NT and its descendants' success would disappear as well.
I just hope all the Redmondites see the irony of MS sitting around for two decades declaring NT's superiority because, you know, Windows and all, and now essentially reinventing, badly in many cases, what the Unix ecosystem has had for decades.
Windows had a Telnet server, to be sure. But you had to be pretty damned careful as to which commands you used. We did play around with Cygwin's bash script running in a TTY on Windows 2000, but it was clunky and slow (like everything in Cygwin was, and maybe still is, I dropped it years ago). In the end it just wasn't a very good CLI-based management platform because 1. there was no good native pure CLI-based toolset to administer a system, 2. no good TTY based text editor, and 3. it was bloody Telnet, and unless you were going to throw everything in an encrypted tunnel, it simply wasn't secure enough for production servers.
Looks like the Redmondites are out in force with their mod points.
I just have to ask all you clever little MS types. As Microsoft moves Windows Server closer to a CLI-based operating system, what exactly is the point of Windows now, other than, I suppose Exchange?
I can only hope you can run a native version of Bash with a set of GNU or Posix versions of the toolset, and I can send Powershell to the shithole that horrible scripting language belongs.
So let me get this straight. Windows is getting the kind of terminal support *nix has had for nearly 50 years? Wow, I mean, how fucking innovative of MS.
Fuck fuck fuck.
I think being open about what is being transmitted would help. I concede that in modern operating environments, there's a lot of checking for updates and patches, and while we do run a Windows Update Server at the main office (mainly to save some bandwidth and give us more granular control over updates), many of our road warriors and people at the branch offices still have their computers being updated directly by Windows own update services. That means data on software installed is going to Microsoft's servers, but the trade off is we keep our systems up to date.
However, we have a number of government contracts that require safe storage of data, including assuring that no confidential data is transmitted to unauthorized third parties or out of the country. At that point it gets iffy, and I'm trying to put my head around whether "telemetry" data puts us at risk in the breach of contract department. Particularly now as we just got a three year extension on contract which will take us through 2019, we are preparing for large scale upgrades. We've already updated our Windows servers to 2012 R2, and are now in the process of deciding whether to go through the irritation of Windows 7 licenses, or just jump to Windows 10, which has been working fairly well in our test environment.
Microsoft needs to come clean here, and explain what exactly is being sent to their servers.
But then how do you trust the hardware? Even if I had the skill and patience to develop my own OS, I'm still putting faith in the hardware manufacturers that there aren't back doors.
There would be a few angry phone calls, some threats and Microsoft would give the corporations a huge break on license costs. Once you've invested vast amounts of cash in an infrastructure, even scandal won't shake you loose from it.
You simply need to pick a different route. Epubee and FBReader do the job for me. Even better, I actually have an unencrypted copy of the epub, just in case there is some sort of "licensing" issue.
Translation; You bought an Apple. You're going to pay and pay and pay, and then pay again. Welcome to our Hotel California ecosystem, you stupid hipster! BWAHAHAHAHAHAHA!!!!
All Androids? Really? Care to cite evidence? Or are you just making shit up
10 to the minus 6th power Movie = 1 Microfilm