Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!axion!uzi-9mm.fulcrum.bt.co.uk!igb
From: igb@fulcrum.bt.co.uk (Ian G Batten)
Newsgroups: news.software.b
Subject: Re: Ideas for Message-ID's
Message-ID: <N0Q&1*@uzi-9mm.fulcrum.bt.co.uk>
Date: 26 Mar 91 07:12:03 GMT
References: <3427@litchi.bbn.com> <1991Mar22.050749.22115@looking.on.ca> <5084abb1.1bc5b@pisa.citi.umich.edu>
Sender: news@fulcrum.bt.co.uk (News with an UZI)
Organization: BT Fulcrum, Birmingham
Lines: 11

In article <5084abb1.1bc5b@pisa.citi.umich.edu> rees@citi.umich.edu (Jim Rees) writes:
> CMU).  Uids may be just another Multics-era idea that got lost in the quest
> for "simplicity" (is Unix still simpler than Multics?)

I recall that Multics unique identifiers are only unique
per-installation and provided the clock is never reset.  They provided a
base-foo coding the clock which was ticking microseconds from 1900.  I
was told that there were some hairy interlocks on the clock so that in
multi-processor set-ups only one cpu could get a given clock value.

ian