Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA28216; Wed, 20 Dec 95 14:27:10 EST
Received: from colossus.cse.psu.edu by MIT.EDU with SMTP
	id AA27780; Wed, 20 Dec 95 14:27:04 EST
Received: by colossus.cse.psu.edu id <78355>; Wed, 20 Dec 1995 14:13:23 -0500
Received: from gatekeeper.dbSystems.com ([204.181.117.1]) by colossus.cse.psu.edu with SMTP id <78352>; Wed, 20 Dec 1995 14:13:04 -0500
Received: (from gdb@localhost) by gatekeeper.dbSystems.com (8.6.11/8.6.9) id NAA10247 for 9fans@cse.psu.edu; Wed, 20 Dec 1995 13:06:33 -0600
Date: 	Wed, 20 Dec 1995 14:06:33 -0500
From: "G. David Butler" <gdb@dbSystems.com>
Message-Id: <199512201906.NAA10247@gatekeeper.dbSystems.com>
To: 9fans@cse.psu.edu
Subject: Permissions on names served by the kernel
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu

Hi all!

I am running into an interesting problem.  I have been working on
getting the LP subsystem up using a PostScript printer connected
to the COM port of my PC cpu server.  It all works great (after
creating a "postio" and fixing lpdaemon) from the cpu server console.

When printing from a terminal (yes tcpsend works now) or from
a cpu window on the terminal,  the postio program can't do I/O to
/dev/eia0 since it doesn't have permissions.

The question.  How do you change the permissions of a file that is
served by the kernel?  Since the lpdaemon runs as "none" and the
permissions on #t/eia0 are 660 bootes bootes, it won't work.

Also, is there a problem binding something like '#t' in multiple
processes and doing I/O?

If the answer to the question is "you can't" (that is what it looks
like), it would seem my only alternative is to start up a process on
the cpuserver that keeps an eye on the print queue and fires up the
daemon.  Perhaps using pipe(3) to synchronize the spooler and daemon?

I would like to see a discussion about unrelated namespace processes
binding '#|" for IPC.  Does this work or does each bind create
another pair of fd's?  There are some things about this local
namespace that makes one feel uncomfortable.

If anyone has a better idea or a different view of the whole issue,
I would appreciate any input.

(As soon as I get it all to work, I will make it available.)

Thanks.

db

