Re: Quick question about multivalue history

I recall hearing that the SMI version needed a S1 to access the DB on the big iron(3xxx)? Maybe to support the dumb serial terminals which weren't native to the big iron?

Mark Brown wrote:
IIRC, SMI did a pick implementation on some heavy metal from IBM, but it wasn't S1.

CDI which became Seattle Lab did the Series/1 in 1983. Gordan Ayres, Kip McAfee, George Coleman, Mark Brown, Denis Kreuger and a great guy I can't for the life of me remember his name--we went back to General Dynamics together in '84--(sorry; and sorry if I misspelled anyone's name)

"Concerned Netizen" <SpammeNotDangit@xxxxxxxxxx> wrote in message news:V1ADe.1361$Fk4.955@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"murthi" <c_xyz_murthi@xxxxxxxxxxxxxxxxxxxx> wrote in message news:UIzDe.9568$Zx3.5331@xxxxxxxxxxx

S1 was done by SMI? In Chicago? Ridgway? GOd, my memory's getting fuzzy!


In retrospect, I'm not sure SMI did the S1, but that was the company I think i was looking for.

Does anyone know who founded it?


Relevant Pages

  • Re: EntryStatus and smiv1
    ... modification of SMI v2 tables, ... "We support row creation, deletion, and activation ... the choices made by the MIB module designer, ... your agent if you implement what they expect. ...
  • Re: [RFC][PATCH 2.6.13-rc6] add Dell Systems Management Base Driver (dcdbas) with sysfs support
    ... > The dcdbas driver allows access to all of the Dell SMIs. ... > As implemented, get and set are normally separate SMI calls, so for each ... > stores some options in CMOS, these are already available in libsmbios. ... If even you don't know what its good for, we probably don't want to support it ...
  • error compiling linkchecker
    ... command 'gcc' failed with exit status 1" which is not very helpful. ... o.h 1.2 99/10/25 SMI ... ot support `long long' ...