Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ist.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!mit-eddie!godot!harvard!seismo!mcvax!ukc!qtlon!ist!jmc From: jmc@ist.UUCP Newsgroups: net.unix-wizards Subject: Re: Access to kmem - System namelist - 'ps' etc Message-ID: <272@ist.UUCP> Date: Fri, 14-Dec-84 14:53:38 EST Article-I.D.: ist.272 Posted: Fri Dec 14 14:53:38 1984 Date-Received: Sat, 22-Dec-84 01:26:54 EST References: <970@opus.UUCP> Organization: Imperial Software Technology, London, England Lines: 15 > Why not retain the current model but put some finer-grained protection in? > That is, let the kernel be selective about what areas of memory it will > read for a process. This is perhaps ratty, but you don't end up trying to > reorganize a system call when you discover that ps, pstat, or some new tool > you've designed needs access to a data structure you didn't plan on at > first. > Dick Dunn a Gosh it does sound rather like what I originally suggested..... -- John Collins calling courtesy of ist Please reply to ...!mcvax!ist!inset!jmc Phone: +44 727 57267 Snail: 47 Cedarwood Drive, St Albans, Herts, AL4 0DN, England