> parted  <www.gnu.org/software/parted/>
>         Then we could use your diskette to repartition our drives

Put parted on a second floppy.  I already include rescuept and fdisk, the
size of parted is prohibitive especially as rescuept and fdisk meets the
need for recovery functionality.  Normal (non-rescue) maintenance is not
in the design goals, it is intended that tomsrtbt be sitting around for
the *un-predicted* needs.  If you know you want to repartition your drive,
you can make a custom tomsrtbt with parted on it, easily, given the luxury
of a working system.  There are not so many situations where you could
recover with parted but not with rescuept and fdisk, so parted is just not
going to make it into the default set of stuff.  Parted is also, by the
way, not only large, it is unfriendly in environment requirements.  Just
try to get it to work with the version of the ext2fs libraries and c
libraries on tomsrtbt, you will see that GNU is assuming it will be run on
an everything-at-the-latest version system with no resource constraints.
In my opinion, parted is not well designed for rescue distributions.
Parted + libparted + ncurses, even stripped, is going to add about 500K to
any rescue floppy.  Parted itself is only 150K, but libparted is 250K, and
ncurses (which is not already on tomsrtbt) is over 200K now.  And to TOP
all of that, it requires a newer larger libuuid.  Basically, you might as
well just make a statically linked parted, and put it on its own floppy.

> recover <www.linuxave.net/~recover/>
>         If we accidentally have deleted a file

This one is at least conceivable, I'm not sure it will make the cut, but
I'll at least try to build a libc5 with libm statically linked and put it
in the add-ons.

> zile    <web.tiscalinet.it/ssigola/sandro/>
>         A smaller emacs clone than the one on your disk

This I will definitely look into!  Thanks!

-Tom

Reply via email to