64mb of space for 'disk' ? You aren't compiling the kernel anyhow without
some serious mucking around.
> 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.
And you think that trying to transport the kernel srcs + userland
will save you time in the long run? If you have to physically move
your disk to initially put userland on, you can put on python too. Or
go and run the 'freeze' schitt on it and have the C version. What kind
of 'new' systems are you talking about? I'm biased I guess since I'm
used to working on documented hardware. So documents + time + good hw
debugger tend to help things along.
> >> And introduces new problems that so far haven't been addressed.
>
> Tom> Which is what? The dependancy on python2?
>
> Yes
Because with the exception of your unique situation in which you have
a machine which is stable enough to compile a kernel on and develop
but can't run python, it's not a problem.
-- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - 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/