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] how to make hardware work?
Date: Tue, 18 Jan 2011 08:53:40 -0500	[thread overview]
Message-ID: <c5e261ca4753b4b7598d7b218f1d127f@chula.quanstro.net> (raw)
In-Reply-To: <125317bb829b1e9a2afe41e7a8ce02f6@gmail.com>

> And starts usb/disk
>
> 	term% ls /dev/*u*
> 	/dev/sdU6.0/ctl
> 	/dev/sdU6.0/data
> 	/dev/sdU6.0/raw
> 	term% cat /dev/sdU6.0/ctl
> 	/dev/usb/ep6.0 lun0: inquiry geometry 1990407 512
>
> No partitions. Checked in Linux

this one's easy.  unlike the braindamage in linux, plan 9
allows you to partition the drive when and if you wish.
the kernel doesn't have partition table reading software.
you have to partition this disk with

	d=/dev/sdU6.0
	disk/fdisk -p $d/data>$d/ctl
	for(i in $d/plan9*)
		disk/prep -p $i>$d/ctl
this is all distilled into a script diskparts  (sic.).

- erik



  reply	other threads:[~2011-01-18 13:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 15:23 sergey.kish
2011-01-17 17:17 ` John Floren
2011-01-17 18:11   ` Nick LaForge
2011-01-17 18:37     ` lsub
2011-01-17 18:52       ` lsub
2011-01-17 19:09   ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-01-17 19:35     ` Nick LaForge
2011-01-17 23:27       ` John Floren
2011-01-18  0:01         ` Francisco J Ballesteros
2011-01-18  3:29           ` Nick LaForge
2011-01-18 13:27   ` sergey.kish
2011-01-18 13:53     ` erik quanstrom [this message]
2011-01-18 19:23     ` Lyndon Nerenberg (VE6BBM/VE7TFX)
  -- strict thread matches above, loose matches on Subject: below --
2011-01-16  6:21 [9fans] plan9 go output faults on 9vx but ok on cpu kokamoto
2011-01-17 15:20 ` [9fans] how to make hardware work? sergey.kish

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=c5e261ca4753b4b7598d7b218f1d127f@chula.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).