[BusyBox] Division of work.

[Vladimir N. Oleynik]

Glenn,

> Well, busybox started out as an internal debian project for the
> installer.
> My primary reason for working on busybox is to develop ways for using it
> in the new installer that is being developed. I hape to have a small
> static busybox initrd that can unpack .deb packages to create the root
> filesystem on a virtual memmory fs (shmfs/tmpfs)

And you did not reflect, what these .deb packages can lay in a network? 
Then it will be necessary for you to support pppd, any environment for program
management above wget or ftp or God forbid smbclient. 
I already am afraid to mention about secure the moments (for example about
scp).   

> If more distributions use busybox then that will be good for busybox.
> Im not really familiar with slackware, havent installer it for years, im
> not familiar with the development proccess for slackware either, is it
> open ?

I not in course. Though it is my idea-fix, I realize, that I am not ready to
offer any solution for Slackware instalator as it is based on rather unpleasant
thing for busybox - the big set must of utilities to be completely we compose 
to complete documentation on these utilities as the complete analysis 
for incompatibility on options between busybox-applets and GNU-utils 
is extremely heavy..
 
> uClibc is a real space saver for me, i love it.
> 
> Im sure you like saving space as well, so i assume you dislike it mostly
> for technical reasons, i dont care so much about this, i just care that
> it works.

I see senselessness to have static busybox when one additional utility which
behind itself will pull glibc is necessary even, locale, nss, pam. 
Therefore I seriously can not concern to idea uclibc.  


--w
vodz