From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yoann Padioleau <pad@fb.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Date: Sat, 18 Jan 2014 06:57:32 +0000
Message-ID: <725B0528-2ACD-49BF-B09C-8A0625C89080@fb.com>
Content-Type: text/plain; charset="us-ascii"
Content-ID: <824224DC673DFC449F35A13745BAE8C4@fb.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [9fans] mechanism to bind partitions in /dev?
Topicbox-Message-UUID: b3de40ec-ead8-11e9-9d60-3106f5b1d025

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 shel=
l (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=20
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?