I am a total noob when it comes to working with Linux. The only experience I have with Unix is in college when I used to pipe the manual of trn via the write command to unsuspecting classmates. If I remember correctly, this is how you do it.
write username | man trn
This would fill the user’s screen with a bunch of text. Always good for a laugh.
Normally, the write command informs the receiver who originated the message. I remember there was some way to hide who I was when sending the message, but have since forgotten that trick. Yep, them...
UPDATE: I could not slip the subtle beg for an MSDN subscription I surreptitiously embedded in this post past my astute readers. Many thanks to James Avery for contributing an MSDN subscription to this grateful developer. Now that I have my MSDN subscription, I say this whole VPC licensing thing is a non-issue and quit whining about it. (I joke, I joke!). In a recent post I declared that Virtual PC is a suitable answer to the lack of backwards compatibility support for Visual Studio.NET 2003. In the comments to that post Ryan Smith asks a great question surrounding the licensing issues involved. ...
I read this article recently that describes the mind frying complexity of the Windows development process. With Vista sporting around 50 million lines of code, it’s no wonder Vista suffers from delays. Quick, what does line #37,920,117 say? Microsoft has acknowledged the need to release more often (as in sometime this millenia), but that agility is difficult to achieve with the current codebase due to its immense complexity as well as Microsoft’s (stubbornly?) heroic efforts to maintain backward compatibilty. The author of the article labels this the Curse of Backward Compatibility. I don’t think anyone doubts that maintaining backwards compatibility can be...