From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] use nproc
Date: Sun, 1 Jan 2017 09:32:47 +0100 [thread overview]
Message-ID: <20170101093247.1e9cc6b3@free-electrons.com> (raw)
In-Reply-To: <87zijd87rg.fsf@dell.be.48ers.dk>
Hello,
On Fri, 30 Dec 2016 21:46:43 +0100, Peter Korsgaard wrote:
> > My rule of thumb is that once a change is 7 years old, you can rely on
> > the installed base to have it. With that in mind, would you like to use
> > nproc to check how many processors are available?
>
> > http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=74cf4cb26dcecd36eb45dc00dbd4587d9dc24a2f
>
> Why? What is the advantage? Purely cosmetical? Are there any well known
> distributions providing nproc and not getconf?
Well, the simplification provided by Rob looks useful to me. It's
purely cosmetic, but we also do tons of other cosmetic changes.
The big question is whether nconf is available even in the really old
RHEL distros that some of our users have.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-01 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 20:14 [Buildroot] [PATCH] use nproc Rob Landley
2016-12-30 20:46 ` Peter Korsgaard
2017-01-01 8:32 ` Thomas Petazzoni [this message]
2017-01-01 9:46 ` Peter Korsgaard
2017-01-01 8:30 ` Thomas Petazzoni
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=20170101093247.1e9cc6b3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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