From: utzoo!decvax!harpo!npoiv!npois!houxm!houxa!houxi!houxq!3723edm Newsgroups: net.unix-wizards Title: kernel memory tomfoolery Article-I.D.: houxq.232 Posted: Sat Jan 1 16:21:16 1983 Received: Sun Jan 2 01:38:43 1983 A while back, a question was raised about how to find out what's in kmem, e.g. how to you locate the process table, what's there once you find it, and whatever other goodies may be there. Subsequent articles discussed why reading kmem was a bad idea, and suggested improved interfaces to obtain the information in kmem. This discussion is all well and good, but I am still hoping somebody will provide the information originally requested. In addition, I would like some suggestions on what users who have permission to both read and *write* kmem and mem can do with this ability. There are apparently several systems where reading and *writing* kmem and mem are allowed, and I would think this capability could be put to various interesting uses. I have read enough about why these programs should be written using better interfaces, so there's no point in flaming about why it's so lousy to access kmem directly--that is the only interface provided. Eli Mantel, houxq!3723edm