From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] installing on a usb disk
Date: Mon, 19 Jul 2010 10:33:17 +0200 [thread overview]
Message-ID: <AANLkTilzi57Zu2XwfipTdVy28h1pjN3abXdUYC_DM75B@mail.gmail.com> (raw)
In-Reply-To: <8055D71E-EEAA-4812-AB39-518A9F70F21C@corpus-callosum.com>
>
> If I do:
>
> usb/disk
>
> I get "no device found". But if instead the command is:
>
> usb/usbfat:
>
> I get /dev/sdU0.0 and /dev/sdU0.1 with plausible trees (ctl data raw). The sdU0.0 corresponds to a usb/probe that returns:
>
Are you running usbd with embedded disks? In that case the disks are owned by
the usb/disk linked into usbd, and the one you start by hand should
see no disks, as it happens.
I'd like to confirm this, just to know if it's a bug.
next prev parent reply other threads:[~2010-07-19 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 2:30 Jeff Sickel
2010-07-19 8:33 ` Francisco J Ballesteros [this message]
2010-07-19 13:48 ` Jeff Sickel
2010-07-19 13:52 ` Francisco J Ballesteros
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=AANLkTilzi57Zu2XwfipTdVy28h1pjN3abXdUYC_DM75B@mail.gmail.com \
--to=nemo@lsub.org \
--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).