Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!gatech!ncar!noao!mcdsun!mcdchg!heiby From: heiby@mcdchg.UUCP (Ron Heiby) Newsgroups: comp.unix.wizards Subject: Re: phys(2) under sVr3? Message-ID: <10126@mcdchg.UUCP> Date: 3 Jun 88 23:32:32 GMT References: <10033@tekecs.TEK.COM> Reply-To: heiby@mcdchg.UUCP (Ron Heiby) Organization: Motorola Microcomputer, Schaumburg, IL Lines: 11 Motorola Microcomputer Division's System V/68 Release 3 has an augmentation to the shmget(2) call, whereby a process with euid 0 can specify the *physical* address at which the shared memory segment is to be located. said process can then set permissions, owner, and group appropriately for the application and exit, leaving the shared memory segment ready to be shmat(2)'d by the appropriate processes. I have a couple of customers who have used this interface to avoid writing a driver for (for example) an imaging board. -- Ron Heiby, heiby@mcdchg.UUCP Moderator: comp.newprod & comp.unix "Failure is one of the basic Freedoms!" The Doctor (in Robots of Death)