Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sudo for Windows

devblogs.microsoft.com

Post reply on HN
Print view View original

301–310 of 439 posts

Re: Sudo for Windows

#301

Post by Sakos »

KeepFlying wrote: post #171
Sakos wrote: post #133

Earlier quoted context omitted.

You say that like Microsoft isn't an incredibly deeply dysfunctional company with absurd turf wars and conflicting interests between all the teams. You'd think it should be sufficiently integrated, but it's likely office politics made that impossible. How about be glad we got this at all as a first step, then maybe it will build momentum towards a better integrated solution?

You forgot that because of backcompat this solution will now become the unchangeable standard for years and anything more integrated will be in addition, not a replacement.

And that's OP's fault how? We often have to work with the environment and framework we have, not the one we wish we had where we could just immediately implement the best possible solution.

Re: Sudo for Windows

#302

Post by TheLoafOfBread »

herbst wrote: post #299
alpb wrote: post #286

Earlier quoted context omitted.

Unlikely. Windows is all about compatibility and that includes all the weird things accumulated in windows over the decades. There is not a real incentive to change this. Think of all the gamers, custom hardware like ATMs and commercial terminals that run on Windows. That’s a huge market.

Old windows software often runs better or only with Wine instead of recent windows versions. So if they want to keep their 'compatibility' long term, they have no choice but to to include (or worse, fork) wine.

Unless it touches hardware.

Re: Sudo for Windows

#303

Post by herbst »

TheLoafOfBread wrote: post #302
herbst wrote: post #299

Earlier quoted context omitted.

Old windows software often runs better or only with Wine instead of recent windows versions. So if they want to keep their 'compatibility' long term, they have no choice but to to include (or worse, fork) wine.

Unless it touches hardware.

It depends. I would argue getting an old scanner or printer running with no current driver is definitely much easier on Linux as well. I am not into Windows enough to have any other examples :)

Re: Sudo for Windows

#304

Post by codetrotter »

JaggedJax wrote: post #265
zadjii wrote: post #2

Yep, it's really happening. Sudo is coming to Windows. It's obviously not just a fork of the linux sudo - there's enough that's different about the permissions structure between OS's that just a straight port wouldn't make sense. But the dream of being able to run commands as admin, in the same terminal window - that's the experience we're finally bringing to users. I've been working on this for the last few months n…

The real question is, where will incidents be reported to if you're not in the sudoers file?

billg@microsoft.com

Re: Sudo for Windows

#305

Post by magicalhippo »

wvenable wrote: post #160
neurostimulant wrote: post #78

Earlier quoted context omitted.

I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.

Windows and Linux already share dozens of commandline commands with the same name and have different behaviors.

Not like it's unique to Windows. Linux and say FreeBSD are similar in this regard as well, lots of commands with same name but different behavior.

Re: Sudo for Windows

#306

Post by fransje26 »

msravi wrote: post #261

Here's hoping that "Windows 12" will be just a Window manager + Desktop running on Linux, with all existing bugs meticulously replicated to maintain backwards compatibility with Windows 95/7/8/10/11.

And you then get sudo for free! With all the command parameters you know and love. Win-win.

Re: Sudo for Windows

#307

Post by bluish29 »

t0ps0il wrote: post #181
neurostimulant wrote: post #78

Earlier quoted context omitted.

I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.

> imagine the confusion of unsuspecting users searching how to use sudo in the future. Linux users can experience this now by using sed on macOS

To be fair, you will probably be confused by using sed in general

Re: Sudo for Windows

#308

Post by Kichererbsen »

FergusArgyll wrote: post #166

Considering the way PowerShell commands go, I assume this will be: RunWithAllTheElevatedPermissionsPossible --YesEvenThose .\inthisfolder.folder\. grep : The term 'grep' is not recognized....

Sir, you're doing PowerShell wrong:

   Run-WithAllTheElevatedPermissionsPossible -YesEvenThose .\inthisfolder.folder\.
See, verb-noun. and single dash. because reasons?

Re: Sudo for Windows

#310

Post by divbzero »

jraph wrote: post #137
neurostimulant wrote: post #78

Earlier quoted context omitted.

I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.

They've done it with curl: they made an alias to their own program not supporting the same feature set and it inevitably backfired [1]. sudo is a complex program with a lot of different options [2] and as people from MS said here, it's never going to be compatible because of how Windows works differently. While I understand picking a familiar name, sudo is certainly not the only player, there's also doas. This shows…

Using sudo for a Windows program doesn’t seem as bad as using curl as an alias for Invoke-WebRequest. While the real curl can be installed and fully functional on Windows, sudo is intuitively an OS-level program that deals with OS-level access control.
Post reply on HN