From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Heads up
Date: Thu, 30 Apr 2015 06:30:19 -0600 [thread overview]
Message-ID: <5542205B.2040609@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1sqjwfh=LYAJu781B-JjBEYuBk6OohkqXu+B7YrYpC6HtQ@mail.gmail.com>
On 2015-04-30 01:45, Khem Raj wrote:
> On Wed, Apr 29, 2015 at 7:18 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> This is just a note that the recent upgrade of util-linux
>> to version 2.26.1 (from 2.25.2) was much more major than
>> the version change implies. The 'sfdisk' tool changed a
>> lot and will no longer be compatible with many scripts out
>> there that still use it.
>
> Can we document the needed differences and info for users ?
> may be it will handy in release notes too eventually when release time comes
>
From the 2.26 release notes:
This version provides a completely new sfdisk(8) command; the new version is
based on libfdisk. If your use cases depend on sfdisk(8), then it is strongly
recommended to be careful and re-test your scripts. The new version supports
MBR and GPT disk labels (SGI and SUN are also supported but not well tested).
The new version no longer supports some obscure MBR-specific command-line
options nor legacy CHS addressing.
What this means is that any script (there are a ton of them out there)
that tries to create a label for a disk device using Cylinder-Head-Sectors
style will have to be rewritten as the new sfdisk only does sector unit
addressing.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-04-30 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 14:18 Heads up Gary Thomas
2015-04-29 14:46 ` Robert P. J. Day
2015-04-30 7:45 ` Khem Raj
2015-04-30 12:30 ` Gary Thomas [this message]
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=5542205B.2040609@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.