Will 2.6 require Python for any configuration ? (CML2)
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
Quoted 8 lines · Rick Hohensee
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.
Yes, Linux does have a nice chicken-and-egg process. But unless you're building a brand new arch, which means you have to fix glibc and gcc and binutils to know about you, throwing in python isn't going to hurt you. And if you're trying to do this on the machine you're trying to make supported, you're going to have lots of fun. In other words, I don't see this as an issue. If you're talking about bringing up a new board for supported platform X, the only issue is getting Python2 onto the system. Which isn't nearly as painful as getting the kernel source, glibc or gcc will be. It'll only be maybe twice as painful as getting the bash sources over (2.05) even. :)
Signature · 2 lines
Tom Rini (TR1265) http://gate.crashing.org/~trini/