LWN.net Weekly Edition for June 23, 2005

Changes at the Linux Mark Institute

Linux users and developers, as a whole, prefer to avoid legal and political hassles. As a result, contacts with the legal system tend to be initiated by the outside world. In the case of the Linux trademark, that contact happened in 1996, when one William Della Croce thought it would be fun to register the Linux trademark in the U.S. and start shaking down the few struggling companies which were trying to make a living in that space back then. The community reacted, lawyers were called in, and, eventually, the trademark was transferred to Linus Torvalds.

There have been occasional trademark issues since then. In 1999, a company called Channel One Gmbh made a grab for the trademark in Germany. They lost too. In early 2000, "SeriousDomains" brought about a trademark shutdown from Linus when it tried to scalp a pile of Linux-related domain names. The notion of spending big bucks for LinuxOnSteroids.com may seem amusing, but remember that things were a little different those days. Just look at the LWN Weekly Edition covering this event - the other front page story was that a company called Linuxcare thought people might want to line up and buy its stock.

Whether the domain name or the stock would be worth more now is debatable. But that event was the first episode in which the Linux trademark had been used to shut down a business in this way. In the aftermath, Linus posted an informal trademark policy to explain how he thought the mark should be used:

At that time, Linus noted that official permission to use the trademark would involve the payment of a "nominal fee," which would go to Linux International's "trademark fund."

That is where things sat for a long time. Companies using the Linux mark were expected to obtain a license for a one-time $500 fee. More recently, however, some changes have popped up which shine a light on a shift in how the trademark is being administered.

Changes at LMI

The headquarters for Linux trademark administration is, as it has been for some years, the Linux Mark Institute (LMI). It should come as no surprise that Linux International is no longer handling the trademark. What might surprise some people, however is that LMI has been reincorporated in Oregon and its web server is now hosted by OSDL. Even more surprising might be changes made to the licensing agreement for the trademark itself. None of these changes have been announced to the community.

The following table highlights a couple of key differences between the current version of the license, and the license as it appeared last October, thanks to archive.org.

October, 2004	June, 2005
LMI hereby grants to Licensee a non-exclusive sublicense to use the Linux mark and goodwill, in the form listed in the Licensee information at the end of this License form, for the purpose of marketing and distributing software that relates to the Linux operating system, whether it is an application or a version of the operating system itself.	LMI hereby grants to SUBLICENSEE, subject to the timely payment of applicable fees listed in Schedule A attached hereto and compliance with all other terms and conditions of this Agreement, a nonexclusive, non-transferable license and right to use the SUBLICENSED TRADEMARK solely (a) in the TERRITORY; (b) for the SUBLICENSEE MARKS identified on the signature page of this Agreement; and (c) on AUTHORIZED GOODS/SERVICES which are (i) produced by or for SUBLICENSEE, and (ii) distributed under SUBLICENSEE's name.
This License is perpetual so long as Licensee complies with the terms and conditions of this License...	If SUBLICENSEE is in material breach of one or more of its obligations under this Agreement, LMI may, upon its election and in addition to any other remedies that it may have, at any time terminate this Agreement and all the rights granted hereunder by not less than thirty (30) days written notice to SUBLICENSEE specifying any such breach, unless within the period of such notice all breaches specified therein shall have been remedied. By way of example but not of limitation, a material breach includes a failure to timely pay the sublicense fees set forth in Schedule A.
One Time Single Payment Royalty. This License shall become effective only upon acceptance by LMI at its official office in Monterey, California and the receipt by LMI of a one-time license fee of Five Hundred Dollars (US $500.00), which shall be non-refundable under all circumstances.	SUBLICENSEE shall pay to LMI a periodic trademark sublicense fee as specified in Schedule A appended hereto (the due date of such payment, the "Payment Due Date").

The new license has clearly gained a great many capital letters. It also has a new "schedule A" setting out what the license will cost. The figure varies depending on the amount of revenue the licensee gains from the Linux-related products; it can be anywhere from $500 to $5000. At the low end, there is a $200 rate for non-profit companies. At the high end, the $5000 applies to each product or service using the trademark. In all cases, however, the new fee is annual - it must be paid every year, or the right to use the trademark goes away.

What has also come out is that the Institute is actively contacting companies and telling them that they need a license. In this quest, it has started to upset some members of the community; in particular, Bruce Perens received a demand that the UserLinux project purchase a trademark license. Mr. Perens does not appear to be upset about trademark licensing in general, but the terms of the new agreement are not to his liking. In particular, he objects to the terms of the license grant, which reads:

How, asks Bruce, can these terms be made to work for a project like Debian, which has little control over how its distribution is distributed? Can Debian call its product "GNU/Linux" when said product can be distributed by others, using different names?

