>:>I'll be brief and say the Hardhat tools are insufficient.
>Sigh. Feel free to enlighten me. Here are some of the issues I've
>had with Hardhat TCT (2.0 release). Hardhat support has acknowledged
>them and suggested that I fix them by hand, which I've done for most
>of the cases. But it's not what I was hoping for from their tools.
Maybe you are requesting too much? Tools like the MV Target
Configuration Tool will always be less efficient than an expert...
Quote:> Specifying the netbase package, which includes little essentials
> like /etc/services, drags in PERL at a total cost of 16 MB.
This is one of the general problems of all these tools: they have to
groupt tools into packages, and the unavoidable dependencies will
blow up the total size beyound what is really needed for _your_
specific target system.
Quote:> The initscripts package includes startup scripts that don't play
> well with some of the busybox utils. Some of these scripts
> aren't really appropriate for a ramdisk based system anyway.
The SYSV init concept is more or less complete overkill for most
embedded systems; don't use it, then. Busybox can easily do without
Quote:> Several of the packages I need contain large elements I don't
> need. I'm going to have to do a lot more hand work to really
> trim the elements down to the minimal files needed to support
> our application.
This is the wrong approach anyway. When you have to try to "trim" any
existent configuration you have already lost. In my experience, the
only reliable way is to start with an EMPTY system and just adding
the parts that are necessary for your target - but on a by-file base,
You have two options:
* Either you are a beginner who doesn't know how to buils an embedded
configuration; then you can use tools like MV's TCT which will
result in a system that most probably will be working, at the cost
of some overhead. If you want to optimize this system, hire an
* If you know what you need, then don't use such tools, just build
the system with the minimum of necessary files manually. This is
the only way to give you complete controll over what you are doing.
Quote:>Reading over what I've just written, I realize that I could solve
>some of my issues by scrapping TCT and just managing content via
The standard RPMs cannot be used if you want to build an optimized
system (minimum memory footprint).
You have to trade off memory footprint against effort spent on
configuring the system; the easier the configuration the bigger the
Quote:>On the other hand I have no complaints with the kernel they provided.
>: Maybe our SELF (Simple Embedded Linux Framework) is more to your
>: liking; see ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/
>The README (and the related website) look intriguing.
At least if gives you complete controll about the things you add - at
the cost of missing tool support for the configuration part.
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Web: www.denx.de
If I had to live my life again, I'd make the same mistakes, only
sooner. -- Tallulah Bankhead