Language Selection

English French German Italian Portuguese Spanish

For Me, It’s Linux, Not GNU/Linux

Filed under
Linux

I do not call Linux “GNU/Linux.” I am not only referring to the kernel, but the entire system, programs and all. Why? Many other people call it “GNU/Linux.” Here’s why I call Linux just Linux.

1. The FSF is a radical, activist organization. They created one of the best open source licenses, but take a moment to listen to Richard Stallman, the head of the FSF. Once you do, it becomes clear that the organization has radical political and software ambitions. Patents, and Microsoft, are “evil” in their minds, and so are other large companies such as Coca-Cola. I personally do not think Microsoft is “evil” (reflecting the views of many Ubuntu supporters), simply because the most vocal supporters of anti-Linux talk is found in the upper-management of the company.

2. The license should not determine the name of the software.

More Here




I stopped reading when..

> "1. The FSF is a radical, activist organization."

The same can be said about Microsoft, even Apple. Have you seen internal documents? Here is one from Microsoft:

http://www.groklaw.net/article.php?story=20071023002351958

" 5: Jihad

A Jihad is a road trip. in which an evangelist visits a large number of ISVs one-on-one to convince them to take some specific action. The classic Jihad is one focused on getting Tier A ISVs to commit to supporting a given technology by signing the technology’s Letter of Agreement (LOA - see above).

A Jihad focuses on the Travelling Salesman aspect of evangelism. As in sales, the purpose of the exercise is to close – to get the mark the ISV to sign on the dotted line, in pen, irrevocably. Not to get back to us later, not to talk to the wife about it, not to enter a three-day cooling-off period, but to get the ISV to sign, sign, sign.

If the start of the meeting is the first time the ISV has seen the LOA, then he’s not going to sign it at the end of the meeting. Since we’re asking for a very serious commitment, we want the ISV to give their signing serious consideration. If the ISV cannot deliver, then his committing to deliver is worse than useless – the ISV’s participation may occupy one of a limited number of available slots, keeping some other ISV from participating.

To maximize the chance of getting the ISV to sign during the Jihad visit, make sure that

— The ISV has seen the LOA at least a week before the Jihad visit

— The LOA is very clear about what exactly each side is promising to deliver, and when

— An Officer of the ISV’s corporation will be attending the meeting

— Microsoft’s Director of DRG has positioned the LOA with sufficient seriousness, in a cover letter or other communication in advance of the meeting

— You make it clear from the start that the purpose of your visit is to answer any questions that they might have, preparatory to signing the LOA while you’re there

— They understand that those who do not sign the LOA, are frozen out of all further information about the techology until it goes into public beta

— They understand (without being crude about it) that you will be making the same offer to their competitors

— You have T-shirts or other swag to give to those who sign. lt’s amazing what some people will do for a T-shirt.

There are a million tips and tricks to effective road trips, and to being a Road Warrior in general, all of which is beyond the scope of this discussion.

[…]

8: The Slog
Guerilla marketing is often a long, hard slog.

slog (sl^g) v. slogged, slogqing, slogs. –tr, To strike with heavy blows, as in boxing. -intr. 1. To walk with a slow, plodding gait. 2. To work diligently for long hours. –n. . 1. long, hard work. 2. A long, exhausting march or hike. [Orig. unknown.] -slog’ger
–American Heritage Dictionary, 1991

In the Slog, Microsoft dukes it out with the competition. MSDN and Platform marketing are the regular forces, exchanging blows with the enemy mano a mano. Evangelism should avoid formal, frontal assaults, instead focusing its efforts of hit-and-run tactics.

In the Slog, the enemy will counter-attack, trying to subvert your Tier A ISVs to their side, just as you should try to subvert their ISVs to your side. New ISVs should be sought, and directed to MSDN’s one-to- many programs. Evangelism should constantly be on the lookout for killer demos, hot young startups, major ISVs, customer testimonials, enemy-alliance-busting defections and other opportunities to demonstrate momentum for our technology. If bugs are found in our technology, or missing features are found to be critically important, then now is the time to identify and fix them. Stay engaged with the technology development team; ensure that you are a valuable resource for them, not a hectoring pest. Document all of your progress (ideally in regularly updated internal Web pages) and forward it regularly to management. If management is not aware of your progress, your successes, and your stumbling blocks, then they can’t help. (They may not help anyway, but they can’t if they don’t know what you need.)

Keep those Tier A ISVs on track to delivery! They are your strongest weapons and cannot be forgotten.

The elements of the evangelical infrastructure - conference presentations, courses, seminars, books, magazine articles, whitepapers, etc. – should start hitting the street at the start of the Slog. They should be so numerous as to push all other books off the shelf, courses out of catalogs, and presentations off the stage.

Working behind the scenes to orchestrate “independent” praise of our technology, and damnation of the enemy’s, is a key evangelism function during the Slog. “Independent” analyst’s report should be issued, praising your technology and damning the competitors (or ignoring them). “Independent” consultants should write columns and articles, give conference presentations and moderate stacked panels, all on our behalf (and setting them up as experts in the new technology, available for just $200/hour). “Independent” academic sources should be cultivated and quoted (and research money granted). “Independent” courseware providers should start profiting from their early involvement in our technology. Every possible source of leverage should be sought and turned to our advantage.

