The Line That Never Widened - Cover

The Line That Never Widened

Copyright© 2026 by Alexander Winston

Chapter 4: The Enterprise Decision

May through June 1995 — Novell headquarters, Provo; Compaq headquarters, Houston; joint engineering workshop

The boardroom had two futures in it before anyone said a word. The UnixWare transfer folder sat at Gordon Maddix’s elbow, closed, representing a transfer that had been stayed for the last month. Beside it, Sarah set down a thinner packet — the source audit, the license, the governance charter, the staged engineering plan, the conditional statement from Karen Whitlock and David Rosen, Avery’s letter, carrying his engineering director’s signature rather than merely Avery’s private assurances.

The room wasn’t arranged for a presentation. It was arranged for a vote. Every director’s copy of her packet already had tabs in it, and handwritten questions in margins she hadn’t written herself. Sarah had spent four months learning to read a room like this one, and what she read now was a board that had already done its homework and arrived wanting confirmation, not persuasion — which was its own kind of danger, since confirmation could run in either direction just as easily.

Helen Vance chaired the strategy committee, and she opened by taking away the only argument Sarah hadn’t had to make in weeks. “We’re not deciding whether Microsoft’s position is dangerous, Ms. Caldwell. Everyone in this room already believes that. We’re deciding which risk Novell is willing to own.” She laid out the three real choices without editorializing any of them: complete the UnixWare transfer and recover something now; keep the product proprietary and keep funding it at a level that hadn’t changed its trajectory in two years; or publish a legally cleared foundation, keep the enterprise services commercial, and fund the work required to make the combination real.

A director from finance took the third option apart first. Publish the foundation and Novell destroyed an asset before it had proven a single dollar of replacement revenue. Once it was out, there was no selling exclusivity back.

“He’s right about the mechanics,” Denise said, before Sarah could soften it for her. “The initial grant can’t be withdrawn. A future management team can stop contributing to it. It cannot reclaim what’s already released, and it cannot stop a competitor from using the same code.”

Sarah didn’t try to argue the premise. “The asset is already losing value while it’s closed — Mr. Maddix has seen the same purchase histories I have. This isn’t a plan to monetize the operating system. It’s a plan to use the operating system to expand what we sell around it. NDS, NCP, GroupWise, management, clustering, certification, support — every one of those grows if this foundation exists in more places than Novell can reach alone.”

Maddix let her finish without stepping in front of her. It was the first time in four months nobody in the room was protecting her from a question. She’d noticed, walking in, that he’d taken a seat at the side of the table rather than at its head — not distance, exactly, but a small, deliberate refusal to let anyone read his face before they’d read her answer.

The questions came fast after that, and each one wanted an operational answer, not a conviction. What stopped a competitor from taking the published foundation and simply outselling Novell with it? Nothing in the license — Novell would have to win that on integration, trusted releases, certification, and support, the same way it would have had to win it eventually against Microsoft. What happened if the BSD contacts walked away entirely? Their participation was useful, not load-bearing; the compatibility work stood on its own. What happened if Compaq walked away? The program stayed nonexclusive by design — Compaq accelerated things, it didn’t gate them, and it would get no veto for showing up first. Did any of this abandon the NetWare customers already running Novell’s network? No — NCP and NDS stayed intact, mixed-environment administration stayed a requirement, and nobody’s working servers got replaced on Novell’s schedule instead of the customer’s own.

A director near the end of the table, who hadn’t spoken yet, asked the question Sarah suspected mattered most to him personally: what happened to the people currently earning a living selling and supporting UnixWare as it existed today, once the strategy shipped. She told him the truth rather than the reassurance — some of that work moved onto the new foundation’s support and certification side, some of it didn’t survive the transition intact, and she wasn’t going to promise him a headcount number she couldn’t back up in this room.

“How long,” another director asked, “before there’s something real to ship?”

Eric answered that one himself. A narrow, bootable reference source first — cleared, honest about what it didn’t yet include. Restricted utilities and drivers replaced in waves after that. Novell’s own services ported in parallel, not bolted on afterward as an afterthought.

