From: "Sinan Kaya" <okaya@kernel.org>
To: Ross Burton <ross@burtonini.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta-oe][PATCH v5] procps: split ps and sysctl into individual packages
Date: Tue, 12 Jan 2021 13:57:30 -0500 [thread overview]
Message-ID: <5755d813-6ffd-f23e-06a1-584a3222e797@kernel.org> (raw)
In-Reply-To: <CAAnfSTubexeYPZeexc5xTnx2sz3BiYUj4un=FmtaucDwPNOZXg@mail.gmail.com>
On 1/12/2021 9:09 AM, Ross Burton wrote:
> On Wed, 16 Dec 2020 at 22:16, Sinan Kaya <okaya@kernel.org> wrote:
>> Move the ps and sysctl tools into its own package. Useful for
>> size constrained systems that only want the ps and/or sysctl tools.
> Both of these are part of busybox. If you're in massively size
> constrained systems, why not just use busybox?
That's true. I needed more functionality for these two specific tools.
The rest is all busybox as you suggested.
To be fair, ps in busybox really sucks IMO.
prev parent reply other threads:[~2021-01-12 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 22:16 [meta-oe][PATCH v5] procps: split ps and sysctl into individual packages Sinan Kaya
2021-01-12 14:09 ` [OE-core] " Ross Burton
2021-01-12 18:57 ` Sinan Kaya [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=5755d813-6ffd-f23e-06a1-584a3222e797@kernel.org \
--to=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.com \
/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