From: "Ángel González" <ingenit@zoho.com>
To: Ulf Zibis <Ulf.Zibis@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: sfdisk man page bug
Date: Mon, 28 Jan 2013 21:33:33 +0100 [thread overview]
Message-ID: <5106E09D.5010708@zoho.com> (raw)
In-Reply-To: <51068D38.3040708@gmx.de>
On 28/01/13 15:37, Ulf Zibis wrote:
> Hi,
>
> from the Manual page sfdisk(8):
> "... For example, when there are several primary DOS partitions, DOS
> assigns C: to the first among these that is bootable.)"
>
> This seems to be wrong. I'm not 100 % sure about DOS, but about modern
> Windows, above statement is definitely wrong. Correct is:
> "... Windows/DOS assigns C: to the first among these that is visible
> (=not hidden).)"
> "... Windows/DOS typical generic MBR boot code loads and executes the
> bootloader found on the first among these that is bootable.)"
>
> to be sure, I tested following:
> - having old WinXP installation on sda1, labelled "WIN_OLD"
> - copy this partition by GParted to sda2
> - newly install WinXP on sda1, labelled "WIN_NEW"
> - set sda2 to active
> - boot
> --> result:
> 1. in effect, WinXP from sda1 becomes booted
> 2. sda1 is named C:, cd1 is named D:, "bootable" sda2 is named E:
>
> As today Windows is the more interesting use case, at least please add
> correct info for the Windows case.
>
> Many thanks for your attention and hopefully answer,
>
> -Ulf
Well, DOS assigns drive letters only to partitions it can read (although
obvious, this is not explained in the main page). When a partition is
hidden, it appears as having a different type, so it's skipped and thus
not taken into account.
In the Windows NT family (ie. all modern windows versions) it is
possible to assign fixed letters to a drive, so you no longer get the
letter-dancing that happened before.
next prev parent reply other threads:[~2013-01-28 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 14:37 sfdisk man page bug Ulf Zibis
2013-01-28 20:33 ` Ángel González [this message]
2013-01-28 23:00 ` Ulf Zibis
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=5106E09D.5010708@zoho.com \
--to=ingenit@zoho.com \
--cc=Ulf.Zibis@gmx.de \
--cc=util-linux@vger.kernel.org \
/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