Subject: "/dev/io as kmem device"?
To: None <mycroft@NetBSD.ORG, port-i386@NetBSD.ORG>
From: Chris G Demetriou <Chris_G_Demetriou@BALVENIE.PDL.CS.CMU.EDU>
List: port-i386
Date: 12/09/1995 01:26:22
> mycroft
> Sat Dec  9 00:53:05 EST 1995
> Update of /a/cvsroot/src/sys/arch/i386/i386
> In directory pain.lcs.mit.edu:/b/tmp/cvs-serv21022
> 
> Modified Files:
> 	conf.c 
> Log Message:
> Include /dev/io as one of the `kmem' devices.

While i think this definitely makes sense, it raises some concerns:

(1) shouldn't the i386_iopl syscall be similarly protected (i.e.
    in terms of what you can do for which 'security levels') as
    /dev/io?  (This makes sense, because of both security concerns
    and consistency...)

(2) If (1) is done, am i correct in thinking that XFree86 just Will
    Not Work if 'options INSECURE' (or something similar) isn't
    present in the kernel? 


chris