Erling Westenvik <erling.westen...@gmail.com> wrote:

>Please ignore and forgive my obviously unforgivable ignorance:
>
>I wanted to test a snapshot of OpenBSD 5.1 on my ThinkPad T500 which
>runs 5.0 Release. I decided to overwrite the Windows 7 installation
>which I never use anyway. fdisk(8) before installation was more or less
>like this:
>
> #: id     C  H  S -     C   H  S [    start:     size ]
>----------------------------------------------------------------
> 0: 07     1 11  5 -   109  59 12 [     2048:   204800 ] NTFS
> 1: 07   109 59 13 - 41336   1  2 [   206848: 77918208 ] NTFS
>*2: A6 41336  1  3 - 82669 114 10 [ 78125056: 78120960 ] OpenBSD
> 3: 00     0  0  0 -     0   0  0 [        0:        0 ] unused
>
>During install, when prompted for which partition to use, I selected
>the
>run fdisk-option and used the +edit 1; to set partition 1 to type A6,
>and +flag 1;-command to make it the active and bootable partition like
>this:
>
> #: id     C  H  S -     C   H  S [    start:     size ]
>----------------------------------------------------------------
> 0: 07     1 11  5 -   109  59 12 [     2048:   204800 ] NTFS
>*1: A6   109 59 13 - 41336   1  2 [   206848: 77918208 ] OpenBSD
> 2: A6 41336  1  3 - 82669 114 10 [ 78125056: 78120960 ] OpenBSD
> 3: 00     0  0  0 -     0   0  0 [        0:        0 ] unused
>
>I'm almost certain I have done it like this earlier? I mean: just
>marking the partition to use with +flag n;, upon which the installer
>used
>that partition for creating layout with disklabel(8), leaving other
>partitions untouched?

You do not flag which "to use". Multiple A6 entries brings problems since you 
get multiple disklabels.

I am pretty sure this is documented and in the faq and archives.

You could try setting the partition not to be used to some other dummy type. 
Backup first. Ymmv.

/Alexander
>
>The rest of the installation went well as always with disklabel using
>the default layout. However, when I wanted to boot into my 5.0 and
>hence
>used the +flag 2;-command in fdisk(8), the system still booted into the
>new 5.1. Now it doesn't matter if I run +flag 1; or +flag 2; -- the
>system boots into 5.1 anyway.
>
>
>Regards,
>Erling

Reply via email to