3 ms·
Well, what you said, crappy console, no ssh (the powershell equivalent is just not very good), but also, no grep (findstr is not a good substitute), no rsync, e
by joelthelion 12y ago
Well, what you said, crappy console, no ssh (the powershell equivalent is just not very good), but also, no grep (findstr is not a good substitute), no rsync, etc.
Whatever I've attempted I've always hit unexpected walls due to the unavailability of tools we take for granted with linux.
- Already__Taken 12y agoI'll parrot one of the PS developers; "grep, sed and awk etc are really great on nix because they're great with text, they're text based operating systems and you can do anything with them. Windows is an API based system so just moving text around doesn't get you very far." There's a mountain of filters available in the cmdlets parameters but specifically since you mentioned grep. findstr is not powershell it's in the old cmd family of programs still in your PATH. You want to look at select-string http://technet.microsoft.com/en-us/library/hh849903.aspx http://technet.microsoft.com/en-us/library/hh849903.aspx I wish MS would include SSH but the party line is they've no idea who really wrote the code and they won't include it in windows in case they get sued over it.