Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-12-01 Thread Erich Titl
Nathan
Nathan Angelacos wrote:
On Tuesday 30 November 2004 08:07, Erich Titl wrote:
 

Nathan
Would you consider to split off haserl and pwcrypt  from webconf.lrp.
IMHO this would make webconf extremely portable.
   

Erich,
My first reaction was "but that's what makes it go!  Its like removing pluto 
from ipsec.lrp or pppd from ppp.lrp!"  But I think I understand your  
concerns, - you'd like to use webconf.lrp on another platform without having 
to repackage webconf.lrp
 

Right.
I wonder if the lwp mechanism would work:
What if you create a wc-207.lwp with haserl and pwcrypt for glibc 2.0.7, and 
then add wc-207 to the LWP variable in /etc/webconf/webconf.conf?

That means the webconf init script would pull in the correct haserl and 
pwcrypt binaries for your platform. 

Would that work?
 

Sounds like it might do the trick, I will have to pull your latest 
webconf and see what that would do

Thanks
Erich

---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-12-01 Thread Nathan Angelacos
On Tuesday 30 November 2004 08:07, Erich Titl wrote:
> Nathan
>
> Would you consider to split off haserl and pwcrypt  from webconf.lrp.
> IMHO this would make webconf extremely portable.

Erich,

My first reaction was "but that's what makes it go!  Its like removing pluto 
from ipsec.lrp or pppd from ppp.lrp!"  But I think I understand your  
concerns, - you'd like to use webconf.lrp on another platform without having 
to repackage webconf.lrp

I wonder if the lwp mechanism would work:

What if you create a wc-207.lwp with haserl and pwcrypt for glibc 2.0.7, and 
then add wc-207 to the LWP variable in /etc/webconf/webconf.conf?

That means the webconf init script would pull in the correct haserl and 
pwcrypt binaries for your platform. 

Would that work?


---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-30 Thread Erich Titl
Nathan
Nathan Angelacos wrote:
On Tuesday 16 November 2004 04:06, Luis.F.Correia wrote:
 

To make webconf a full weblet replacement, there are some things to
enhance:
- add 'pretty shorewall logs'
   

The version in CVS now has an attempt at parsing the shorewall logs.  My 
initial reaction was "pretty firewall formatting belongs in shorwall.lwp, not 
in basic webconf"   But... I'm not opposed to the idea /that/ much.   In this 
version, parsing of the shorewall logs is done via a sed script.   

There's a new column called "Formatted" that shows the parsed version of the 
log.  I guess if there's pretty formatting to be done for other logs, it 
could go in that column. (parsed ipsec logs, anyone?)

Let me know what you think.   If most think the original parsefw belongs in 
webconf.lrp, then I'll put it in.
 

Would you consider to split off haserl and pwcrypt  from webconf.lrp. 
IMHO this would make webconf extremely portable.

cheers
Erich

---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-29 Thread Nathan Angelacos
On Tuesday 16 November 2004 04:06, Luis.F.Correia wrote:
>
> To make webconf a full weblet replacement, there are some things to
> enhance:
>
> - add 'pretty shorewall logs'

The version in CVS now has an attempt at parsing the shorewall logs.  My 
initial reaction was "pretty firewall formatting belongs in shorwall.lwp, not 
in basic webconf"   But... I'm not opposed to the idea /that/ much.   In this 
version, parsing of the shorewall logs is done via a sed script.   

There's a new column called "Formatted" that shows the parsed version of the 
log.  I guess if there's pretty formatting to be done for other logs, it 
could go in that column. (parsed ipsec logs, anyone?)

Let me know what you think.   If most think the original parsefw belongs in 
webconf.lrp, then I'll put it in.

> - simplify log file viewing by not opening a separate window

Done.

Enjoy!


---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


RE: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-16 Thread Luis.F.Correia
 
Hi!

> -Original Message-
> From: Nathan Angelacos [mailto:[EMAIL PROTECTED] 
> >
> > - add 'pretty shorewall logs'
> 
> You mean the table format (parsefw)?  or is there more?

Yes, it is the parsefw thinghy...

> 
> > - simplify log file viewing by not opening a separate window
> >
> 
> I was surprised this didn't get mentioned long before this.   
> I'll fix it soon.

Thanks!

> >
> > Opinions may differ from mine ;)
> 
> I think silence is agreement, right?   
> Thanks for your comments!

No problem!

Luis Correia   
Bering uClibc Team Member

PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 
Key Server: http://pgp.mit.edu


---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-16 Thread Nathan Angelacos

On Tuesday 16 November 2004 04:06, Luis.F.Correia wrote:
>
> To make webconf a full weblet replacement, there are some things to
> enhance:
>
> - add 'pretty shorewall logs'

You mean the table format (parsefw)?  or is there more?

> - simplify log file viewing by not opening a separate window
>

I was surprised this didn't get mentioned long before this.   I'll fix it 
soon.
>
> Opinions may differ from mine ;)

