Clearly this post is too old for anyone to care about, so I'll do it just to mark the article.
While I agree with/. reader comments, I wanted to point out some other problems with the article:
Avoid the use of || and && on the command line. They are squirrely between different systems, and as some other reader pointed out, you should just run a command and see what happens. You're not in a script. Also, I am afraid of A || B && C - what happens? A and C, B and C, or just A? Operator precedence matters.
Be careful about tars. I spent 2 years managing open source, and found that while most authors correctly name a root of the extraction./my-package-1.2.3, some just put all their files in the current directory. You need to "jail" your tars carefully.
Why not do "grep 'Dec '" for that grep example, instead of invoking awk? Point is, look at your data, then decide the simplest way to handle it.
Piping cats is a loopy comment. Nobody cares. Also, the wc -l saving 0.84 seconds is loopy, as well.
If you find yourself using many backslashes to continue a line, then you should be writing a script. Actually, the best thing you can do is open a notepad-like editor and build your command line in that, then paste it to your shell window.
Now, for my tips:
Never depend on a variable being set when doing a remove. That is, NEVER do "rm -rf $SOMEPATH/*" because if SOMEPATH is not set, guess what gets removed? Uh huh.
Always back up your MBR before making serious changes to your filesystem. Do this using "dd if=/dev/hda of=mbr.bin bs=1 count=512" and ideally put it on a USB stick. It's free, takes little time, and you can always restore your MBR from a bootable Linux distro such as SysRescueCD (my fav) if you really hose things up.
Quit using CSH, like some other poster said. Use bash. It's everywhere.
Pipe error output into a file, not just stdout. Somecommand >output.txt 2>&1 will write everything including errors into output.txt. If you ignore the 2>&1 (which says, duplicate stdout and route stderr into it), you only get the normal output.
Archeologists of the future will have the opposite problem of those from today - too much data.
Case in point - I'm reading Walter Shirer's 1245 page tome on the Rise and Fall of the Third Reich. He had to sift through 10,000's of captured documents to distill the complete picture down into his book.
While the 1245 page Rise and Fall covers a period of about 40 years, the source data only covered a period of probably 25 years, and that was the era immediately preceding the information age.
Think what happens when someone wants to research the Second Gulf War for historical fact, background, and rationale. (Hint, I bet his initials won't be GWB.)
"...the only solution is to rebuild from scratch. In some cases, there really is no way to recover without nuking the systems from orbit."
Um, hello? Yes, it's me, I used to administer a small lab of about 20 IBM PC-ATs down in the engineering building at Maryland, in the early 90's, where the students of some gosh awful computer engineering operating systems class used to come in and load up custom versions of COMMAND.COM. Brilliant he/she was, the instructor that decided this was a Really Good Idea: let's teach the kiddies about TSR's, then turn them loose in the lab to do whatever they want!
Nonetheless, I learned one important lesson during my daily reinstall of each of those 20 PCs: Always Boot From A Clean Disk.
An important corrolary was, you need only replace the damaged files.
Here, over 15 years later, and we have some Microsoft chump proclaiming that a PC is irrecoverable without a total wipe. Two solutions: first, don't try recovering a PC operating system by first booting the infected operating system. Second, if you boot from a clean system, you shouldn't have to completely reinstall, just hit the ones that changed.
As an aside, has anyone else but me wondered, how truly effective is antivirus scanning that runs in realtime from the host OS it is scanning? Shouldn't you always couple so called "online scanners' with some kind of forced, whole-disk scan prior to full OS start, to be run at least every once in a while?
... after reading the opening line, I'm ROTFLMAO, SCOOMN (spitting coffee out of my nose). No kidding. I had a mouthful of coffee, now I have to clean off my monitor and keyboard.
Ultra stable... crash-free... rhetoric of the "zero defects" camp. Ooops, Service Pack 2 is ready to install, gotta run.
If you're going to let someone go who holds high computer or network credentials, please make sure you disable or terminate their access IMMEDIATELY PRIOR to informing them of your decision. Failure to do so makes the outsourcee become an insider threat.
The best security policy - although it seems cruel - is to escort someone out of the building immediately after receiving their resignation, or informing them that they are being terminated - and simultaneously disable their tokens, badges, RFID devices, company credit cards, voicemail accounts.
This story is being spun into sensationalistic crap. The story is, the fine is being levied by the SEC for, and I qtfa, "securities fraud... during the period between 1998 and 2000." I used to work for McAfee, and I want to educate the community.
All of what you know as McAfee used to be called Network Associates up until about 2004. It was formed in 1998 by a massive buy-up of various software firms, including Network General and McAfee Associates - hence the name, "Network Associates." During this reign, the CEO committed the fraudulent acts, including the channel stuffing as indicated, and was eventually fired in 2000 or 2001 for fraud. The new CEO, George Samenuk, took over and has since been credited with turning the company around, reestablishing the McAfee brand identity, focussing on the core products, cutting loose various deadwood (including, unfortunately, the research group that I worked for), and returning the company to legitimate profitability. At an all-hands (the one time Samenuk braved a visit to us research dweebs), he explained that the old regime consisted of "crooks," and that he vowed to be forthright with the SEC and do his personal best to fly straight. To my knowledge, he has done a good job of that ever since.
This fine being reported today is a result of the SEC, acting in good government swiftness, merely enforcing a punishment for deeds done in the past, under different leadership. Take this news as no indication of the current state of the company or its leadership, but view it merely as a capstone to an unfortunate period in McAfee's history.
Reminds me of the early days of the WWW, when thousands of web pages were being created per day. Nowadays, it's blogs. How about we follow the pattern and make a new blogger indexer service... "Bloogle," anyone?
Question - how did you figure all this out? I expect it must have taken at least a couple people to piece together this history.
I'm thinking that the '-r' rsync file must have not gotten erased, because they were able to tell it was an rsync file, and saw it sitting there and knew rm -f * would have picked it up as "-r" as an option.
Still, wouldn't rm -rf * also have deleted the '/-r' file? Maybe someone caught it in time to keep that around, or had a backup of the root directory (but I'm thinking not, not if the data loss caused weeks of headaches.)
Why is his prior art such a piece of crap? Having written patents before, it is beholden on the author to do a reasonable search for prior art.
Clearly, Dan is either incompetent at locating e-mail packages that do precisely what his patent claims, or he is willfully omitting them in the interest of scoring a quick patent.
Somebody ought to create a legal fund designed at shooting this crap down. Honestly.
Well, on the good side, at least my patents don't suck as badly now, comparatively.
An operating system is a rack into which device drivers and APIs are inserted. A platform is a rack into which applications are inserted.
I concede that Linux (kernel plus drivers) is not itself a platform, but most users acquire Linux through the context of a much larger distribution that is, by the article's definition, a platform. The problem is that there are too many distros all doing different things, and it's hard for a novice desktopper to pick one.
The best distro people should convene and define a single distribution standard aimed at creating distros for novice user desktop replacement. Think POSIX for apps, maybe call it DESKIX (name not taken), whereby any two DESKIX distros are guaranteed file- and service-level compatible.
The standard should require a suite of MS-compatible apps like OpenOffice, specify a boot manager and appropriate installation wizards, security using reasonable best practices, apt-get like functionality for package download and management, and should specify that all licenses ensure binaries are completely free.
Then, they should follow Firefox's model and market the bejeesus out of the standard and distros supporting the standard.
Then, and only then, will Microsoft have something to worry about.
These comments were taken from the HTML variation on the Call for Papers. This is what happens when you use Microsoft Word to publish anything: "all your metadata are belong to us," er, you get the point.
Of particular interest: author is Roberto Rodrigues, using software that was at one point reported as the property of the company Callaos Y Asociados CA. The acceptance letter http://www.pdos.lcs.mit.edu/scigen/rooter-acceptan ce.txt on MIT's website is signed by a Dr. Nagib Callaos.
Anyway, here are the headers in case someone wants to do further social engineering. I have contacted the hotel to verify if the conference is real or not.
Attention college students, if you read through to the end of the article you'll see that these kids don't have any means to go to college.
One way we can help as a community is to petition the heads of our local Comp Sci/EE departments and see if there's any sort of grant or scholarship they might be willing to give them.
"Gates do A good marketing job at Microsoft" if you think of the swinging things. Otherwise, "Gates does A good marketing job at Microsoft" if you consider "Gates" to be a proper noun.
Truthfully, "Poor software does A good marketing job ON Microsoft" when I enable my semantic checker.
This is a good discussion thread, and it's great we have regular stories about desktop environments (DE's). In this thread, I've learned what other DE's people use, how they feel about them, where to get them, how they compare against the others, and now have a sense of what the best ones are. I will check back later and compile a list.
On the topic, I read Pat's changelog, and my take is that the decision to drop Gnome from Slackware is more about duplicated effort than it is about absolute effort: there seem to be other folks that provide Gnome for Slackware, as indicated in the changelog.
Interesting interview. I often find myself talking in bullet points, but the way Miguel adds boldface and sublevel indents while talking - now that is an achievement.
After RTFA, (grin), and being a Vonage user, I am outraged. It's not like the article says, folks.
...filed a lawsuit against Vonage, the country's largest Internet-based telephone service provider, for failing to make clear to consumers that the company's current service does not include access to traditional emergency 9-1-1 service.
Suppose I'm interested in signing up for Vonage. I go to vonage.com, click on "Basic 500 plan." On the main page, it says, "Does Vonage offer a 911 Dialing emergency type of dialing service?
Yes. Click here to learn more. " Clicking on the link takes me to a page where the first sentence reads, "Vonage offers 911 Dialing to all customers. When you dial 911, your call is routed from the Vonage network to the Public Safety Answering Point (PSAP) for your area." Just below it, in bright yellow-orange letters, a message clearly states, "You Must Tell Us the Physical Location of Your Vonage Line for 911 Dialing to Function."
When consumers purchase the plan over the phone, call center salespeople also fail to disclose this important information...
Okay, so 2 weeks later, I sign up for Vonage by phone. My phone rep tells me about 911. Of course, YMMV, but the burden of proof is going to be unfortunately on Vonage via policies to its employees.
Even after signing up, there are limitations to the service that Vonage customers may never know about unless they read the fine print buried on the company's Web site.
After signing up, I log in, and get a dashboard. Granted, nothing about 911 shows on the dashboard. When I click on "Features," however, which is where you go to set up call forwarding, voicemail, network outage fallback number (strangely called Network Availability Number), Right There In A Bold Red Box, It Says "911 Dialing is NOT automatic. You must activate 911 Dialing for each number on your account."
This is hardly "buried in the fine print."
...[Vonage] fails to make clear that when a customer signs up for Vonage's service, the customer does not automatically have the ability to dial 9-1-1
See above.
For example, customers who dial 9-1-1 through Vonage's "911 dialing" service are routed through administrative lines at 9-1-1 call centers, not directly to call-station operators who dispatch emergency vehicles. Calls outside regular business hours may not be answered. If emergency personnel do get the call, they may not be able to identify the caller's phone number and will not have information about the caller's address.
No personal experience on this one, but given the other falsehoods in the article, I find it highly suspicious. Vonage collects your address and binds it to your telephone number. When you call them, they know the registered address of the phone. Vonage claims to use that information to connect to the proper call center. In the age of call forwarding, I would hope this information is auto-routed to the call center... but then again, how many times have I keyed my account number into an automaton only to have the human ask for it all over again.
In summary, Vonage is great, it's 911 is what it is, but they certainly warn you about it, and this lawsuit is baseless.
100% correct. I got Vonage recently, and the dashboard clearly directs you to where you should go to activate 911. From the point of initially setting up the account (via customer service rep), I was informed of the 911 registration. The dashboard on the Internet page clearly directed me on where to go to set this up. I set it up, received clear confirmation to my primary e-mail address that the 911 service was set up. Man, there were warnings and "I agrees" all over the place.
They COULD NOT MAKE IT MORE CLEAR. In my opinion, they are not trying to hide behind the fact that their 911 service adds one extra hop in the mix. They are being responsible, and telling you what you can expect.
That said, we kept our landline... and used it to call 911 recently to save my dad-in-law's life...
IMHO, if you're using UNIX, you gotta learn some basic regexes backward and forward. They are used in vi, grep, stream editing, and many other text utilities. If you don't innately know some basic constructs, you will be forever asking your cubicle mate - or worse, like my cube mate, using VI and clacking out "j-j-cw-foo-enter", "j-j-cw-foo-enter", "j-j-cw-foo-enter", "j-j-cw-foo-enter",... With a tool like Regex Coach, it would make you dependent on the tool.
Slashdot Mirror
While I agree with /. reader comments, I wanted to point out some other problems with the article:
Now, for my tips:
Hope this helps.
Case in point - I'm reading Walter Shirer's 1245 page tome on the Rise and Fall of the Third Reich. He had to sift through 10,000's of captured documents to distill the complete picture down into his book.
While the 1245 page Rise and Fall covers a period of about 40 years, the source data only covered a period of probably 25 years, and that was the era immediately preceding the information age.
Think what happens when someone wants to research the Second Gulf War for historical fact, background, and rationale. (Hint, I bet his initials won't be GWB.)
Nonetheless, I learned one important lesson during my daily reinstall of each of those 20 PCs: Always Boot From A Clean Disk.
An important corrolary was, you need only replace the damaged files.
Here, over 15 years later, and we have some Microsoft chump proclaiming that a PC is irrecoverable without a total wipe. Two solutions: first, don't try recovering a PC operating system by first booting the infected operating system. Second, if you boot from a clean system, you shouldn't have to completely reinstall, just hit the ones that changed.
As an aside, has anyone else but me wondered, how truly effective is antivirus scanning that runs in realtime from the host OS it is scanning? Shouldn't you always couple so called "online scanners' with some kind of forced, whole-disk scan prior to full OS start, to be run at least every once in a while?
... after reading the opening line, I'm ROTFLMAO, SCOOMN (spitting coffee out of my nose). No kidding. I had a mouthful of coffee, now I have to clean off my monitor and keyboard.
Ultra stable... crash-free... rhetoric of the "zero defects" camp. Ooops, Service Pack 2 is ready to install, gotta run.
If you're going to let someone go who holds high computer or network credentials, please make sure you disable or terminate their access IMMEDIATELY PRIOR to informing them of your decision. Failure to do so makes the outsourcee become an insider threat.
The best security policy - although it seems cruel - is to escort someone out of the building immediately after receiving their resignation, or informing them that they are being terminated - and simultaneously disable their tokens, badges, RFID devices, company credit cards, voicemail accounts.
This story is being spun into sensationalistic crap. The story is, the fine is being levied by the SEC for, and I qtfa, "securities fraud ... during the period between 1998 and 2000." I used to work for McAfee, and I want to educate the community.
All of what you know as McAfee used to be called Network Associates up until about 2004. It was formed in 1998 by a massive buy-up of various software firms, including Network General and McAfee Associates - hence the name, "Network Associates." During this reign, the CEO committed the fraudulent acts, including the channel stuffing as indicated, and was eventually fired in 2000 or 2001 for fraud. The new CEO, George Samenuk, took over and has since been credited with turning the company around, reestablishing the McAfee brand identity, focussing on the core products, cutting loose various deadwood (including, unfortunately, the research group that I worked for), and returning the company to legitimate profitability. At an all-hands (the one time Samenuk braved a visit to us research dweebs), he explained that the old regime consisted of "crooks," and that he vowed to be forthright with the SEC and do his personal best to fly straight. To my knowledge, he has done a good job of that ever since.
This fine being reported today is a result of the SEC, acting in good government swiftness, merely enforcing a punishment for deeds done in the past, under different leadership. Take this news as no indication of the current state of the company or its leadership, but view it merely as a capstone to an unfortunate period in McAfee's history.
Reminds me of the early days of the WWW, when thousands of web pages were being created per day. Nowadays, it's blogs. How about we follow the pattern and make a new blogger indexer service... "Bloogle," anyone?
What happens if we lose control over this massive spacecraft - would it not orbit the sun, thus creating *another* thing that could smash into us?
Question - how did you figure all this out? I expect it must have taken at least a couple people to piece together this history.
I'm thinking that the '-r' rsync file must have not gotten erased, because they were able to tell it was an rsync file, and saw it sitting there and knew rm -f * would have picked it up as "-r" as an option.
Still, wouldn't rm -rf * also have deleted the '/-r' file? Maybe someone caught it in time to keep that around, or had a backup of the root directory (but I'm thinking not, not if the data loss caused weeks of headaches.)
Why is his prior art such a piece of crap? Having written patents before, it is beholden on the author to do a reasonable search for prior art.
Clearly, Dan is either incompetent at locating e-mail packages that do precisely what his patent claims, or he is willfully omitting them in the interest of scoring a quick patent.
Somebody ought to create a legal fund designed at shooting this crap down. Honestly.
Well, on the good side, at least my patents don't suck as badly now, comparatively.
The best distro people should convene and define a single distribution standard aimed at creating distros for novice user desktop replacement. Think POSIX for apps, maybe call it DESKIX (name not taken), whereby any two DESKIX distros are guaranteed file- and service-level compatible.
The standard should require a suite of MS-compatible apps like OpenOffice, specify a boot manager and appropriate installation wizards, security using reasonable best practices, apt-get like functionality for package download and management, and should specify that all licenses ensure binaries are completely free.
Then, they should follow Firefox's model and market the bejeesus out of the standard and distros supporting the standard.
Then, and only then, will Microsoft have something to worry about.
Actually, just got e-mail from the hotel... it IS a conference that is being held there.
This conference looks like total garbage. It is a shame that things like this exist only to make money. It gives conferences a bad name.
These comments were taken from the HTML variation on the Call for Papers. This is what happens when you use Microsoft Word to publish anything: "all your metadata are belong to us," er, you get the point.
n ce.txt on MIT's website is signed by a Dr. Nagib Callaos.
d >a ces>
<o:_EmailSubject dt:dt="string">Cartas de invitación y CFPs, SCI 2004...</o:_EmailSubject>u thorEmail>< !--[if gte mso 9]><xml>> l aceholderText>w serLevel>4 D" id=ieooui></object>( #ieooui) }
Of particular interest: author is Roberto Rodrigues, using software that was at one point reported as the property of the company Callaos Y Asociados CA. The acceptance letter http://www.pdos.lcs.mit.edu/scigen/rooter-accepta
Anyway, here are the headers in case someone wants to do further social engineering. I have contacted the hotel to verify if the conference is real or not.
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Author>Roberto Rodrigues</o:Author>
<o:LastAuthor>Miguel </o:LastAuthor>
<o:Revision>2</o:Revision>
<o:TotalTime>168</o:TotalTime>
<o:LastPrinted>2003-10-10T15:42:00Z</o:LastPrinte
<o:Created>2005-03-23T15:57:00Z</o:Created>
<o:LastSaved>2005-03-23T15:57:00Z</o:LastSaved>
<o:Pages>1</o:Pages>
<o:Words>4418</o:Words>
<o:Characters>24305</o:Characters>
<o:Company>Callaos Y Asociados CA</o:Company>
<o:Lines>202</o:Lines>
<o:Paragraphs>57</o:Paragraphs>
<o:CharactersWithSpaces>28666</o:CharactersWithSp
<o:Version>11.5606</o:Version>
</o:DocumentProperties>
<o:CustomDocumentProperties>
<o:_AdHocReviewCycleID dt:dt="float">1344996426</o:_AdHocReviewCycleID>
<o:_AuthorEmail dt:dt="string">robertorgontardo@hotmail.com</o:_A
<o:_AuthorEmailDisplayName dt:dt="string">Roberto Rodrigues</o:_AuthorEmailDisplayName>
<o:_ReviewingToolsShownOnce dt:dt="string"></o:_ReviewingToolsShownOnce>
</o:CustomDocumentProperties>
</xml><![endif]-->
<w:WordDocument>
<w:HyphenationZone>21</w:HyphenationZone>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowP
<w:Compatibility>
<w:SelectEntireFieldWithStartOrEnd/>
<w:UseWord2002TableStyleRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:Bro
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><!--[if !mso]><object
classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC
<style>
st1\:*{behavior:url
</style>
<![endif]-->
Attention college students, if you read through to the end of the article you'll see that these kids don't have any means to go to college.
One way we can help as a community is to petition the heads of our local Comp Sci/EE departments and see if there's any sort of grant or scholarship they might be willing to give them.
You must admit, this is an exceptional story.
Techniques such as these lose luster when it comes time to actually using them - the learning curves are too steep for the average user.
Should be,
"Gates do A good marketing job at Microsoft" if you think of the swinging things. Otherwise, "Gates does A good marketing job at Microsoft" if you consider "Gates" to be a proper noun.
Truthfully, "Poor software does A good marketing job ON Microsoft" when I enable my semantic checker.
This is a good discussion thread, and it's great we have regular stories about desktop environments (DE's). In this thread, I've learned what other DE's people use, how they feel about them, where to get them, how they compare against the others, and now have a sense of what the best ones are. I will check back later and compile a list.
On the topic, I read Pat's changelog, and my take is that the decision to drop Gnome from Slackware is more about duplicated effort than it is about absolute effort: there seem to be other folks that provide Gnome for Slackware, as indicated in the changelog.
One step closer to MovieOS. TELL me this won't show up in the next Matrix.
Interesting interview. I often find myself talking in bullet points, but the way Miguel adds boldface and sublevel indents while talking - now that is an achievement.
Suppose I'm interested in signing up for Vonage. I go to vonage.com, click on "Basic 500 plan." On the main page, it says, "Does Vonage offer a 911 Dialing emergency type of dialing service? Yes. Click here to learn more. " Clicking on the link takes me to a page where the first sentence reads, "Vonage offers 911 Dialing to all customers. When you dial 911, your call is routed from the Vonage network to the Public Safety Answering Point (PSAP) for your area." Just below it, in bright yellow-orange letters, a message clearly states, "You Must Tell Us the Physical Location of Your Vonage Line for 911 Dialing to Function."
When consumers purchase the plan over the phone, call center salespeople also fail to disclose this important information...
Okay, so 2 weeks later, I sign up for Vonage by phone. My phone rep tells me about 911. Of course, YMMV, but the burden of proof is going to be unfortunately on Vonage via policies to its employees.
Even after signing up, there are limitations to the service that Vonage customers may never know about unless they read the fine print buried on the company's Web site.
After signing up, I log in, and get a dashboard. Granted, nothing about 911 shows on the dashboard. When I click on "Features," however, which is where you go to set up call forwarding, voicemail, network outage fallback number (strangely called Network Availability Number), Right There In A Bold Red Box, It Says "911 Dialing is NOT automatic. You must activate 911 Dialing for each number on your account."
This is hardly "buried in the fine print."
See above.
For example, customers who dial 9-1-1 through Vonage's "911 dialing" service are routed through administrative lines at 9-1-1 call centers, not directly to call-station operators who dispatch emergency vehicles. Calls outside regular business hours may not be answered. If emergency personnel do get the call, they may not be able to identify the caller's phone number and will not have information about the caller's address.
No personal experience on this one, but given the other falsehoods in the article, I find it highly suspicious. Vonage collects your address and binds it to your telephone number. When you call them, they know the registered address of the phone. Vonage claims to use that information to connect to the proper call center. In the age of call forwarding, I would hope this information is auto-routed to the call center... but then again, how many times have I keyed my account number into an automaton only to have the human ask for it all over again.
In summary, Vonage is great, it's 911 is what it is, but they certainly warn you about it, and this lawsuit is baseless.
100% correct. I got Vonage recently, and the dashboard clearly directs you to where you should go to activate 911. From the point of initially setting up the account (via customer service rep), I was informed of the 911 registration. The dashboard on the Internet page clearly directed me on where to go to set this up. I set it up, received clear confirmation to my primary e-mail address that the 911 service was set up. Man, there were warnings and "I agrees" all over the place.
They COULD NOT MAKE IT MORE CLEAR. In my opinion, they are not trying to hide behind the fact that their 911 service adds one extra hop in the mix. They are being responsible, and telling you what you can expect.
That said, we kept our landline... and used it to call 911 recently to save my dad-in-law's life...
Don't you mean, Regex Crutch?
... With a tool like Regex Coach, it would make you dependent on the tool.
IMHO, if you're using UNIX, you gotta learn some basic regexes backward and forward. They are used in vi, grep, stream editing, and many other text utilities. If you don't innately know some basic constructs, you will be forever asking your cubicle mate - or worse, like my cube mate, using VI and clacking out "j-j-cw-foo-enter", "j-j-cw-foo-enter", "j-j-cw-foo-enter", "j-j-cw-foo-enter",
... or IBM offering Linux on its high-end servers, or the SE Linux initiative.