Slashdot Mirror
Windows to Have Better CLI
MickyJ writes "The command line interface to the Windows Server OS will be changed to the new Monad Shell (MSH), in a phased implementation to take place over the next three to five years. 'It will exceed what has been delivered in Linux and Unix for many years', so says Bob Muglia, a Senior VP at Microsoft." More from the Tom's Hardware article: "The language in Muglia's comment offers the first clear indication that WMI may be yet one more component being left behind, as Microsoft moves away from portions of Windows architecture that have historically been vulnerable to malicious attack."
Unix have no Monads.
Gr@ve_Rose
!ekoj on si aixelsyD
"The language in Muglia's comment offers the first clear indication that WMI may be yet one more component being left behind, as Microsoft moves away from portions of Windows architecture that have historically been vulnerable to malicious attack."
1. Write complex management interface
2. Shore up security holes over many years of use and testing
3. Ditch for new immature code
4. ?
5. Profit!
If they're ditching WMI it *won't* be for security reasons.
Next Headline on Slashdot:
Microsoft Pushes Back Longhorn Until 2008 Over New CLI and Changing of "My"
Dashboard Widgets
Bah:
"...will exceed what has been delivered in Linux and Unix for many years. It will take three to five years to fully develop and deliver."
Somehow I'm not too worried.
They change their entire platforms over 2 years, and MS will spend 3-5 years changing the default shell? :p
...you just gotta go download it from here.
Weaselmancer
rediculous.
Unless I can get transparent terminals. That is what really holds back MS in the server market. I mean, how useful is a shell unless you can see through it?
And it's vera nice!
Can you say bash from cygwin?!? thought you could
Well, to me, MoSH sounds best, but hey, I'm just a metal head.
Geek used to be a four letter word. Now it's a six-figure one.
Is Microsoft going to release MS-DOS v8? I thought they claim Windows does not run over DOS since win95 :-)
Also, who here believes MSH actually stands for Microsoft Shell?
Who cares? MSH will be pronounced as "mash" and this will develop a related song for sysadmins to sing on Haloween:
I was working in the lab late one night
When my eyes beheld an eerie sight
For my server from his slab began to rise
And suddenly to my surprise
He did the MSH
He did the Microsoft MSH
The Microsoft MSH
It was a server smash
He did the MSH
It caught on in a flash
He did the MSH
He did the Microsoft MSH
Catchy, no?
More
It is interesting that they are now trying to implement a command line competitive with BASH....what year is this again?
The year is 1973. Apple Computations Inc. have just announced that they are switching to the cutting-edge Zilog Z80 architecture for their range of low-cost pocket calculators; Sony Industrial Consumer Electronics are making use of an innovative new Integrated Circuit for their Alpha-Max-3 video system which contains at least five separate transistors; the Duke Nukem Forever board-game has been given a favourable reception at the Entertaining Entertainment Exposition at the Crystal Palace, London, and now Micro-Soft-Ware are designing their new, BASIC-derived timesharing shell for competing against the burgeoning MULTICS.
Well, you did ask...
Tedious Bloggy Stuff - hooray?
Uh... don't you mean
;)
sed 's/m/g'
Thought so
Geesh.. I was thinking the other mash.. Through early morning fog I see visions of the things to be the pains that are withheld for me I realize and I can see... [chorus]: That Microsoft is clueless They bring on many changes and I can take or leave it if I please. I try to find a way to make all our systems relate without that ever-present slate but now I know that it's too late, and... [Chorus] The unix shell is hard to play I'm gonna learn it anyway The Linux card I'll someday lay so this is all I have to say. [Chorus] The only way to win is cheat And lay it down before I'm beat and to another give my seat for that's the only painless feat. [Chorus] MASH The sword of time will pierce our shells It doesn't work when it begins But as it works its way on in The pain grows stronger...watch it grin, but... [Chorus] A brave man once requested me to answer questions that are key 'can you fix my computer please' and I replied 'oh why ask me?' 'Cause Microsoft is clueless They bring on many changes and I can take or leave it if I please. ...and you can do the same thing if you choose.
-if at first you don't succeed, stay the heck away from paragliding.
(courtesy of mopslik. Original post.
The far more appropos MASH reference would be the song "suicide is painless".
A Pirate and a Puritan look the same on a balance sheet.
When it stops looking like DOS,
/dev/{h,s}d{a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s, t,u,v,w,x,y,z}". Oh well, if by "quacks" you mean "errors", yeah, it's still the same.
DOS:
cd C:\PROGRA~1
2k+ cmd.exe:
cd C:\Program Files
smelling like DOS,
Which is why you no longer have a true DOS enviroment... in case you haven't noticed, 2000 on up no longer uses DOS as it's initial bootloader. It's gone, and it's been gone for a bit.
and quacking like DOS.
Can't help you there, I'm still getting this weird error about not finding '/dev/hda' in this script I made... it doesn't seem to like "echo 000000000000 >
In literally every aspect, though, DOS has been gone for a very, very long time.
clearly they're spending the extra time and energy choosing the perfect font
Sounds like Paranoia, the RPG.
This requires RED security clearance.
What is RED security clearance and how do I get it?
Attention, User, you have requested information on a clearance level you are not authorized to know about. Please press the red button to complete your termination. Disobedience is cause for termination. Have a nice day.
bash:
echo $PATH
Monad:
Private Sub echo1_CLI(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles echo1.CLI
Try
AddHandler EchoCL1.PrintLine, AddressOf Me.PrintCL1_PrintLine
PrintLine1.Print(Sys.Init.Windows.PATH)
Catch ex As Exception
Message.Show("An error occurred while printing PATH ", _
ex.ToString())
End Try