The Line That Never Widened
Copyright© 2026 by Alexander Winston
Chapter 3: The Promise That Could Not Be Withdrawn
Late March through April 1995 — Novell headquarters, Provo; Walnut Creek, California; telephone meetings with outside participants
Denise Fenwick came into Sarah’s office the morning after the meeting with Maddix carrying nothing but a legal pad, and on it, in block letters that took up most of the page, one word: IRREVOCABLE.
“Do you understand what you promised in that room?” she asked, before Sarah had finished sitting down.
“That Novell can’t reclaim the code once it’s released.”
“That’s the sentence. I want to make sure you understand the rest of it.” Denise set the pad on the desk between them and started counting on her fingers. Novell could stop contributing new work to the foundation whenever it wanted. It could discontinue its own supported distribution entirely. It could sell what remained of the commercial business to someone else altogether. What it could never do, once code was out the door, was stop anyone else from maintaining it, distributing it, or building a business on top of it. A competitor could adopt the same foundation Novell had published. A hardware company could support it without Novell’s involvement at all. And no executive who came after Gordon Maddix — however he felt about any of this — would have the authority to take the grant back.
“You didn’t promise them access,” Denise said. “You promised them independence.”
“That’s the only access they’ll believe,” Sarah answered.
“Belief isn’t a legal instrument.” Denise tapped the word on the pad. “Before either of us writes a license, I need to know what Novell actually owns. Not what we think we own. What we can prove.”
The thirty-day clock had already started running.
Eric Langford put together a small team out of engineering and legal to sort the UnixWare source into four piles: code Novell clearly owned outright, code that had come across intact from the USL acquisition, third-party components governed by agreements nobody in the room had negotiated, and the enterprise services — NDS, NCP, GroupWise, clustering — that were never going to be part of any public foundation regardless of how the rest came out.
The first pass told Sarah what she’d half expected and hoped to be wrong about. The foundation she’d sketched on hotel stationery couldn’t simply be published as it stood. There were third-party utilities bundled in from vendors who’d licensed them for inclusion, not redistribution. There were development tools under agreements that predated most of the engineers now working on the product. There were hardware drivers supplied under confidentiality terms Novell had signed and never expected anyone outside Novell to inspect. There was code whose ownership records had gone soft with time — nobody could say with certainty who had written a given routine or under what terms, only that it worked. And there were pieces so tightly wound into everything around them that pulling them out meant replacing them, not simply deleting them.
Eric laid it out for her without softening any of it. A legally clean foundation was possible. It would need a published inventory of everything included, the restricted components stripped out, replacement work for whatever essential piece got removed along with them, a repeatable review process for anything anyone contributed afterward, and separate packaging to keep Novell’s licensed services clearly apart from what was actually free to take.
“If too much comes out,” he said, “what’s left might not even boot without proprietary pieces nobody outside this building has access to.”
Sarah wasn’t willing to release something that looked like generosity and functioned like a trap. “If the free version is deliberately crippled, everyone will know what we did.”
“They’ll know before the download finishes,” Eric said.
What he could deliver within thirty days was an auditable boundary for a minimal foundation — bootable, usable, and honest about its limits — along with a plan for clearing it in stages after board approval: a second wave once the confidential driver agreements had been renegotiated or replaced, a third once someone had rewritten whatever couldn’t be untangled from the components with soft ownership records. Sarah took the smaller, truthful promise over the larger one she couldn’t keep. A staged plan that admitted what it hadn’t cleared yet would survive contact with the outside world. A complete release that quietly depended on pieces nobody was allowed to see would not.
Denise’s first license draft arrived two days later, and Sarah rejected it within the hour. It let a customer look at the code and change it for their own use, but redistribution needed Novell’s separate approval, a commercial product built on it needed a Novell agreement, the license itself could be terminated if the underlying program ever ended, and nothing built from it was allowed to compete with Novell’s own certified distribution.
“This is visibility,” Sarah told her. “It isn’t independence. It’s everything Eric warned Compaq and BSD would both walk away from the moment they read past the first page.”
They rebuilt it from the rights outward instead of the restrictions inward: use for any lawful purpose, access to the source, the right to modify it, the right to redistribute it in source or compiled form, commercial use without asking Novell’s permission first, the right to build an entirely independent version if someone wanted to, and permanence — whatever was granted for a given release stayed granted for that release, forever, regardless of who ran Novell afterward. The rights to the code and Novell’s own trademarks would live in entirely separate places, so that using one never implied anything about the other.
Denise pointed out, correctly, that this meant an independent company could take the exact foundation Novell published and sell support against Novell directly, using Novell’s own engineering as the raw material.
“I know,” Sarah said.
Novell’s protection, going forward, would have to come from somewhere other than the license: the Novell Enterprise UNIX trademark, a certification mark customers could look for, the licensed services that actually made the foundation into a network — NDS, NCP, GroupWise, management, clustering — tested hardware combinations, real maintenance commitments, and support a customer’s auditors could plan around. The license protected people’s ability to participate. The trademark and the paid services identified what Novell was actually willing to stand behind.
The harder argument came over what happened to somebody else’s improvements. Denise wanted to require that anyone distributing a modified version publish those changes under the same open terms — Eric backed her on it, on the theory that nobody should get to quietly improve Novell’s own foundation and keep the result to themselves. Sarah had read enough BSD licensing material, and heard enough from Avery, to know that requirement would cost them both audiences at once. BSD’s own tradition ran the other way, and a hardware company doing proprietary engineering on top of a shared foundation wasn’t going to publish its competitive advantage because Novell’s license told it to.
She chose the more permissive model instead. Redistribution stayed allowed, without conditions attached to what came back. Copyright and attribution notices had to remain intact. Nothing in the license let anyone claim Novell’s endorsement it hadn’t given. Only work actually contributed into the common foundation itself — accepted, not merely built alongside it — had to carry the same public terms forward. Everyone else was invited, not required, to send their improvements back.
It was a real trade, and Sarah said so out loud in the room: Novell was giving up any guaranteed claim on the improvements other people made, in exchange for a foundation people would actually be willing to build on top of.
Sarah asked Margaret to set up a meeting with “the BSD organization” before she’d learned enough to know how badly that request would land. Margaret’s reply came back inside an hour, on a single line: Which one?
There wasn’t a BSD organization to negotiate with, and Sarah spent the better part of a day discovering exactly how many pieces the thing she’d been picturing as one entity was actually made of. The University of California held rights to portions of the historical code and the settlement records that had cleared it. Berkeley Software Design sold its own commercial system built from that lineage. FreeBSD and NetBSD were separate projects entirely, run by separate people, with no shared authority over each other. Beneath all of that sat individual contributors who participated through mailing lists and personal relationships that had built up over years — people whose standing came from the code they’d written, not from any title that let them speak for anyone else.
Novell could not negotiate its way into this the way it negotiated an OEM agreement, one executive across a table from another. Sarah and Denise arranged conversations instead, with people willing to talk on the explicit understanding that they represented themselves, and their own employers or projects only where they actually had standing to. Karen Whitlock, a FreeBSD contributor who’d built her reputation on networking and portability work, agreed to meet in California. So did David Rosen, an attorney and engineer at a small commercial BSD systems company outside San Jose.
The meeting, held in a rented conference room not far from where Walnut Creek CDROM ran its own BSD distribution business, started badly and stayed that way for the first twenty minutes.
To read the complete story you need to be logged in:
Log In or
Register for a Free account
(Why register?)
* Allows you 3 stories to read in 24 hours.