DENX Embedded Linux Development Kit discussion ()

John Connolly | 5 Oct 2010 17:21

Pruning Filesystem

Hello,

My project based on the eldk requires a much smaller footprint than we
currently have.  I'm going through the process of hand-removing many
packages (*-devel, etc), but it appears that the end-goal of 60mb
(confined by on-board flash space limitations of 64MB) is unattainable
due to the huge package (~270MB):

  277036416 bits crosstool-targetcomponents-ppc_4xx

Any pointers?  Is 60MB attainable?  Has anyone successfully pruned
away the ELDK in this fashion?

Thanks

-John Connolly

headers

Detlev Zundel | 5 Oct 2010 17:42

Re: Pruning Filesystem

Hi John,

> My project based on the eldk requires a much smaller footprint than we
> currently have.  I'm going through the process of hand-removing many
> packages (*-devel, etc), but it appears that the end-goal of 60mb
> (confined by on-board flash space limitations of 64MB) is unattainable

It is pretty uncommon in order to build a bicycle, by starting off with
another wheel-vehicle, say a truck, and then to strip away the unneeded
pieces.

With the ELDK this is just the same, use the other direction, i.e. start
with a minimal system and extend it as neccessary.  An especially nice
starting point is our Root File System Builder which starts off with
only a few megabytes[1].

> due to the huge package (~270MB):
>
>   277036416 bits crosstool-targetcomponents-ppc_4xx
>
> Any pointers?  Is 60MB attainable?  

Depending on your application and the service you use out of ELDK, this
should still be easy.

> Has anyone successfully pruned away the ELDK in this fashion?

I doubt it.

Cheers

(Continue reading)

headers

John Connolly | 5 Oct 2010 18:00

Re: Pruning Filesystem

On Tue, Oct 5, 2010 at 11:42 AM, Detlev Zundel <dzu@...> wrote:
> Hi John,
>
>> My project based on the eldk requires a much smaller footprint than we
>> currently have.  I'm going through the process of hand-removing many
>> packages (*-devel, etc), but it appears that the end-goal of 60mb
>> (confined by on-board flash space limitations of 64MB) is unattainable
>
> It is pretty uncommon in order to build a bicycle, by starting off with
> another wheel-vehicle, say a truck, and then to strip away the unneeded
> pieces.

Understood.  Nice analogy ;D

>
> With the ELDK this is just the same, use the other direction, i.e. start
> with a minimal system and extend it as neccessary.  An especially nice
> starting point is our Root File System Builder which starts off with
> only a few megabytes[1].

Perfect.  This is precisely the starting point I was hoping for.

>
>> due to the huge package (~270MB):
>>
>>   277036416 bits crosstool-targetcomponents-ppc_4xx
>>
>> Any pointers?  Is 60MB attainable?
>
> Depending on your application and the service you use out of ELDK, this

(Continue reading)