9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] mechanism to bind partitions in /dev?
@ 2014-01-18  6:57 Yoann Padioleau
  2014-01-18  7:17 ` Bruce Ellis
  2014-01-18 19:33 ` Steven Stallion
  0 siblings, 2 replies; 4+ messages in thread
From: Yoann Padioleau @ 2014-01-18  6:57 UTC (permalink / raw)
  To: 9fans

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?





^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [9fans] mechanism to bind partitions in /dev?
  2014-01-18  6:57 [9fans] mechanism to bind partitions in /dev? Yoann Padioleau
@ 2014-01-18  7:17 ` Bruce Ellis
  2014-01-18 22:34   ` Yoann Padioleau
  2014-01-18 19:33 ` Steven Stallion
  1 sibling, 1 reply; 4+ messages in thread
From: Bruce Ellis @ 2014-01-18  7:17 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [9fans] mechanism to bind partitions in /dev?
  2014-01-18  6:57 [9fans] mechanism to bind partitions in /dev? Yoann Padioleau
  2014-01-18  7:17 ` Bruce Ellis
@ 2014-01-18 19:33 ` Steven Stallion
  1 sibling, 0 replies; 4+ messages in thread
From: Steven Stallion @ 2014-01-18 19:33 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

On Fri, Jan 17, 2014 at 10:57 PM, 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?

Hi Yoann,

sdC0 and friends are populated by devsd (#S) as a part of some
bootstrap goop. What you will typically find is that only the
drive/partitions used to boot are populated, this is the reason for
the readparts= plan9.ini variable. There are other ways to prompt
devsd to create fs entries at boot - I'd suggest looking through
/sys/src/9/port/devsd.c.

Steve



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [9fans] mechanism to bind partitions in /dev?
  2014-01-18  7:17 ` Bruce Ellis
@ 2014-01-18 22:34   ` Yoann Padioleau
  0 siblings, 0 replies; 4+ messages in thread
From: Yoann Padioleau @ 2014-01-18 22:34 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

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

Got it, thx a lot.
Just need to do  fdisk -p /dev/sdC0/data > /dev/sdC0/ctl
and then prep -p /dev/sdC0/plan9 > /dev/sdC0/ctl


On Jan 17, 2014, at 11:17 PM, Bruce Ellis <bruce.ellis@gmail.com<mailto:bruce.ellis@gmail.com>> wrote:

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<mailto: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: 1926 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-01-18 22:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-18  6:57 [9fans] mechanism to bind partitions in /dev? Yoann Padioleau
2014-01-18  7:17 ` Bruce Ellis
2014-01-18 22:34   ` Yoann Padioleau
2014-01-18 19:33 ` Steven Stallion

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).