> Meanwhile, I discovered another problem... it appears that lilo might
> need to be upgraded.
The problem is that the lilo version and the boot.b version have to
exactly match. Therefore, there is no right version for all systems.
Do something like:
chroot /mnt /sbin/lilo
in order to run the lilo on your system against the boot.b on your system.
If the boot.b or lilo on your system is damaged, you will have to copy the
tomsrtbt boot.b or otherwise reference it in the lilo.conf, in order to
use the tomsrtbt lilo.
There is no way to just do "lilo -r /mnt", since you will then be running
the tomsrtbt lilo against your systems boot.b.
> The other thing I want to mention is that sooner or later you will
> _have_ to take it to glibc2.0/2.1.
I encourage someone to do this for me... There are 2 problems:
(1) Glibc6 is bigger. Significantly bigger. To do this, I must research
and pursue many ways to make it as small as possible, perhaps manually
hacking out some stuff, and cetera. Big job.
(2) All programs need to be recompiled. Work done to make them as small
as possible must thus be re-done, across the entire diskette. This is a
logical time to review whether versions need to be upgraded. Big job.
> It's proving to be very
> inconvenient to use tomsrtbt to work with any redhat 5.x/6.0 systems.
> Yes, I know your views about this and that you have good reasons for
> staying with libc5, but I'm just saying this again anyway :)
Well, you only have to figure out how to compile a libc5 executable on a
glibc system once. There are apparently a few ways to do it. Until then,
learn how to use chroot. A chrooted shell from tomsrtbt should pick up
the glibc libraries and executables. The only *real* problem is when you
want to *add* something to tomsrtbt, for use on systems *without* a glibc
filesystem. It is NOT, repeat, *NOT* a problem to run glibc6 executables
on your hard drive from tomsrtbt. Just use chroot.
-Tom
