Jes Sorensen
I am actually much more concerned about bringing up new systems than
embedded however it is not uncommon to have very limited space to work
in (like 64MB). My point is that the transport process of the kernel
image is painful. Some of the embedded devices or new systems being
brought up may only have serial some do not have network or
floppy. This makes it *very* painful to move things around because you
have to physically move your disk or similar. In particular when
bringing up a system you tend to disable large parts of the kernel in
moi
In other words, a kernel build has a close correlation with actual system
bootstrap processes, where the niceties of the interpreter-du-jour are
irrelvant, as are the percentages or absolute numbers of people that don't
do hard bootstrapping of anything. This is the aspect of low-level code
that utilities used in a kernel build should adhere to, no gratuitous
dependancies. Linux is and always has been hard enough to bring up,
needing as it does a C compiler that needs a C compiler. Somehow the
cuteness of this class of recursion is lost on me.
This is why I wrote and am extending an assembler in Bash. Two
dependancies; a recent unix shell, and an OS. The one-link toolchain.
Rick Hohensee
www.clienux.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:01:01 EST