9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] 9Front network (driver?) issue
Date: Mon, 23 Dec 2013 01:03:31 +0100	[thread overview]
Message-ID: <df4c9e7919a119a90cb90d9369dbf3ee@felloff.net> (raw)
In-Reply-To: <CABwHSOt8Uyf4o38dKNwJHtOFeKoQxggVRq4T9SCjgeN67y+BvQ@mail.gmail.com>

thats strange. when you plug in the drive, the nusbrc script
started the usb disk filesystem and run that fdisk command to
register the partitions. for some reason, the partitions
step failed. but when you run it manually later it wored.

the drive might be sensitive to the timing?

can you pull and replug the drive and see if there are any
error messages on the console?

as a work arround for now, you can try doing this manually:

diskparts /dev/sdU6.0
dossrv
mount -c /srv/dos /n/usb /dev/sdU6.0/dos
cd /n/usb

the dos filesystem does not do write buffering so there is
no need to flush. (see dossrv(4))

mounts are local to the namespace. you can remove something
from the namespace with the unmount command (see bind(1))
or you just close the whole namespace (close the rio window).

for documentation on formating and partitioning disks see prep(8).

--
cinap



  reply	other threads:[~2013-12-23  0:03 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 [this message]
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
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=df4c9e7919a119a90cb90d9369dbf3ee@felloff.net \
    --to=cinap_lenrek@felloff.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).