Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!uwvax!dogie!uwmcsd1!marque!uunet!munnari!mulga!ditmela!latcs1!vertical!greg
From: greg@vertical.oz (Greg Bond)
Newsgroups: comp.unix.wizards
Subject: Re:  Reading VAX SID register on ultrix or 4.3bsd
Summary: Can you say IOCTL? I thought you could.
Keywords: syscall kenel variable
Message-ID: <90@vertical.oz>
Date: 29 Apr 88 07:07:04 GMT
References: <13089@brl-adm.ARPA> <337@hotlr.ATT>
Reply-To: greg@vertical.oz (Greg Bond)
Organization: Vertical Software, Melbourne, Australia
Lines: 26

In article <337@hotlr.ATT> dkc@hotlr.UUCP (Dave Cornutt) writes:
> > 	get_kernel_variable(int variable_index)
>Yep, a lot of stuff like getpagesize and getdtablesize could be
>sucked up into this.  Define a bunch of indices in an include file
>for naming the variables (it might be a good idea to divide them
>into hardware-independent and hardware-dependent partitions, with
>plenty of numbers reserved for future use in both).  You might
>also want to make the syscall take a pointer to an area where
>it can deposit the value, so it can return string and structure
>items instead of just ints.

Does this sound like an IOCTL? Which has the advantage of encoding 
the arg size and mode into the IOCTL.

What file to do the ioctl on? /dev/proc?

Nasty portability problems, however.

l
i
n
e
-- 
Gregory Bond,  Vertical Software, Melbourne, Australia
ACSnet: greg@vertical.oz,              UUCP: uunet!vertical.oz!greg
Gad! Did *I* start those lightbulb jokes?