What is really going on

LWN spent some time trying to figure out what is going on at LMI; in the process, we took up quite a bit of Jon 'maddog' Hall's and Eric Boustani's time. Eric, a member of the LMI board, has been involved with the Linux trademark since the beginning, when he helped to set up the initial licensing scheme. What Eric tells us is that, over the last year, there has been a constant effort to solidify and improve the management of the Linux trademark, with the community's interests kept firmly in mind. While the work has been ongoing, only now are the results beginning to be visible.

There were a number of problems with the previous management scheme which needed to be addressed. The number of trademark licenses issued was too small - companies simply were not buying them. The protection of the Linux trademark was spotty - it is not possible to simply create a worldwide trademark license, and the mark had not been registered in many countries. There have been abuses of the trademark (Linux-related domain names pointing to porn sites, for example) which needed to be shut down. Solidifying the Linux trademark requires bringing more resources to bear, which is being done in a couple of ways. One is the increase in licensing fees, especially for the larger companies which are making money from Linux. The other was to bring in some outside support, which has come from OSDL. So OSDL is providing hosting and some staff time to assist LMI. Eric insisted, however, that OSDL has not taken over the management of the Linux trademark, and that it has no special rights with regard to that mark.

The licensing changes are aimed at improving the situation. The old licensing fee was simply not enough to fund LMI at the level it needed to properly manage the trademark. The change in the license term is meant to address a different problem: the perpetual term of the old license gave LMI no way to terminate a license. Termination in this case is not a punitive or enforcement measure; the real problem is simply companies which go out of business or stop using a Linux-related trademark for some other reason. A renewable license allows parts of the name space to be reclaimed when they fall out of use. The one-year term also allows the license to be regularly reviewed and updated; things change quickly in the Linux community, and the legal structures need to be able to change too.

LMI was not able to talk much about the specific complaints raised by Bruce Perens. Mr. Hall has described them as "non-issues," however. He and Mr. Boustani have both said that the last thing LMI wants to do is to create difficulties for community projects. If some aspect of the licensing language does turn out to be a problem, they will find a way to change it if they can.

One thing that is worth noting is that the process by which LMI makes its decisions is opaque to the community, at best. Mr. Bourstani tells us that LMI understands this, and plans to change things. So we should see initiatives from LMI to "open things up" and give the community a larger say in how the trademark is administered. Much of the work which has happened so far has been the laying of the foundations that needed to happen first.

For the curious: the current LMI board members are: Larry Augustin, Eric Bourstani, Jon 'maddog' Hall, Linus Torvalds, and Stuart Cohen. Mr. Cohen is the CEO of OSDL; he has held a board position for a relatively short period of time.

In conclusion...

One might wonder why all of this matters. The fact is that the care of the Linux trademark is an important issue. The trademark must be held by somebody, or we run the risk of more Della Croce-style shakedown attempts. If no effort is made to protect the trademark, it may degrade into a generic term which anybody can use. This may seem like the best outcome to some, but who can doubt that it would lead to some sleazy operators distributing products called "Linux" which none of us would recognize as such?

It is to our benefit that the term "Linux" actually means something. If we want that situation to continue, then somebody must defend the trademark. So a group like the Linux Mark Institute seems like a necessary evil. LMI has not conducted itself in a manner contrary to the community's interests in the past, and it does not appear that the recent changes at LMI will be anything but good for the community. If the community is to believe that over the long term, though, LMI will have to follow through with its plans for greater openness. An organization which is truly operating in the community's interest has no reason to fear the community's participation.

Comments (13 posted)

A look at Xen

The Xen virtual machine monitor is starting to pop up all over the place, or at least in several Linux distributions. Fedora Core 4 comes with Xen packaged as part of the release. SUSE Professional 9.3 includes Xen, there's the Xenophilia Linux distribution that is based around Xen, and Xen is in Debian unstable as well. XenSource, a company founded by Xen project developers, has also been in the news, and is getting funding from Kleiner Perkins Caufield & Byers and Sevin Rosen Funds as well as technology contributions from Intel.

This seems like a good time to take a look at Xen, see what it's capable of, and where it's going. We decided to test out Xen in Fedora Core 4, and the latest release from the Xen project in the form of a live CD to see how mature Xen is. According to the Xen Quickstart guide, Xen in FC4 is based on the Xen unstable tree, so some features will be a bit rough. Users who want to test Xen without installing FC4 can download demo CDs based on Debian from the Xen website. We also spoke with XenSource's Simon Crosby, a founder of XenSource and former professor at the University of Cambridge where Xen got its start.

