>
> > I'd rather not support this for a couple of reasons:
> > 1) It's a security hole.
> Have it password protected (require a login).
> > 2) You should be able to do everything you need to do with the
> GUI/startup
> > script combination. If you can't then I need to make it so you can.
> If STN is ever improved so that additional programs can be run on
> the STN box, I will need more than the GUI can offer.
> > 3) You can already get to a command like if you have physical
> access to the
> > machine.
> My STN box doesn't have a monitor/keyboard hooked up, and it is
> a big hassle to do so (it's on a shelf with its back to the wall).
> >
> > What do you need to do at the command line?
> As I said before, if STN supports additional progs, I would need the
> command line to execute and configure them.
>
Hi Webmaster (the only name I have for you),
The purpose for STN is not to create a generally useful Linux
distribution -- if you wan that, then you should use RedHat, Caldera et al.
If you want a general distribution that fits on a diskette, then you should
either use the freeware version of STN or LRP. STN is supposed to be simple
to use, and any time you add a command line, it's more difficult than the
average STN user wants. The problem with adding the command line is it has
to be supported. The debug option is bad enough. Realistically, I'll
probably remove the debug option before I'll create a telnet-in option.
All that being said, there's nothing stopping you from adding in.telnetd
from your redhat 4.2 distribution (for the correct libraries) to a STN
diskette. I'd be happy to give you any information you require to make this
happen -- it's fairly simple if you have Linx knowledge.
Regs,
John
_______________________________________________
ShareTheNet maillist - [EMAIL PROTECTED]
http://www.webserv.com/mailman/listinfo/sharethenet
