The Line That Never Widened - Cover

The Line That Never Widened

Copyright© 2026 by Alexander Winston

Chapter 8: The Second Name on the List

February through April 1996

The crate had no purchase order attached to it, which was the first thing that made Eric Langford’s morning difficult.

Receiving had called him down to the dock because nothing in the manifest matched an open Novell account, and because the packing sheet, taped under plastic to the crate’s side, was addressed in block letters to UNIXWARE CERTIFICATION. Eric read it twice, signed for it anyway, and had it rolled into the certification lab before he called Sarah Caldwell.

She found it parked beside the Compaq ProLiant system that had occupied the reference position in that lab for the better part of a year — close enough that a technician had to turn sideways to get between them. One machine had been there long enough to gather a film of dust along its intake vents. The other still had its shipping foam wedged in the front bezel. Someone had already taped a handwritten sign to the ProLiant’s bay reading REFERENCE — DO NOT RECONFIGURE, in the particular tone of a label meant for a room where nothing had ever needed saying twice before.

Sarah stood in the doorway a moment before either man noticed her, taking in exactly how little space the second chassis actually occupied against how much room the shipment would claim everywhere else in the building over the months that followed.

“Dell PowerEdge,” Eric said, reading off the second machine’s tag. “Engineering sample. There’s a formal request underneath it.”

The request came from a Dell enterprise-server engineering manager named Anne Keating, and it was thorough in a way that made its intentions plain before Sarah finished the first page. Dell’s server group had already built against the public UnixWare foundation — the released source, the published documentation — and had written its own storage and network drivers. It had adapted a proprietary hardware-management agent to the documented service interface the foundation had published after the patch dispute the previous winter. Keating asked for three things, in careful order: compatibility certification for the public UnixWare release; qualification against the complete Novell Enterprise UNIX environment, the separately licensed Novell services included; and, contingent on both, an OEM and reseller agreement permitting Dell to sell those same Novell services alongside its own hardware.

What she did not ask for was conspicuous by its absence. No request for Compaq’s source. No request for Compaq’s private test results, or the Compaq-Intel agreement, or any voice in what entered Novell’s own tree. Just the published requirements, a place in the queue, and the right to the certification mark if the system earned it. Sarah found herself reading the letter twice, the way she’d once read Karen Whitlock’s contribution statement twice, because both documents had the same quality of asking for exactly what the rules actually promised and nothing else — which made them harder to argue with than almost anything a lawyer could have drafted.

“They already have the source,” Eric said.

“Then the crate isn’t asking whether they may build it,” Sarah answered. “It’s asking whether we’ll judge what they built.”

She understood, standing in the narrow gap between the two chassis, exactly what the real question was. Refusing the shipment would not slow Dell’s UnixWare port by a single day — the permanent license had already settled that, and nothing about a formal certification request changed it. Refusing it would only prove that Novell’s publicly usable, freely redistributable foundation still had exactly one favored gate into the enterprise market, guarded by the same company that had written the rules.

Dell could have skipped that gate entirely. Nothing in the license stopped it from building its own BSD-derived distribution for the low end and selling it without asking Novell anything at all. But a homegrown UNIX meant taking on the job of developing and supporting an operating-system business for years to come, and competing for an application catalog Dell would have had to build compatibility into from nothing. Certification bought entry to a System V application market and a Novell partner ecosystem that already existed, without any of that overhead. It was, Sarah thought, the same calculation Compaq had made a year earlier, arriving from the opposite direction.


Gordon Maddix’s office held four people and the Compaq agreement, spread open across his desk beside Novell’s published certification requirements.

“Walk me through what Dell can and can’t have,” Gordon said.

Denise Fenwick had the answer ready. “The permanent license lets Dell use and redistribute the public foundation — that was never in question. It doesn’t give Dell our trademarks, our commercial support, the proprietary NDS and NCP components, or certification. We can deny certification for a technical or support failure. What we cannot do is turn certification into undisclosed exclusivity after using the opposite promise to attract every contributor and customer we have.”

“And what did Compaq actually buy?” Gordon asked. “Precisely. Not the marketing version.”

Sarah had the list from memory by now. “Continuing joint development. A weekly build exchange. Influence over what the reference platform actually requires. Coordinated hardware and UnixWare testing. Integration with their own proprietary management tools. And a twelve-to-eighteen-month lead that comes out of the separate Compaq-Intel server agreement, not out of anything Novell controls. What they didn’t buy was the right to keep every other machine off the list.”

Eric had been quiet, reading Dell’s submission again. “Whatever comes through my lab has to pass every test that applies to the capabilities it actually claims. Certification tells a customer the configuration is reliable and supported. It doesn’t hand Dell capabilities it doesn’t have.”

Gordon authorized the evaluation, then closed the folder before anyone could treat that as the end of the conversation. “You talk to Elaine Foster before that chassis sees a single formal test,” he told Sarah. “She does not learn about this from a certification bulletin. Not after everything Compaq put into getting us here.”

