ChrisA wrote: Is Microsoft going to supply BASH, TCSH or any type of unix type shells? Where is a list of command line commands for core server? cmd.exe is a weak shell and unless enough cli tools are provided to make this thing really useful
Windows isn't as shell-centric as Unix is.
Philosophically, you don't generally pass around bits of data between multiple programs in Windows. Instead, you write script in VBScript, JScript, etc. and have cscript (or wscript) execute it. You get contructs and tools (string manipulation, file I/O, logging, etc.) which are more or less equivalent to what you'll get from the GNU set of tools, as well as access to a lot of neat information and functionality that the OS provides, through WMI and COM.
Microsoft has already been providing piles of Unix command-line tools for years, including tcsh and ksh. More info here:
Whether or not this stuff will be installable as part of Server Core is something MS will need to clarify someday.
That is a pretty funny comment, Warren, especially considering the fact that Core ONLY has a CLI. I call that very shell centric - no, shell dependent!
I think you should change your comment to "Windows WASN'T as shell-centric as Unix is", because that lame excuse for a CLI, CMD.exe, has been replaced by PowerShell (well, it is out there and rapidly gaining mindshare and raising HUGE expectations for the future of the windows CLI and windows automation).
God help the server team if they don't implement PowerShell, in all it's glory, on the future windows server platform (as I understand it, Core IS Longhorn Server, the next replacement for Windows Server 2003 R2).
If there is one server that needs a great CLI, it's Core.
EDIT: Of course, I assumed (somewhat incorrectly, from what I can gather) that Core is the only way that all Longhorn servers start their life. Perhaps Microsoft can be a little more informative of the targeted nature of the Core's role, which now seems to be highly security focused, and contrast that to the rest of the Longhorn family, which WILL most likely run the CLR "by default".
That said, it would make sense to include the CLR and PowerShell as options for Core, for those that would run Core in their normal environments because they don't need a UI.