From owner-freebsd-hackers Sat Dec 30 19:11:44 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA02371 for hackers-outgoing; Sat, 30 Dec 1995 19:11:44 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA02362 for ; Sat, 30 Dec 1995 19:11:35 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id OAA16531; Sun, 31 Dec 1995 14:11:21 +1100 From: David Dawes Message-Id: <199512310311.OAA16531@rf900.physics.usyd.edu.au> Subject: Re: /dev/io To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 31 Dec 1995 14:11:20 +1100 (EST) Cc: hackers@freebsd.org In-Reply-To: <8724.820374911@time.cdrom.com> from "Jordan K. Hubbard" at Dec 30, 95 05:55:11 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org Precedence: bulk >> To me it seems like it would be more "standard" if FreeBSD supported an >> implementation like NetBSD's. It would also pave the way for the >> implementation of IO permission bitmaps (if they are ever needed). Changing >> it would probably be a little more secure, and I can't even think of any >> programs that would break if /dev/io was removed? > >I think a few X servers would definitely break of /dev/io went away >suddently, but I also see no reason why the other interface couldn't >be implemented in parallel with a change-over at some point in the >future. For what it's worth, the XFree86 servers get I/O permission by using the KDENABIO ioctl in the console driver rather than by opening /dev/io. David