9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Device permissions
Date: Mon, 15 Apr 2002 15:59:09 +0200	[thread overview]
Message-ID: <20020415155907.A19779@cackle.proxima.alt.za> (raw)

I'm busy extending the ns16552 driver for the PC to handle a multiport
card (shared IRQ, it's not quite managed by the existing driver) and
largely it is all functional.

However.  The owner of the CPU server is "proxima" and "lucio" is
listed among the group members of "proxima" (no group leader - does
that matter?):

	10008:proxima::lucio

The device I'm trying to access from either a drawterm session or a
workstation cpu session (where I'm logged on as "lucio") is:

	--rw-rw---- t 0 proxima proxima 0 Apr 15 12:47 /dev/eia000

and attempts to read the device fail:

	cpu% cat eia000
	cat: can't open eia000: permission denied

What am I missing?  I'd hate to think that permissions will turn out
to be the stumbling block in distributing access to resources.  Is
there perhaps a more congenial way of gaining access from a remote
workstation?

++L


                 reply	other threads:[~2002-04-15 13:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020415155907.A19779@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).