Live data from Hacker News

Windows Server 2019 Includes OpenSSH

blogs.windows.com

251–260 of 296 posts

Re: Windows Server 2019 Includes OpenSSH

#251
post #216
post #169

Earlier quoted context omitted.

Well, if you're going to trot out quotes from the 80s (more precisely, 1987, Henry Spencer), you should be aware that Microsoft made and sold one of the first commercial Unixes: Xenix. And they made it in 1980, long before your quote. https://en.wikipedia.org/wiki/Xenix -> "In the mid-to-late 1980s, Xenix was the most common Unix variant, measured according to the number of machines on which it was installed.[1][2] M…

Apple successfully leveraged UNIX to develop macOS (officially UNIX) from which they developed iOS. Google successfully managed to leverage the Linux kernel (Unix-like) and Java to develop Android. Windows Phone, on the other hand, flopped.

My original comment said: "there was no market for Unix for close to 2 decades". That was hyperbole, but:

1. 1980 to 1998 for Google, 18 years -> that's awfully close to 2 decades.

2.1980 to 2001 for Apple, 21 years -> that's more than 2 decades.

So your counter examples confirm what I said.

3. Windows Phone and family failed because of marketing blunders, not because of tech. MS-DOS and Windows succeeded because of marketing prowess, not because of tech.

4. The mainstream market just wasn't ready for Unix for a long time. The biggest Unix success was Sun, for a long time, and Microsoft absolutely dwarfed Sun for most of their existence. Further proof that my statement was right.

Re: Windows Server 2019 Includes OpenSSH

#252
post #251
post #216

Earlier quoted context omitted.

Apple successfully leveraged UNIX to develop macOS (officially UNIX) from which they developed iOS. Google successfully managed to leverage the Linux kernel (Unix-like) and Java to develop Android. Windows Phone, on the other hand, flopped.

My original comment said: "there was no market for Unix for close to 2 decades". That was hyperbole, but: 1. 1980 to 1998 for Google, 18 years -> that's awfully close to 2 decades. 2.1980 to 2001 for Apple, 21 years -> that's more than 2 decades. So your counter examples confirm what I said. 3. Windows Phone and family failed because of marketing blunders, not because of tech. MS-DOS and Windows succeeded because of…

> Regarding Windows Phone: for technical reasons? Not really...

Not alone, it was also the network effect, and Microsoft's terrible reputation they gained in the end of '90s and '00s.

> 1980 to 2000

Yes, I noticed, but that isn't a representative range. If anything, what's relevant is their recent history:

1) Less proprietary software, more FOSS.

2) Data gathering is more important.

3) As the old cash cows dwindle (Windows and Office) new ones are attempted.

Re: Windows Server 2019 Includes OpenSSH

#253
post #252
post #251

Earlier quoted context omitted.

My original comment said: "there was no market for Unix for close to 2 decades". That was hyperbole, but: 1. 1980 to 1998 for Google, 18 years -> that's awfully close to 2 decades. 2.1980 to 2001 for Apple, 21 years -> that's more than 2 decades. So your counter examples confirm what I said. 3. Windows Phone and family failed because of marketing blunders, not because of tech. MS-DOS and Windows succeeded because of…

> Regarding Windows Phone: for technical reasons? Not really... Not alone, it was also the network effect, and Microsoft's terrible reputation they gained in the end of '90s and '00s. > 1980 to 2000 Yes, I noticed, but that isn't a representative range. If anything, what's relevant is their recent history: 1) Less proprietary software, more FOSS. 2) Data gathering is more important. 3) As the old cash cows dwindle (W…

I'm not sure I understand your comment, are those supposed to be criticisms of Microsoft?

Re: Windows Server 2019 Includes OpenSSH

#254
post #253
post #252

Earlier quoted context omitted.

> Regarding Windows Phone: for technical reasons? Not really... Not alone, it was also the network effect, and Microsoft's terrible reputation they gained in the end of '90s and '00s. > 1980 to 2000 Yes, I noticed, but that isn't a representative range. If anything, what's relevant is their recent history: 1) Less proprietary software, more FOSS. 2) Data gathering is more important. 3) As the old cash cows dwindle (W…

I'm not sure I understand your comment, are those supposed to be criticisms of Microsoft?

