From owner-freebsd-questions@FreeBSD.ORG Sat Jul 26 22:41:07 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AFF537B401 for ; Sat, 26 Jul 2003 22:41:07 -0700 (PDT) Received: from smtp2.adl2.internode.on.net (smtp2.adl2.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D091B43F75 for ; Sat, 26 Jul 2003 22:41:05 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from smtp2.adl2.internode.on.net (localhost [127.0.0.1]) h6R5f3gI093867 for ; Sun, 27 Jul 2003 15:11:04 +0930 (CST) Received: (from mailnull@localhost)h6R5f3ce093863 for ; Sun, 27 Jul 2003 15:11:03 +0930 (CST) X-Authentication-Warning: smtp2.adl2.internode.on.net: mailnull set sender to using -f Received: from beta.home (ppp526.sa.padsl.internode.on.net [150.101.246.13]) h6R5f1gI093859; Sun, 27 Jul 2003 15:11:03 +0930 Content-Type: text/plain; charset="windows-1252" From: Malcolm Kay Organization: At home To: Mark , Date: Sun, 27 Jul 2003 15:11:00 +0930 User-Agent: KMail/1.4.3 References: <200307262149.H6QLN203081893@asarian-host.net> In-Reply-To: <200307262149.H6QLN203081893@asarian-host.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307271511.00823.malcolm.kay@internode.on.net> X-Proc-As: freebsd-questions X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) Subject: Re: Unable to open /dev/io X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2003 05:41:07 -0000 On Sun, 27 Jul 2003 07:19, Mark wrote: > Earlier, I had asked a question on how to write a byte to the parallel > port. And Daan Vreeken was kind enough to point me to a litle c-source = that > uses /dev/io. > > Unfortunately, as I just found out, when I raise kern.securelevel to 2 > (FreeBSD 4.7R), I can no longer open /dev/io for writing. :( That means= I > can no longer use this method; because there is no way I will allow my > production server to run at kern.securelevel lower than 2. Which means = I am > back to square one. :( > > Sigh. Is there then no way to write a simple 0 or 1 to the parallel por= t, > without compromizing the security of the server at large? > I also responded to your original enquiry suggesting that you might also look at accessing the parallel port via /dev/ppi0 which can set the = data port using an ioctl() call -- man page ppi(4) I believe this has less restrictions than /dev/io opening the whole devic= e=20 port area. This might circumvent your problem. > Thanks, > > - Mark > Malcolm Kay