From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: "parted" vs "sfdisk"
Date: Fri, 5 Aug 2016 06:19:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1608050617280.13505@localhost.localdomain> (raw)
your personal opinions, if you would -- i'm working on some scripts
to do automated installs on a target board, currently based on
parted, but parted seems a bit dense at times, and awkward, and i'm
thinking of switching to sfdisk.
for people who have done this sort of thing, do you have any strong
opinions either way of parted versus sfdisk? i realize that's not much
to go on, just curious about personal preferences, and why.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2016-08-05 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 10:19 Robert P. J. Day [this message]
2016-08-05 10:28 ` "parted" vs "sfdisk" Gary Thomas
2016-08-05 10:31 ` Robert P. J. Day
2016-08-05 13:00 ` Andrew Bradford
2016-08-05 14:02 ` Robert P. J. Day
2016-08-09 12:22 ` Mike Looijmans
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=alpine.LFD.2.20.1608050617280.13505@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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