VMS

Page Allocation
Each process is allocated a static number of pages at startup
Kernel never allocates more pages than there are frames
If there are not enough frames, a process is temporarily swapped out 

Low Level Management is done within the kernel; similar to Unix

Eviction Policy
All applications are completely self-paged
If an application is at its frame quota and tries to allocate a page, the kernel first asks for a page back
Pages are not necessarily flushed immediately
If a page is required, the inactive list is checked
Applications can "go over" their allocation limit even if there is extra memory in the system
Method is very efficient
Applications always know what is best for themselves
No global policy

Paging is similar to Unix; there are no trust issues