9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mechanism to bind partitions in /dev?
Date: Sat, 18 Jan 2014 18:17:19 +1100	[thread overview]
Message-ID: <CAJQxxwkT8Sy_PbaQuh+A=FSei=yfMTXn74Qhwcezndeh3aph7A@mail.gmail.com> (raw)
In-Reply-To: <725B0528-2ACD-49BF-B09C-8A0625C89080@fb.com>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

disk/prep (and it's mates) are what you need for sdC0. man 8 prep.

brucee


On 18 January 2014 17:57, Yoann Padioleau <pad@fb.com> wrote:

> Hi,
>
> Can someone explain how the partitions in /dev/sdC0/xxx are populated? Who
> create those device files? I have a small plan9 kernel running a small
> shell (sh.Z)
> in memory and when I do  'bind #S/sdC0 /dev/' I just see the 'data',
> 'ctl', and 'raw' files.
> There is no 9fat or plan9 or whatever partitions there is on this disk. In
> fact I've
> tried to make on MACos via the Utility disk some fat images and when I do
> qemu -hdb dosdisk.img I can not access again the fat partition on this disk
> (I've tried dossrv and then mount /srv/dos/ /mnt #sdC1/data but it does
> not work).
> I can access it though when it's on a floppy disk (mount /srv/dos /mnt
> /dev/fd0disk
> works). How fd0disk is different from #sdC1/data?
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

  reply	other threads:[~2014-01-18  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18  6:57 Yoann Padioleau
2014-01-18  7:17 ` Bruce Ellis [this message]
2014-01-18 22:34   ` Yoann Padioleau
2014-01-18 19:33 ` Steven Stallion

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='CAJQxxwkT8Sy_PbaQuh+A=FSei=yfMTXn74Qhwcezndeh3aph7A@mail.gmail.com' \
    --to=bruce.ellis@gmail.com \
    --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).