Xen is a "hypervisor," or virtual machine monitor, which can execute several virtual machines on a single piece of hardware. Xen isn't unique in being able to run virtual hosts -- Linux users can run virtual machines using User-Mode Linux (UML), bochs, VMware products, SWsoft's Virtuozzo and a number of other virtualization technologies.

Xen operates a bit differently, however, than UML or VMware Workstation. Xen requires that a OS be ported to run on Xen's hypervisor, rather than attempting to emulate an x86 virtual machine completely as VMware Workstation does. The Xen approach is supposed to offer superior performance -- a performance comparision between VMware Workstation, Xen, native Linux and UML is available on the Xen website -- but it means that unmodified operating systems will not run on top of Xen. Users who want to run a virtual instance of Microsoft Windows, for example, will have to look elsewhere, at least for now. Crosby said that work is being done that will allow unmodified guest OSes to run on top of Xen, but that won't be complete until some time after 3.0 is released.

Also, Xen runs only on x86 systems with 686 processors or better, though ports to x86_64 and other processors are in progress. Crosby said that IBM is working on Power5 support, HP is working on Xen on IA64 and that he believes Sun is working on a Sparc port as well. The current Xen release will run on SMP systems, but does not include SMP support for guests. However, Crosby said that work is being done in this area, and the 3.0 roadmap calls for SMP support within guest hosts as well.

In addition to allowing a system to run multiple instances of Linux, Xen also works with NetBSD and FreeBSD, so users aren't restricted to using a Linux host for running Xen. Using the Xen live CD, we ran instances of Debian with the 2.4 and 2.6 series kernels alongside instances of FreeBSD and NetBSD.

We installed the Fedora Core 4 with the default "Workstation" set of packages. Xen's packages are not installed by default so we used Yum to grab the Xen host kernel, the Xen guest kernel and support packages. Xen in FC4 still requires a great deal of manual setup. There's no point-and-click GUI interface included to allow easy creation of Xen virtual hosts, and some users might find the steps to setting up Xen to be somewhat daunting. We followed along with the Fedora+Xen Quickstart guide to install Xen and create virtual hosts, and the Xen users' manual to get started with the basic Xen utilities.

After installing the Xen0 kernel, we disabled SELinux support and restarted the host to boot into the Xen0 kernel. SELinux needs to be disabled in order to create the guest filesystems. After rebooting, we created a 2GB file to use for the filesystem and then installed the Fedora Core 4 base system using Yum. It is also possible to export block devices directly to guest domains, so users could choose to use entire partitions for Xen guest filesystems.

After creating the filesystem, and creating a configuration file for the guest system under /etc/xen, we started up the guest host. We gave the guest 128 MB of RAM on a system with 1 GB total. We then tested the system a bit by creating a network interface, installing Apache with Yum and so on. The guest and host performance seemed fine, even when we started up a second guest with the same configuration on the same machine.

Xen also includes a web-based control interface. This interface didn't work in FC4, but worked just fine with the Xen live CD. After firing up "xensv" we were able to connect to the localhost on port 8080 and perform most of the functions available via the command line using the web-based interface.

The control interface for Xen is adequate, but certainly won't be winning any awards for ease of use. Crosby acknowledged that "you have to be something of a guru to use it", but noted that Xen's is very polished in the area of stability. Indeed, we didn't run into any stability issues with Xen while testing, and it looks like it's already suitable for utility computing. Crosby noted that XenSource is running its website and other services within Xen hosts.

Another interesting feature in Xen is the ability to move Xen instances from one physical machine to another. Crosby said that it's possible to move a Xen virtual machine "so that the guest is only non-responsive to the outside world for tens of miliseconds".

Xen 3.0 is scheduled for sometime in the July time frame according to the Xen roadmap. Crosby said that 3.0 will fork "in a few weeks time", and that the Xen team was waiting on a few features from the community before forking. When 3.0 forks in July, Crosby said that the Xen team would be working with the community, partners and distributions to hammer out the bugs.

We also talked to Crosby about the direction of XenSource, and whether its future offerings would be released as open source. Crosby said that the company planned to ship some proprietary tools for use with Xen, though Xen would continue to be open source. He also said that XenSource is interested in a world where the hypervisor is "ubiquitous" and provides an ecosystem with "a whole load of opportunities for vendors to compete in, creating a big pie... and we aim to have a fair slice of that pie".

While Xen is still a little rough around the edges, it's well worth a look for users who want a free software solution for virtualization. Xen's performance seems very good, and it looks like a good solution for Linux testing and perhaps web hosting and so forth. Given the interest from investors, Intel, SUSE, Red Hat and others, it seems likely that Xen will continue to improve at a rapid pace.

Comments (13 posted)