<snip>
> get the same functionality. 103 sectors free now. Note, don't get
> *too* spoiled by having 103 sectors free, the idea is if I get enough
> free I can try to cram 2.2.19 onto the default image. Note, my current
> thinking is that going from 2.0.39->2.2.19 is much more useful than to
<snip>
I think it would be great if you could squeeze a 2.2.19 kernel into
tomsrtbt. Working with libc5 isn't that bad, at least I managed to compile
some vital apps using the kit on the ftp site, but using 2.0.39 is a royal
pain because the gcc in most distros (like RH 6.2 and anything else in the
last few years) isn't compatable with 2.0.39. There was a unsupported patch
for 2.0.38 for the newer compilers, but somewhere in the 2.0.39 development
this was broken.
Also, like you said, all these new-fangled file systems are coming out right
now and while they all still support the 2.2.x series, I imagine the chances
of seeing a port to 2.0.x are about zilch. Without file tools, tomsrtbt
isn't really that usefull, to me anyway.
Douglas Bollinger
Mt. Holly Springs, PA
My other computer runs Linux.