“And how will this board know, twelve months from now, whether the experiment is working or simply expensive?” Vance asked.

Sarah had the gates ready: a legally cleared, bootable reference tree; an independent governance body with procedures the public could actually read; NDS and NCP running as supported services on the new foundation, not merely promised for it; at least one hardware family fully certified against published tests; a small group of application and storage vendors on record; and one enterprise customer willing to run the combined system as a real pilot rather than a demonstration. She didn’t name Front Range. She’d understood that bank’s problem well enough to build half this proposal around it, but Martin Hale had committed to nothing, and she wasn’t going to borrow his name to close a board vote he hadn’t been asked about.

“You’re asking us to surrender control,” Vance said.

“Over the foundation,” Sarah answered. “So customers will trust us with everything we build above it.”


The board didn’t authorize a public release. It authorized a program, with a leash on it. The transfer of UnixWare would stay suspended for a hundred and eighty days — not abandoned, stayed, with a date attached. Funding was approved for the source audit, the replacement engineering, and the team porting Novell’s own services onto the cleared foundation. Denise was authorized to finish the license and the independent-governance charter. Formal, nonexclusive talks with Compaq and any other interested hardware vendor could proceed. A second board review would gate the first public release of any code at all. And Sarah would return — with cleared source, a signed hardware agreement, a working support model, and a credible customer pilot — or she wouldn’t, and the transfer would resume exactly where it had been stayed.

The vote wasn’t unanimous, and Sarah was glad of it in a way she hadn’t expected to be; a unanimous vote would have meant nobody in the room had actually understood what they’d just done. Two directors voted against it on the finance committee’s own numbers. Maddix voted for it, and made a point of saying, once the count was read, that the authorization belonged to Sarah now — the budget, the people, the clock, and whatever came of missing any of the milestones attached to all three.

Vance was the one who put it in words Sarah would carry into every room after this one.

“You asked us to give up control,” she said. “We’re giving you responsibility instead.”

Denise collected the transfer folder on her way out. It wasn’t merely closed this time. It was stayed, on the record, with a date recorded in the board minutes. The difference mattered more than either state of the folder looked like it should.


Compaq’s Houston office had promised Sarah, Eric, and Denise a technical meeting. What they walked into was a negotiation, with finance, support, product management, and enterprise-systems leadership all already seated. Thomas Avery was there, but he wasn’t running it. Elaine Foster was, and she set Sarah’s license down next to a projected engineering budget before anyone had finished with introductions.

“Why should Compaq spend millions making this platform reliable,” Foster asked, “if Dell can certify the same code a year later for free?”

Sarah didn’t try to make the problem disappear with exclusivity — she’d had that argument with herself back in Provo and lost it on purpose. Hardware exclusivity would narrow adoption, chase off exactly the outside contributors the foundation needed, and turn the whole thing into one more vendor-owned UNIX nobody outside that vendor had a reason to trust. What she offered instead was an advantage built entirely out of time and execution. Compaq would get the earliest engineering access to Novell’s supported distribution and its service roadmap, before anyone else saw it. Its engineers would help write the first published hardware-certification suite, not merely take a test somebody else had already designed. ProLiant would be the inaugural reference family — if it passed the same tests any other vendor could eventually take. The two companies would build one coordinated escalation path, so a customer’s problem never got to sit in the gap between a hardware help desk and an operating-system one. And Compaq would get joint launch support and channel visibility tied to actual, passed certification — not a contract that promised it regardless.

Denise drew the boundary before Foster could ask where it sat. Compaq could get confidential early access to unreleased Novell components under an ordinary development agreement. It would get no ownership stake in the public foundation, and no veto over who else eventually implemented it.

 
There is more of this chapter...
The source of this story is StoryRoom

To read the complete story you need to be logged in:
Log In or
Register for a Free account (Why register?)

Get No-Registration Temporary Access*

* Allows you 3 stories to read in 24 hours.