|
attn: hadji (ref: Windows IP lookups) | by bobmon | 2007-02-16 06:04:40 |
|
Threadjack! Linux CLI tools for Windows | by CynicalRyan | 2007-02-16 06:18:16 |
|
Native Unix Tools | by Nerzul | 2007-02-16 06:44:54 |
|
Did some digging | by madjo | 2007-02-16 06:53:53 |
| Hey, that is pretty sharp but it seems to be... |
by CALL-198 |
2007-02-16 09:11:46 |
...missing one of the more important componets: a bourne shell. All of these utilities seem to depend on Windows built in command interpreter which lacks a number of useful scripting constructs. Does anybody know where one could find a native shell environment (preferrably Bourne)?
awk also seems to be missing from the list. I use awk considerably -- both for scripting and on the command line. I would severly hindered on any system without it.
The one other thing that might make Windows usable for shell scripting would be the addition of some kind of /proc filesystem. Some of the files in /dev would also be handy In Unix, almost everything can be accessed as a file including information about the system through /proc. This makes it possible to write shell scripts that can interact with the system.
Taken together, these utils, along with a Bourne shell, awk, proc, and dev filesystyems, might actually make a fairly useable system. |
|
[ Reply ] |
|
Ah, I wasn't thinking. awk is listed as gawk. | by CALL-198 | 2007-02-16 09:14:30 |
|
Nevermind, I see shell now too. | by CALL-198 | 2007-02-16 09:16:07 |
|
Yes. | by CynicalRyan | 2007-02-16 09:46:14 |
|
There has got to be some way. | by CALL-198 | 2007-02-16 10:08:54 |
|
Neither do I. But I know that the device handling | by CynicalRyan | 2007-02-16 10:17:30 |
|
Doesn't Windows have a VFS equivilant... | by CALL-198 | 2007-02-16 10:54:48 |
|
only way your going to get proc is with cygwin | by Freakazoid | 2007-02-16 10:39:33 |
