[leaf-devel] Webconf Development
Don't know if this made to the list of not. Seems I slipped up and left the privacy crap that work email system puts on messages. I registered my home email on the list so that doesn't happen again. Sorry. I couldn't sleep last night, so I spent the time productively; thinking about Webconf and automating Bering in general. Some of the things I thought we will need to EVENTUALLY get working is the detection and installation of network interfaces. That seems to be the first big hurdle for new LEAF users. They don't know what kind of NICs they have, or don't know what module to use. Automatically detecting and installing the network interfaces would get these people over the first big hurdle. This shouldn't be too huge an effort, because distributions such as Damn Small Linux do it now. No need to reinvent the wheel. Just work from the shoulders of those who have done this already. Another, and I should think easier task, would be to automate a very basic setup of Shorewall. Detect the number of interfaces and setup eth0 as the untrusted side, eth1 as trusted, and eth2 if it exists as a DMZ (although anyone with a DMZ should know enough to do this amount of setup). Such a setup could provide multiple levels of user selected restriction, dare I say it, like Windows. Of course this is just to get the user started. A more detailed Shorewall page would help provide more granular control. The last idea was to provide a first page that let the user select the packages needed by a description of the function not by package name. The user would select the functions needed and the packages would be added to Webconf to setup. These are just thoughts I,m tossing out there. I'm not trying to get the cart before the horse. I realize that we need to get Webconf working as currently designed before, we go and try to do so much automation. If others think any of these ideas worth pursuing, I will be glad to work on them. For now I thought I'd start small and start work on dhcpd and dnsmasq, unless someone is already working on them. --- 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 leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Webconf Development
I couldn't sleep last night, so I spent the time productively; thinking about Webconf and automating Bering in general. Some of the things I thought we will need to EVENTUALLY get working is the detection and installation of network interfaces. That seems to be the first big hurdle for new LEAF users. They don't know what kind of NICs they have, or don't know what module to use. Automatically detecting and installing the network interfaces would get these people over the first big hurdle. This shouldn't be too huge an effort, because distributions such as Damn Small Linux do it now. No need to reinvent the wheel. Just work from the shoulders of those who have done this already. Another, and I should think easier task, would be to automate a very basic setup of Shorewall. Detect the number of interfaces and setup eth0 as the untrusted side, eth1 as trusted, and eth2 if it exists as a DMZ (although anyone with a DMZ should know enough to do this amount of setup). Such a setup could provide multiple levels of user selected restriction, dare I say it, like Windows. Of course this is just to get the user started. A more detailed Shorewall page would help provide more granular control. The last idea was to provide a first page that let the user select the packages needed by a description of the function not by package name. The user would select the functions needed and the packages would be added to Webconf to setup. These are just thoughts I,m tossing out there. I'm not trying to get the cart before the horse. I realize that we need to get Webconf working as currently designed before, we go and try to do so much automation. If others think any of these ideas worth pursuing, I will be glad to work on them. For now I thought I'd start small and start work on dhcpd and dnsmasq, unless someone is already working on them. Best Regards, Roger McClurg [EMAIL PROTECTED] This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --- 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
[leaf-devel] Webconf Development
I have been a user of LEAF variants since early Eigerstein. For years I have been taking from this community. I would like to be able to give something back. I don't know if I need to be an official developer or what. I am open to suggestions. I was in the process of putting together a web GUI for LEAF when the announcement of Webconf came up. I am certain that Webconf is a far better approach than what I was thinking of. Since Webconf is already defined, I thought that I might be able to help in developing LWPs. I was wondering who was currently working on LWPs and which ones they are working on. If there is a particular LWP that needs attacking, I'd be glad to give it a shot. Please let me know what you think. Roger McClurg --- 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] Webconf Development
Hi Roger, On Thursday 16 December 2004 10:16, Roger E McClurg wrote: thought that I might be able to help in developing LWPs. I was wondering who was currently working on LWPs and which ones they are working on. If there is a particular LWP that needs attacking, I'd be glad to give it a shot. Please let me know what you think. I think that's great! I don't know of any particular packages that are being worked on. There are people working on packages, but it seems like they are doing them for specific niches. I have some work done on the interfaces file, but other than that, I don't know of any other packages that have any work done on them. If you wat to be a developer, Mike Noyes can set you up. If all you want is a place to put your creations, I'll be happy to host your work under the webconf cvs tree until things with the new website settle down again. --- 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
