From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8516] New: mkcubiecard.sh uses outdated sfdisk switch -D
Date: Wed, 09 Dec 2015 02:22:24 +0000 [thread overview]
Message-ID: <bug-8516-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8516
Bug ID: 8516
Summary: mkcubiecard.sh uses outdated sfdisk switch -D
Product: buildroot
Version: 2015.08
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: tudor at tudorholton.com
CC: buildroot at uclibc.org
The mkcubiecard.sh script contains the following lines:
# ~2048, 16MB, FAT, bootable
# ~rest of drive, Ext4
{
echo 32,512,0x0C,*
echo 544,,,-
} | sfdisk -D $DRIVE
There are two problems with this:
1) On newer versions of sfdisk, the -D switch has been removed.
2) Removing the -D switch from the command allows the script to be interpreted.
However, the unit sizes are different. In particular, "32,512,0x0c,*" results
in a partition starting at sector 32, of size 256K. (Not 2048, size 16MB as
mentioned in the comments) so the latter part of this script fails due to the
partition not being large enough.
My 2c would be to use something like parted which has a similar scripting
language, but which allows us to specify units so that the numbers don't change
meaning on different versions or architectures.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-12-09 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 2:22 bugzilla at busybox.net [this message]
2015-12-14 5:37 ` [Buildroot] [Bug 8516] mkcubiecard.sh uses outdated sfdisk switch -D bugzilla at busybox.net
2016-02-14 21:10 ` bugzilla at busybox.net
2016-11-03 21:53 ` bugzilla at busybox.net
2016-11-04 1:20 ` bugzilla at busybox.net
2016-11-04 8:44 ` bugzilla at busybox.net
2016-11-06 22:15 ` bugzilla at busybox.net
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=bug-8516-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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