phys(2) under sVr3?

[Ron Heiby]

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 at mcdchg.UUCP	Moderator: comp.newprod & comp.unix
"Failure is one of the basic Freedoms!" The Doctor (in Robots of Death)