Observations, both compliments and criticisms alike. Doesn't have to be one extreme or the other.

Re: Windows Server 2019 Includes OpenSSH

#255
post #209

Earlier quoted context omitted.

If you know enough to say: > Linux is a kernel. You also know that 'Linux' is more commonly used as a description of the userspace and other common software. You are starting an unnecessary argument.

And that description is wrong. The userpsace and other common software is not necessarily tied to the Linux kernel. Case in point, this whole article is about software originally developed for OpenBSD. OpenSSH has nothing to do with Linux.

I agree that software isn't Linux specific. That doesn't prove your point or make your original post less obviously looking to start an argument where none exists.

Re: Windows Server 2019 Includes OpenSSH

#256
post #227

Earlier quoted context omitted.

What do you consider the "literal default installation"?

Every Windows Server release following 2016 RTM: https://docs.microsoft.com/en-us/windows-server/get-started/...

I think we have differing terminology. I would consider this a GUI. After all, the command prompts are running in windows. You can move them with your mouse. Other utilities (like regedit) are available, and are not command line / text-only applications.

Re: Windows Server 2019 Includes OpenSSH

#257

Earlier quoted context omitted.

They started on this in the late 2000s when I was an intern there. But there was a lot to untangle. It’s the biggest refactoring job you can imagine. A decade long effort. Back then they didn’t really understand the point of ssh though. They had a vision of remote management via .net RPC and powershell.

This makes you seem like you don't understand the point of PowerShell remoting. Passing serialised scriptblocks to the remote host, executing them, and getting serialized objects back. Meaning you can pass serialisable objects around, handle errors, the multiple output streams, etc. over the remoting connection. Because it's integrated into the language, you can pull PowerShell modules over from the remote host to th…

The mental overhead of this is much higher than the concept of “I’m logged in to this remote machine - all actions happen there”.

That’s why I can guarantee Remote Desktop has more usage than these remote rpc calls for ad-hoc work. Powershell is quite powerful but it’s features are more for programmers than users.

Because of its complexity RPC is not a replacement for ssh where you are typing commands directly to the remote machine.

Re: Windows Server 2019 Includes OpenSSH

#258

Earlier quoted context omitted.

It's almost 2019. Are we still fighting over this? OTOH, purely from my experience, MS's tools are good for managing a domain, or some computers. When you start to administer hundreds or thousands of servers, scriptability of CLI tools and pliability of text files trumps all computer automation. xCAT and Salt are two tools (that I use regularly) which are built on these properties and can manage thousands of servers…

Hell yeah we're going to fight over it. Whenever something that works is turned into something that sucks, we gotta point it out until it's no longer sucky.

I think there's a misunderstanding. I was talking about fighting over "MS vs. Linux" on the subject of administration paradigm.

Of course we should point out sucky tools regardless of its platform.

Re: Windows Server 2019 Includes OpenSSH

#259

Earlier quoted context omitted.

It's almost 2019. Are we still fighting over this? OTOH, purely from my experience, MS's tools are good for managing a domain, or some computers. When you start to administer hundreds or thousands of servers, scriptability of CLI tools and pliability of text files trumps all computer automation. xCAT and Salt are two tools (that I use regularly) which are built on these properties and can manage thousands of servers…

> scriptability of CLI tools and pliability of text files >trumps all computer automa I feel the need to sing, "You may have both.... you _may_ have both.... it's not so hard to imagine... MS even did it in certain products..."

Yes, it's technically possible. However, it's not always implemented like that. Also, in reality we don't have both, at least in my realm.

Being able to tune a system from top to bottom solely with text files is just amazing. Also, some people hate "everything is a file" philosophy, but it's the enabler of this configurability.

When I started programming Linux and saw that everything was accessible via normal file system, it was a big relief compared to W32's iceberg environment, where you cannot see everything and sometimes water is too cold to dive that deep.

Re: Windows Server 2019 Includes OpenSSH

#260

Earlier quoted context omitted.

Those cryptically named programs are scriptable, and those text files (including scripts) are easy to version and backup.

Windows servers used to have a NTBackup, which could just back up all the settings ("system state") if that was what you wanted for some reason.

Windows Server Backup doesn't do this on 2016 or 2019?
Post reply on HN