18 ms·
Exactly. Powershell is some improvement, but still a pale imitation. Windows feels fragile, and often is when you try to do anything difficult. How to bring an
by quoderat 17y ago
Exactly. Powershell is some improvement, but still a pale imitation.
Windows feels fragile, and often is when you try to do anything difficult. How to bring an ethernet adapter down then up with a script in Windows? Very difficult, WMI calls and such.
In Linux? A line (really, a few characters) of script. Just one of the differences I've run into recently.
- jodrellblank 17y agoOh come on, WMI calls? you're just spreading FUD. Bring a network interface down: netsh interface set interface name="Local Area Connection" admin=disabled
- smanek 17y ago"sudo ifdown eth0"
- quoderat 17y agoProblem is, it doesn't work right: http://support.microsoft.com/kb/262265 http://support.microsoft.com/kb/262265
- deleted 17y ago[deleted]
- deleted 17y ago[deleted]
- jodrellblank 17y agoAnd if I picked a Linux distro from 8 years ago I'd find some bugs in it too. Use the current version of Windows, it has fewer bugs.
- quoderat 17y agoSorry, I have to use what the company provides, not what I wish the company provided. That's the real world.
- jodrellblank 17y agoBy that logic, if your company provided Windows 3.1 you would go around saying Windows has no multiuser support. Windows has an interface for doing what you asked. It had a bug / didn't work as described so they fixed it. Your company wont buy the fix, but that doesn't mean the fix doesn't exist. It means you can't take advantage of it, sure. But saying Windows doesn't support it is deliberately misrepresenting Windows to make it look bad. It's spreading FUD, and it's wrong. Plus, why did you bring WMI into this? You can't seem to do it with WMI: http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx "If you are not using DHCP, you cannot use WMI to disable a network connection". Were you just bringing WMI into it because it sounds scary and complicated and so would help shore up your FUD, or is there a way and this MSDN article is wrong? (But you can do it by scripting the shell: http://mcpmag.com/columns/article.asp?EditorialsID=619 http://mcpmag.com/columns/article.asp?EditorialsID=619 or by using Devcon to disable a hardware device from the command line: http://support.microsoft.com/kb/311272/en-us http://support.microsoft.com/kb/311272/en-us )
- deleted 17y ago[deleted]
- quoderat 17y agoIt's not FUD, and it's not wrong. It took me hours of research to do a simple down/up in Windows -- something that took me 30 seconds of research in Linux. And you yourself illustrate all the odd and very long things you have to do in Windows to do a simple down/up of the NIC, and to get it to work correctly. While in Linux, I can just do "sudo ifdown eth0" All in all, I prefer the 30 second way, versus the five hour way. By your very use of evidence, you proved my point. Cool. But didn't know about DevCon. Thanks.
- nailer 17y agoIs there a powershell cmdlet to replace netsh? I'm a *nix guy but actually think object pipelining is way better than scraping text.
- briansmith 17y agoIn Windows it is very rare to ever have to do ifdown/ifup.
- krschultz 17y agoIn linux its very rare (never) to have to dig up a floppy drive whenever you need to install onto a motherboard using AHCI.