It appears that Warner Losh <imp(a)bsdimp.com> said:
Wasn't this from BSDi?
https://en.wikipedia.org/wiki/BSD/OS It wasn't a
commercial version of 386bsd, per se, but based on a porting to the PC work
Jolitz had done prior to 386BSD. They shared a common (very recent)
ancestor. And there was much drama around it all.
Yes, it was a commercial peer of the other BSD forks. I used it for
quite a while until the company was sold and refocused on embedded
applications. It wasn't hard to move to FreeBSD which is what I am
still using.
When I moved tp upstate NY in 1996, I wanted an Internet connection
for my work. So I called up the local independent telco who told me
they had just rolled out their new Internet service. Great, can I have
a T-1? Dunno, have to ask the boss.
They called back and said there was no techncial problem but nobody in
my small town had ever ordered a T-1 before so they had to get a T-1
rate added to the tariff they had on file with the state. That took
about a month, after which a guy in suspenders with a ladder showed
up, ran the two-pair wire, he and I looked at the manual for the
CSU/DSU I'd gotten, wired it up, and whaddaya know it worked. (It was
worth the wait, their price was half what Verizon would have charged
in Ithaca.)
Well, that part worked. They hadn't anticipated leased line customers
who wanted a /24 (which they just let me use, this was 30 years ago)
so they added me to their internal OSPF network. I was running BSDI
on a cheap 386 box, set everything up, and oh crud, the routing
daemon didn't work due to bugs.
I contacted BSDI and, in one of those things that would be too strange
to be fiction, we found that the guy at Cornell who'd written the open
source routing daemon now worked for BSDI and lived about 10 minutes
from me. I called him up, he sent me some patches, and everything
worked. I could not have asked for better software support.
He and I are still the local nerds which you can tell because his
car's license plate says TCP-IP and mine says IPV4.
R's,
John