I have mentioned before the “stacked panel”. Panel discussions naturally favor alliances of relatively weak partners - our usual opposition. For example, an “unbiased” panel on OLE vs. OpenDoc would contain representatives of the backers of OLE (Microsoft) and the backers of OpenDoc (Apple, IBM, Novell, WordPerfect, OMG, etc.). Thus we find ourselves outnumbered in almost every “naturally occurring” panel debate.

A stacked panel, on the other hand, is like a stacked deck: it is packed with people who, on the face of things, should be neutral, but who are in fact strong supporters of our technology. The key to stacking a panel is being able to choose the moderator. Most conference organizers allow the moderator to select the panel, so if you can pick the moderator, you win. Since you can’t expect representatives of our competitors to speak on your behalf, you have to get the moderator to agree to having only “independent ISVs” on the panel. No one from Microsoft or any other formal backer of the competing technologies would be allowed – just ISVs who have to use this stuff in the “real world.” Sounds marvelously independent doesn’t it? In fact, it allows us to stack the panel with ISVs that back our cause. Thus, the “independent” panel ends up telling the audience that our technology beats the others hands down. Get the press to cover this panel, and you’ve got a major win on your hands.

Finding a moderator is key to setting up a stacked panel. The best sources of pliable moderators are:

— Analysts: Analysts sell out - that’s their business model. But they are very concerned that they never look like they are selling out, so that makes them very prickly to work with.

— Consultants: These guys are your best bets as moderators. Get a well-known consultant on your side early, but don’t let him publish anything blatantly pro-Microsoft. Then, get him to propose himself to the conference organizers as a moderator, whenever a panel opportunity comes up. Since he’s well-known, but apparently independent, he’ll be accepted – one less thing for the constantly-overworked conference organizer to worry about, right?

Gathering intelligence on enemy activities is critical to the success of the Slog. We need to know who their allies are and what differences exist between them and their allies (there are always sources of tension between allies), so that we can find ways to split ‘em apart. Reading the trade press, lurking on newsgroups, attending conferences, and (above all) talking to ISVs is essential to gathering this intelligence.

This is a very tough phase of evangelism. You’ll be pulled in every direction at once, randomized by short-term opportunities and action items, nagged by your Tier A ISVs and pestered by every other ISV that wants to become a Tier A. Management will want to know right now how you’re going to respond to some bogus announcement by some random ISV. Some PM over in Consumer will demand that you drop everything to go talk to an ISV in Outer Mongolia, that’s run by an old college chum of his. Competitors will make surprise announcements, lie through their teeth, and generally try to screw you just as hard as you are trying to screw them.

Of course, if you are very, very lucky, there will be no competition to your technology. But this is almost never the case. ODBC had its IDAPI, OLE had its OpenDoc, COM had its SOM, DCOM has its CORBA, MAPI had its VIM, etc., etc., etc. The existence of a Microsoft technology nearly guarantees that a competitive technology will spring into existence overnight, backed by an impromptu association of Microsoft competitors which have decided to draw yet another Line in the Sand (”If we don’t stop Microsoft here, then they are going to take over the whole world!”).

Without a competing technology to fight, you just hand everything over to MSDN, give your Tier A ISVs to PSS, and find a new technology to evangelize. But that takes most of the fun out of the game Smile

9: Final Release:

Evangelism of a given technology usually ends with the final, shipping release of that technology. One last big press event, with demos, a tradeshow, press releases, etc., is often called for, showcasing the apps that are sim-shipping and the customers that are using them. In the face of strong competition, Evangelism’s

focus may shift immediately to the next version of the same technology, however. Indeed, Phase 1 (Evangelism Starts) for version x+1 may start as soon as this Final Release of version X.

10: Critical Mass

The Slog may continue beyond the Final Release, for many months, until Critical Mass is reached. It is possible that Critical Mass will not be reached at all for Version X of a technology, such that Phases 1-9 will have to be repeated – possibly more than once – before ever reaching Critical Mass.

Critical Mass is reached when the technology starts evangelizing itself. When reviews subtract points if it’s not supported; when analysts say “great product plan, but what about [Technology Name]?”; when VC’s won’t fund a company unless it supports [Technology Name] - that’s Critical Mass. At that point, Evangelism of the technology stops, and Evangelism’s resources are applied to other technologies – or, if you’re lucky, moves into the Mopping Up phase.

11: Mopping Up

Mopping Up can be a lot of fun. In the Mopping Up phase, Evangelism’s goal is to put the final nail into the competing technology’s coffin, and bury it in the burning depths of the earth. Ideally, use of the competing technology becomes associated with mental deficiency, as in, “he believes in Santa Claus, the Easter Bunny, and OS/2.” Just keep rubbing it in, via the press, analysts, newsgroups, whatever. Make the complete failure of the competition’s technology part of the mythology of the computer industry. We want to place selection pressure on those companies and individuals that show a genetic weakness for competitors’ technologies, to make the industry increasingly resistant to such unhealthy strains, over time.

