Re: disabling unnecessary perl modules

I'll echo what others have said: Why do you want to spend more in time to find an optimal build than it would cost for a bigger hard drive? You are talking about saving a couple of MB at best. If that amount of space is really a problem then delete one of the mp3's that you never listen to.

It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

Comment on Re: disabling unnecessary perl modules

Replies are listed 'Best First'.
Re^2: disabling unnecessary perl modules by samithawijedasa (Initiate) on May 30, 2014 at 02:21 UTC
Hi, this is for a embedded system where the root file system is restricted to a limited capacity on a NAND as a design specification	[reply]
Re^3: disabling unnecessary perl modules by boftx (Deacon) on May 30, 2014 at 02:43 UTC
Given that information (and being no stranger to embedded systems, albeit back in the bad old days when a 32k EEPROM was cutting edge) is it reasonable to store most of the file system as a compressed image and then extract to RAM on boot-up if you can take the hit in start-up time? What are the cost factors and trade offs? It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.	[reply]