debconf's web frontend

[Seth Cohn]

On Mon, 14 Aug 2000, Joey Hess wrote:

> > Debconf should be able to handle things like that with the 'web' option.
> > If you are remotely installing, you shouldn't depend on an ssh or telnet
> > session staying up.  And vice versa, upgrading a webserver should NOT let
> > you use the 'web' option of debconf.
> 
> Er, debconf includes its own web server. In 256 lines of perl.

Cool, I didn't know that.  So ignore my 'vice versa' there

However, I just read the documentation, and noticed one catch: the client
must be on the same machine (for security purposes).  While this will
still solve the disconnect problem (if your ssh/telnet dies, you
can reconnect and still run lynx/whatever) it's not the solution I was
suggesting (ie, if your box stops answering ssh/telnet ports, you can't
continue configuring it, and it's a trip to the console)

> (Shittiest web server on earth too, btw.)

I thought M$ IIS was :)  At least it's a bit heavier a pile of ....
how big a pile can 256 lines be?

Seth






--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]