[LEDE-DEV] [PATCH 1/2] Add some common packages for x86-64 target.

[Ben Greear]

On 05/26/2016 07:05 PM, Daniel Curran-Dickinson wrote:
>
> Hi,
>
> On Thu, 2016-05-26 at 16:57 -0700, greearb at candelatech.com wrote:
>> From: Ben Greear <greearb at candelatech.com>
>>
>> This should make x86-64 targets more useable out of the box.
>> The assumption is that most x86-64 users have adequate storage,
>> and those that do not can still config away the options they
>> do not need.
>
> Although I agree x86-64 is normally big, I'm not sure that it makes
> sense to make the default install so different from other devices.  One
> thing you might want to look is that patch series I've got as URFC's for
> doing things like preferring full vs. busybox and see if you could
> implement this as something that could be added via a single package
> install (or from imagebuilder baked into the image by specifying a
> single package).
>
> I'm not sure that making big/extra/different stuff part of snapshot and
> release images is a good idea (although including more drivers is
> different IMO, because that is about hardware support out of the box,
> rather than about different choices about what's in the OS (unlike full
> bzip2, getopt, different busybox options, etc)).  I think the user should
> consciously decide they're looking for something other than a standard
> LEDE system.

So maybe getopt is not needed, but here is my reasoning for some of the
others:

tcpdump:  Grab pkt captures, especially in monitor mode for debugging.
           Pkt capture is pretty much required for debugging tricky things, especially
           with something like ath10k that has thick firmware.
ethtool:  Low level stats, firmware version, etc.  Automated bug reporting.
lspci: Automated bug reporting, figure out what driver is missing from random hardware.
curl:  Download scripts and other things from the web, including in automated fashion.
iw:  Automated bug reporting, manual debugging.
iperf3:  Easy way to do performance testing.  Could be part of automated performance testing.

I think if space allows, these should be added to all or most images,
but I wanted to start with a platform that I use and can test, and which
has no space constraints in most cases.  So, this more full image could
start being more the 'standard LEDE' system.

I can do this all with the buildme logic in my 2/2 patch too, so maybe that
is the way to go.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com