My spouse had the problem of creating a bootable copy of A/UX on a single floppy. She decided to write a "doitall" program that had functionality from a number of small commands. This amortized the overhead a great deal.
A similar approach could be used for /(s)bin: lump several programs together into a single binary, but give the binary links for each of the original names (and have the program respond according to the name used, ala vi/ex). My general reaction, however, is that this issue (shrinking sbin) is not worth trashing the software engineering of piles of commands. -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm - my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
