[9fans] q re /sys/src/cmd/disk/prep/prep.c:240

[9fans] q re /sys/src/cmd/disk/prep/prep.c:240

[James A. Robinson]

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

So I noticed that if I run disk/prep -b -a^(arenas isect bloom)
against my disk it goes ahead and creates a partition table that
has arenas starting at sector 0.

If I manually create partitions, /sys/src/cmd/disk/prep/prep.c:24
guards against using sectors 0 and 1 unless it's a 9fat partition.

Why is there a difference in the way an automated partition
set is created vs a manual one?

Jim

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

Re: [9fans] q re /sys/src/cmd/disk/prep/prep.c:240

[Steve Simon]

The usual process is to use prep first to create a windows etc compatible partition table with one big partition called plan9. then subdivide that.

see the recipie near the end of the format(1) manpage.

why part does different things in automatic mode I don't know.

-Steve

Re: [9fans] q re /sys/src/cmd/disk/prep/prep.c:240

[James A. Robinson]

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

On Fri, Nov 4, 2016 at 1:43 PM Steve Simon <steve@quintile.net> wrote:
> The usual process is to use prep first to create a windows etc
> compatible partition table with one big partition called plan9.
> then subdivide that.
>
> see the recipie near the end of the format(1) manpage.
>
> why part does different things in automatic mode I don't know.

Hi,

Yes, when I used disk/fdisk I set a single p1 partition with
the label plan9.  Then I was running disk/prep against that
/dev/sdE1/plan9 partition.

I couldn't think of any reason I needed a 9fat partition on
a disk I didn't plan to use as a boot disk.

Jim

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