home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!auspex-gw!guy
- From: guy@Auspex.COM (Guy Harris)
- Newsgroups: comp.protocols.nfs
- Subject: Re: lockd
- Message-ID: <13718@auspex-gw.auspex.com>
- Date: 23 Jul 92 23:58:06 GMT
- References: <14hpi3INNppo@seven-up.East.Sun.COM> <nje1jic@rhyolite.wpd.sgi.com> <14mrk9INNis@seven-up.East.Sun.COM>
- Sender: news@auspex-gw.auspex.com
- Organization: Auspex Systems, Santa Clara
- Lines: 18
- Nntp-Posting-Host: auspex.auspex.com
-
- >Lockd on SunOs of that vintage could
- >#probably have used vfork(), although that would have been somewhat kludgy.
- >
- >I think that the first lockd work preceded even the SunOS 4.0 memory
- >rearchitecture. Prior to that, vfork would have been a killer.
-
- Well, I'm not sure what the rearchitecture has to do with the use of
- "vfork()". I'm also not sure what "vfork()" has to do with e.g.
- multithreading "lockd", given that, while parent and child share their
- address space, the parent is put in suspended animation until the child
- either "exec"s or exits (true both in 4.x and earlier releases).>
-
- >| Thought for the day: If Unix had been
- >| developed in England, we'd all be using
- >| BCPL (and migrating to BCPL++)...
-
- (Unless, of course, Martin Richards came to the same conclusion that the
- folks who did B came to, and made a typeful successor to BCPL....)
-