Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!think.com!paperboy!hsdndev!spdcc!merk!uvmark!irwin From: irwin@uvmark.uucp (Frank Irwin) Newsgroups: news.software.b Subject: Re: Ideas for Message-ID's Message-ID: <1991Mar27.232050.8137@uvmark.uucp> Date: 27 Mar 91 23:20:50 GMT References: <3427@litchi.bbn.com> <1991Mar22.050749.22115@looking.on.ca> Organization: Vmark Software, Inc. Lines: 19 In article fitz@wang.com (Tom Fitzgerald) writes: >brad@looking.on.ca (Brad Templeton) writes: > >The number of safe characters is way below 85 unfortunately. But above >36 it really doesn't do you a lot of good. If you want to crunch 31 bits >of timestamp and 15 bits of process ID into a string, it's easy to get a ^^^^^^^ > >Do any systems use 16-bit process IDs? The IBM RS/6000 uses 31-bit (yup, thirty-one) process IDs. You can always use the process slot in the kernel, which is encoded into the PID, but that still uses 17 bits. -- ==================================================================== Frank Irwin | "I'll bet $50 on that flush." Vmark Software, Inc. | Whooooosh! ..uunet!merk!uvmark!irwin | "Aaaaiiiieeee! Not *that* flush!"