From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9Front network (driver?) issue
Date: Mon, 23 Dec 2013 08:59:19 -0600 [thread overview]
Message-ID: <CABwHSOvqMC41dh6GKVQMLsJMgiSDUiVtk=3FpHf2wxM9E7XYkA@mail.gmail.com> (raw)
In-Reply-To: <bcfec040f15aebb914ab71d04a33339f@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
On Sun, Dec 22, 2013 at 10:52 PM, <cinap_lenrek@felloff.net> wrote:
> the fdisk command i gave you could read the partition table fine.
> (it didnt register them, just print)
>
> the code thats handling the automounting (/shr) should'v discovered
> the partitions by running the same command but apparently that didnt
> work. (otherwise, the dos partition should'v shown up in /dev/sdU*)
>
> i can not reproduce this on my systems and i need further information
> to debug this issue.
>
> i would like you to:
>
> pulling and replugging the usb device and watch the screen to see
> if there are messages showing up. (you can also run cat /dev/kprint in
> a rio
> window to capture the console output (make sure to make the window
> scrolling))
>
I am using vanilla 9front. I believe it is rio. I tried putting it in and
out and there is no message on the screen.
I tried cat /dev/kprint and that too did not display anything.
As I mentioned, when plugged in, for some reason, I am getting:
/shr/usb/sdU6.0/ctl
/shr/usb/sdU6.0/data
/shr/usb/sdU6.0/raw
I tried another USB drive. Same result.
BTW, how do I abort a command such as the cat /dev/kpeint? I tried ^c, ^d.
^\. Nothing worked. I ended up having to delete the entire window.
>
> try a different dos formatted usb drive.
>
> --
> cinap
>
>
[-- Attachment #2: Type: text/html, Size: 5713 bytes --]
next prev parent reply other threads:[~2013-12-23 14:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 18:56 Blake McBride
2013-12-22 19:07 ` cinap_lenrek
2013-12-22 19:42 ` Blake McBride
2013-12-22 19:48 ` cinap_lenrek
2013-12-22 19:55 ` Blake McBride
2013-12-22 20:00 ` andrey mirtchovski
2013-12-22 20:03 ` cinap_lenrek
2013-12-22 20:04 ` erik quanstrom
2013-12-22 20:16 ` Blake McBride
2013-12-22 20:31 ` erik quanstrom
2013-12-22 21:19 ` Blake McBride
2013-12-22 21:30 ` cinap_lenrek
2013-12-22 23:04 ` Blake McBride
2013-12-22 23:13 ` cinap_lenrek
2013-12-22 23:28 ` Blake McBride
2013-12-23 0:03 ` cinap_lenrek
2013-12-23 1:43 ` Blake McBride
2013-12-23 3:07 ` Skip Tavakkolian
2013-12-23 3:29 ` Blake McBride
2013-12-23 3:37 ` andrey mirtchovski
2013-12-23 3:48 ` Blake McBride
2013-12-23 4:02 ` Kurt H Maier
2013-12-23 6:28 ` Matthew Veety
2013-12-23 9:42 ` Steffen Daode Nurpmeso
2013-12-23 13:57 ` erik quanstrom
2013-12-23 3:49 ` Skip Tavakkolian
2013-12-23 13:38 ` erik quanstrom
2013-12-23 13:58 ` erik quanstrom
2013-12-23 4:52 ` cinap_lenrek
2013-12-23 14:59 ` Blake McBride [this message]
2013-12-23 15:04 ` Alexander Kapshuk
2013-12-23 15:11 ` Blake McBride
2013-12-23 15:17 ` Steve Simon
2013-12-23 15:37 ` erik quanstrom
2013-12-23 16:09 ` Tristan
2013-12-23 16:44 ` Steve Simon
2014-02-10 13:27 ` erik quanstrom
2013-12-24 3:43 ` erik quanstrom
2013-12-23 15:17 ` Alexander Kapshuk
2013-12-23 15:04 ` Friedrich Psiorz
2013-12-23 9:34 ` Steffen Daode Nurpmeso
2013-12-23 14:42 ` Blake McBride
2013-12-22 19:54 ` Kurt H Maier
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='CABwHSOvqMC41dh6GKVQMLsJMgiSDUiVtk=3FpHf2wxM9E7XYkA@mail.gmail.com' \
--to=blake@mcbride.name \
--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).