“And if she asks us to sit on it,” Sarah said, “quietly, until the next release cycle?”

“Then you tell her no, the same way you’d tell anyone no,” Gordon said. “But you tell her yourself, in a room, before it’s a decision instead of a courtesy.”


The call to Houston went differently than Sarah expected, and not in the direction that made it easier.

Thomas Avery took the news with the flat curiosity of an engineer encountering a new variable. Elaine Foster took it personally, in the specific way of someone who had spent real money on a bet nobody else had been willing to make. “We redirected engineering funding and market strategy,” she said, “when UnixWare was still an unproven idea inside a company that hadn’t decided whether to release it. Dell waited until the public foundation existed, until Intel’s work was underway, until Front Range had already survived as a pilot. Then it asked for the same visible certification.”

“I’m not going to tell you that’s an unreasonable complaint,” Sarah said. “It isn’t. But there’s a difference between the same certification standard and the same partnership, and I want to draw it precisely instead of arguing around it. Dell can earn a mark for a named configuration. It doesn’t get early access to what Compaq and Intel are building together, the joint roadmap, the weekly engineering relationship, your release-day readiness, or the combined support operation. The ProLiant stays the reference platform every UnixWare release and every piece of advanced server hardware gets tested against. And the Dell certification record is going to list what the system actually does — not imply parity in multiprocessing, hot-plug operation, redundancy, or recovery it hasn’t demonstrated.”

Foster proposed, without much hope in her voice, a protected window in which only Compaq could certify against new releases.

“That would be a contractual delay whose only purpose is shielding one vendor,” Denise said. “It would turn an open hardware market back into exclusivity, just with better paperwork.”

It was Avery who gave the argument its engineering shape. “If UnixWare only runs on one manufacturer’s hardware, application vendors will treat it exactly like every other hardware-bound UNIX they’ve already decided not to bet on. A second certified manufacturer grows the software market underneath us. It doesn’t hand Dell what Intel is building with us.”

“Then tell me what our advantage becomes,” Foster said, “once the second machine passes.”

“The same one it already was,” Avery said. “We’re the machine every new release runs on first. Our management integration is deepest. Our failures get reproduced fastest, because we’ve been doing it longest. Support doesn’t require two companies to argue about who owns the problem. And for the next twelve to eighteen months, we’re the only platform built around Intel’s dedicated server work — the performance and the redundancy that comes with it. That’s engineering. It doesn’t need a prohibition to be real.”

“I want the minutes to reflect that I raised the objection,” Foster said, before she let the subject go. “Not that I agreed with the outcome. That I understood it.”

“That’s a fair distinction,” Sarah said. “I’ll make sure it’s recorded that way.”

Foster let Novell proceed. She did not pretend to like it, and Sarah did not ask her to. Compaq had taken the earliest risk in this whole arrangement, and it was, Sarah thought, the plainest lesson the license had produced yet: openness charges its steepest early bill to whoever went first.


Anne Keating arrived at the certification lab with one driver engineer and a stack of documentation thick enough to need its own cart.

Eric recorded, before a single test ran, exactly what Dell was submitting: a generally available Pentium Pro server aimed at departmental and midrange workloads, making no claim to the larger processor counts, hot-plug subsystems, redundant paths, or fault-containment features that defined the Compaq reference platform. Keating did not argue the framing. She had come to be measured against a declared configuration, not against Compaq’s.

The public foundation tests went cleanly — installation, hardware discovery, multiprocessor operation under load, storage and network throughput, System V application behavior, BSD-socket compatibility, the published driver-interface conformance suite. Dell’s proprietary management agent loaded through the documented service interface without touching anything private, reporting exactly the health data the hardware actually provided. It was, Sarah noted, a quiet vindication of a decision made in a much angrier room the previous winter — and an equally quiet demonstration that Dell’s management coverage was narrower than Compaq’s.

The commercial-suite tests were harder. NDS replica activity. NCP file operations under sustained load. GroupWise message traffic. Backup verification. Database-style I/O held at saturation while the system was forced into recovery.

It failed there.

During a controlled power interruption, the machine restarted cleanly enough, but the test volume was missing writes the storage driver had already reported as complete. The directory-services stress test found its own records disagreeing with each other and refused to resume on its own.

Eric’s team traced it within a day: a reset path in Dell’s storage driver that acknowledged a cache flush before the controller had actually confirmed the write was durable. Ordinary benchmark and uptime testing had never triggered the narrow timing window that exposed it. Keating’s own engineer found the specific line before Eric’s team did, and said so out loud in the lab rather than waiting for Novell to hand it to her — a detail Eric mentioned to Sarah afterward with something close to approval.

“The same hardware passed qualification for two other operating systems,” Keating said, not quite an argument, more the sound of someone making sure the objection existed on the record before she dropped it.

“We’re certifying this configuration against what UnixWare and Novell’s services promise a customer,” Eric said. “Not against your reputation, and not against somebody else’s test.”

 
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.