From owner-freebsd-hackers Wed May 5 2:10: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kyrnet.kg (news.kyrnet.kg [195.254.160.9]) by hub.freebsd.org (Postfix) with ESMTP id A1F4014C82 for ; Wed, 5 May 1999 02:09:56 -0700 (PDT) (envelope-from fygrave@tigerteam.net) Received: from localhost by kyrnet.kg (8.9.3/8.9.1) with ESMTP id OAA22893; Wed, 5 May 1999 14:01:44 +0500 (GMT) X-Authentication-Warning: kyrnet.kg: fygrave owned process doing -bs Date: Wed, 5 May 1999 14:01:44 +0500 (GMT) From: CyberPsychotic X-Sender: fygrave@kyrnet.kg To: Doug Rabson Cc: freebsd-hackers@freebsd.org, tech@openbsd.org Subject: Re: io ports reading/writing In-Reply-To: Message-ID: Confirm-receipt-to: fygrave@usa.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ~ ~ The access control for io ports is controlled by the file-system ~ permissions on /dev/io. In a standard setup, only root can access this ~ device. ~ yes. But I was refering to linux scheme, where you can set the port-range, so the code wouldn't make any unintentional damage. (like if you're working with cmos you could only permit 0x70/0x71 ports, so even if code goes nuts, your disks will be safe). This is basically programmer's problem of course, but the feature is very handy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message