From: Yoann Padioleau <pad@fb.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] mechanism to bind partitions in /dev?
Date: Sat, 18 Jan 2014 06:57:32 +0000 [thread overview]
Message-ID: <725B0528-2ACD-49BF-B09C-8A0625C89080@fb.com> (raw)
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?
next reply other threads:[~2014-01-18 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 6:57 Yoann Padioleau [this message]
2014-01-18 7:17 ` Bruce Ellis
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=725B0528-2ACD-49BF-B09C-8A0625C89080@fb.com \
--to=pad@fb.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).