9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] External HDD over USB
Date: Sun,  8 Feb 2009 10:04:07 -0500	[thread overview]
Message-ID: <1a40eb020fc3455dd328b4bd4a8bcf40@quanstro.net> (raw)
In-Reply-To: <4e6ca2050902072214h54e4cb15k2f356324f3375c5f@mail.gmail.com>

> 2009/2/6 erik quanstrom <quanstro@quanstro.net>:
> > are you running usb/disk as the host owner (eve)?
> >
>
> oh, *eve* -- yes, I've tried as eve also, with the same
> results.

hostowner, after /dev/hostowner, and eve, after the kernel
variable name, refer to the same thing.  eve is "" until set
by factotum -S (cpuserver) or factotum -u (terminal).  factotum
writes the hostowner to /dev/hostower and as a special case
the setting process' owner is reset as well.

with the default install, a cpu server's hostowner is bootes.

> any debugging I ought to try?

auth/debug is always a good start.  no arguments, no man
page.  just run it.

once that fails, i'd use acid(1) truss to pinpoint the system
call that results in permission denied.  if it is /dev/usb*,
i would use scuzz(8) to double-check that it isn't a bug or misleading
message in devusb.  giving scuzz the "probe" command should
list all the available sd devices.  if it does not, then it's likely
a real permissions problem.

it's pretty likely that i haven't foreseen what's really going
wrong on your system.  so you're probablly going to need
to do a bit of experimentation.

good luck.

- erik



      reply	other threads:[~2009-02-08 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  4:08 Akshat Kumar
2009-02-07  4:12 ` erik quanstrom
2009-02-07  4:35   ` akumar
2009-02-08  6:14   ` Akshat Kumar
2009-02-08 15:04     ` erik quanstrom [this message]

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=1a40eb020fc3455dd328b4bd4a8bcf40@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).