12: Victory

Some technologies continue as competitors long after they are true threats - look at OS/2, the Operating System that Refused to Die. It is always possible - however unlikely – that competitors like OpenDoc, SOM, OS/2, etc, could rise from the dead… so long as there is still development work being done on them. Therefore, final victory is reached only when the competing technology’s development team is disbanded, its offices reassigned, its marketing people promoted, etc. You have truly and finally won, when they come to interview for work at Microsoft.

Victory is sweet. Savor it. Then, find a new technology to evangelize — and get back to work Smile "

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: OSS

  • Codesmith Students Garner National Praise for Open-Source Contributions
    Reactide is an Integrated Development Environment built for React, which intends to make React development easier for Software Engineers. The project has been widely praised, amassing over 6,000 stars on GitHub.
  • Airbnb’s new open source library lets you design with React and render to Sketch
    Today, Airbnb’s design team open sourced its internal library for writing React components that easily render directly to Sketch. Instead of trying to get Sketch to export to code, the Airbnb team spent its time on the opposite — putting the paintbrush in the hands of the engineer.
  • [Older] Telecoms copying cloud providers make beeline for open source, say analysts
    The supersonic growth of Amazon Web Services and other cloud providers in the past few years owes much to open-source communities that fed them cutting-edge tech free-of-charge. Now telecom is mimicking this strategy through involvement with the Linux Foundation, according to Scott Raynovich (@rayno) (pictured, right), guest host of theCUBE, SiliconANGLE Media’s mobile live streaming studio.
  • Get a Preview of Apache IoT Projects at Upcoming ApacheCon
    The countdown until ApacheCon North America has begun. The blockbuster event will be in Miami this year and runs May 16-18. The Apache community is made up of many niche communities and ApacheCon offers something for all of them. Here, Roman Shaposhnik, Director of Open Source, Pivotal Inc., who is heading the Apache IoT track at the ApacheCon conference, gave us a sneak peek of what the Apache Internet of Things community can look forward to at the event.
  • Free Webinar on Starting a Collaborative Open Source Project
  • Oracle draws curtains on OmniOS
    With its openly stated operational remit of ‘aggressive acquisitions’ (albeit positively aggressive), Oracle is (very) arguably a firm known for buying, swallowing, acquiring those companies it decides to consume.
  • Partners Healthcare, Persistent Systems to develop open-source platform
  • Libreboot Applies to Rejoin GNU
    Last week we reported that after reorganization, Libreboot was considering rejoining GNU and was seeking input from its community to determine the amount of support it had for such a move. From reading the comments posted both on our article on FOSS Force and on Libreboot’s website, it comes as no surprise that the project’s core members feel they have the necessary consesus to proceed. Last night, FOSS Force received an email — sent jointly to us and Phoronix — letting us know of the decision. Rather than repeat what’s already been written and said on the subject (for that, follow the first link above), we’re publishing a slightly edited version of the email, which will pretty much bring everyone up to date on the situation.

Security updates and no more patches from grsecurity (without a fee)

  • Security updates for Wednesday
  • GrSecurity Kernel Patches Will No Longer Be Free To The Public
    The GrSecurity initiative that hosts various out-of-tree patches to the mainline Linux kernel in order to enhance the security will no longer be available to non-paying users. GrSecurity has been around for the better part of two decades and going back to the 2.4 kernel days. In 2015 the stable GrSecurity patches became available to only commercial customers while the testing patches had still been public. That's now changing with all GrSecurity users needing to be customers.
  • Passing the Baton: FAQ
    This change is effective today, April 26th 2017. Public test patches have been removed from the download area. 4.9 was specifically chosen as the last public release as being the latest upstream LTS kernel will help ease the community transition.
  • grsecurity - Passing the Baton
    Anyone here use grsecurity and have any thoughts about this?

Microsoft-Connected Forrester and Black Duck Continue to Smear FOSS

More Coverage of Kali Linux 2017.1 Release

  • Kali Linux 2017.1 Security OS Brings Wireless Injection Attacks to 802.11 AC
    Offensive Security, the developers of the BackTrack-derived Kali Linux open-source, security-oriented operating system announced the availability of the Kali Linux 2017.1 rolling release. Since Kali Linux become a rolling distro, the importance of such updated images was never the same, but Kali Linux 2017.1 appears to be a major release of the ethical hacking distro, adding a bunch of exciting new features and improvements to the Debian-based operating system.
  • Kali Linux 2017.1 Released With New Features | Download ISO Files And Torrents Here
    Offensive Security has updated the Kali Linux images with new features and changes. Termed Kali Linux 2017.1, this release comes with support for wireless injection attacks to 802.11ac and Nvidia CUDA GPU. You can simply update your existing installation by running few commands if you don’t wish to download the updated images from Kali repos.