Baslinux mailing list

["David Moberg" <davidjmoberg AT lycos.com>]

----- Original Message -----
From: 3aoo-cvfd AT dea.spamcon.org
 
> Andrew wrote:
> >
> > Am I right in thinking the bl3 ssh packet only includes client programs?
> 
> Yes.  BL3 was designed to be a network client, not a
> server.  That includes dhcp, telnet, ftp, pop3, smtp
> and dns.  The one exception is http, for which BL3
> provides both a client and a server.

Busybox httpd, no doubt. And two clients: wget and links.

> With BL1 and BL2 (which have local login), you can
> use the in.telnetd executable from Slackware (it's
> in the tcpip1.tgz package) to provide a telnet login:
> -----------------
> in.telnetd -debug
> -----------------
> That will give you a single remote login.
> 
> However, I have never tried the above on BL3 and expect
> it to fail (because there's no local login capability).
> If anybody decides to experiment with in.telnetd on
> BL3, please report back here with your findings.

If you really wanted to, you could probably add packages
and configure BL3 to be a multi-user system. However, if
you're not worried about security, you could probably
just tell telnet to use ash as the login program. See
the telnetd or sshd manpage and look for the login prog.
option.

> It is only by keeping defaults to a minimum that BL3 is
> able to run on very low-end systems.

And that's one of the reasons why I use BL. "Modern" distros
waste so many resources just to boot the system.

David
-- 
_______________________________________________
NEW! Lycos Dating Search. The only place to search multiple dating sites at 
once.
http://datingsearch.lycos.com