From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: "parted" vs "sfdisk"
Date: Fri, 5 Aug 2016 06:31:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1608050630250.13682@localhost.localdomain> (raw)
In-Reply-To: <57b0c57a-a81c-42fa-0f31-3ea9d2acff56@mlbassoc.com>
On Fri, 5 Aug 2016, Gary Thomas wrote:
> On 2016-08-05 12:19, Robert P. J. Day wrote:
> >
> > 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.
>
> As you know, I went the other way - I started with sfdisk and
> I find parted more intuitive and easier to use. I also think
> it has a better long-term support horizon.
i figured you'd weigh in on this. :-) i'm going to experiment both
ways for a bit.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-08-05 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 10:19 "parted" vs "sfdisk" Robert P. J. Day
2016-08-05 10:28 ` Gary Thomas
2016-08-05 10:31 ` Robert P. J. Day [this message]
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.1608050630250.13682@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=gary@mlbassoc.com \
--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