I think silence is agreement, right?   
Thanks for your comments!



---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


RE: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-16 Thread Luis.F.Correia

Hi!

> -Original Message-
> From: Nathan Angelacos [mailto:[EMAIL PROTECTED] 
> Sent: Monday, November 15, 2004 7:00 PM
> To: [EMAIL PROTECTED]
> Subject: [leaf-devel] Suggestion to break up webconf.lrp into 
> lrp and lwp parts
> 
> Thanks for all the positive feedback on webconf so far.  There is a 
> suggestion that webconf.lrp (core) be just a weblet 
> replacement, and the 
> current "expert" menu set be moved into webconf.lwp.

To make webconf a full weblet replacement, there are some things to 
enhance:

- add 'pretty shorewall logs'
- simplify log file viewing by not opening a separate window


Opinions may differ from mine ;)


Luis Correia   
Bering uClibc Team Member

PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 
Key Server: http://pgp.mit.edu


---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-16 Thread Erich Titl
KP

At 00:12 16.11.2004 +0100, K.-P. Kirchdörfer wrote:
>Hi Erich;
>
>maybe I do not understand, maybe you made a typo - but that's what 
>proposes IMHO.

I should learn how to read

sorry for the noise

Erich

THINK 
Püntenstrasse 39 
8143 Stallikon 
mailto:[EMAIL PROTECTED] 
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16




---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-15 Thread K.-P. Kirchdörfer
Am Montag, 15. November 2004 23:32 schrieb Erich Titl:
> Nathan
>
> Nathan Angelacos wrote:
> >Thanks for all the positive feedback on webconf so far.  There is
> > a suggestion that webconf.lrp (core) be just a weblet
> > replacement, and the current "expert" menu set be moved into
> > webconf.lwp.
> >
> >The reason is situations where an admin wants to give a customer
> > "read-only" rights to web pages for monitoring; but the customer
> > shouldn't have access to "fix" [pronounced: break] the installed
> > router.
> >
> >This makes sense to me; it means webconf.lrp is the replacement
> > for weblet; webconf.lwp is the value-add for most
> > "do-it-yourself" SOHO users; and extra .lwp's add further
> > functionality.
> >
> >Here's a proposed breakup of the existing webconf.lrp (beta 2)
> >
> >keyboard.lwp  -> keyboard.cgi (basic menu set)
> >dropbear.lwp  -> dropbear.cgi (basic menu set)
> >webconf.lwp   -> lrcfg.cgi (expert configuration pages)
> >  -> lrcfg.pkgdisks.cgi ("Destinations")
> >  -> leafcfg.cgi (Edit leaf.cfg )
> >webconf.lrp   -> (all the framework, lib, css, etc)
> >  -> connection-info.cgi ( Active Connections)
> >  -> general-info.cgi (General Health)
> >  -> logfiles.cgi (Log Files)
> >  -> lrcfg.back.cgi (Backup Packages)
> >  -> wc-passwd.cgi (Webconf password)
>
> Wouldn't you think dropbear.cgi and keyboard.cgi belong to
> dropbear.lwp and keyboard.lwp, especially for keyboard-less boxes.
>
Hi Erich;

maybe I do not understand, maybe you made a typo - but that's what 
proposes IMHO.

kp


---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Suggestion to break up webconf.lrp into lrp and lwp parts

2004-11-15 Thread Erich Titl
Nathan
Nathan Angelacos wrote:
Thanks for all the positive feedback on webconf so far.  There is a 
suggestion that webconf.lrp (core) be just a weblet replacement, and the 
current "expert" menu set be moved into webconf.lwp.

The reason is situations where an admin wants to give a customer "read-only" 
rights to web pages for monitoring; but the customer shouldn't have access to 
"fix" [pronounced: break] the installed router.

This makes sense to me; it means webconf.lrp is the replacement for weblet; 
webconf.lwp is the value-add for most "do-it-yourself" SOHO users; and 
extra .lwp's add further functionality.

Here's a proposed breakup of the existing webconf.lrp (beta 2)
keyboard.lwp  -> keyboard.cgi (basic menu set)
dropbear.lwp  -> dropbear.cgi (basic menu set)
webconf.lwp   -> lrcfg.cgi (expert configuration pages)
 -> lrcfg.pkgdisks.cgi ("Destinations")
 -> leafcfg.cgi (Edit leaf.cfg )
webconf.lrp   -> (all the framework, lib, css, etc)
 -> connection-info.cgi ( Active Connections)
 -> general-info.cgi (General Health)
 -> logfiles.cgi (Log Files)
 -> lrcfg.back.cgi (Backup Packages)
 -> wc-passwd.cgi (Webconf password)
 

Wouldn't you think dropbear.cgi and keyboard.cgi belong to dropbear.lwp 
and keyboard.lwp, especially for keyboard-less boxes.

Erich

---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel