RE: [leaf-devel] Project Description & Goals
On Thu, 2004-01-15 at 14:14, Peter Mueller wrote: > An easy-to-use Embedded Linux Network Applicance; LEAF, like Linux, aims to > be scalable to all environments. I don't see the added value in LAN/WAN > talk, although WLAN might add some relevance. Everyone, Does this sound any better? A Linux Embedded Appliance Framework delivered in easy-to-use branches. Specific branches target a variety of environments. Anything from enterprise networks and Internet service providers to small office/home office environments are supported. (244 characters) -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] Project Description & Goals
>An easy to use embedded Linux network appliance for use in small >office, home office, and home automation environments. >to: >An easy to use embedded Linux network appliance for use in LAN, WAN, >and WLAN environments. What about: An easy-to-use Embedded Linux Network Applicance; LEAF, like Linux, aims to be scalable to all environments. I don't see the added value in LAN/WAN talk, although WLAN might add some relevance. Cheers, Peter M --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Project Description & Goals
On Thu, 2004-01-15 at 13:19, Mike Noyes wrote: > On Thu, 2004-01-15 at 12:40, Ray Olszewski wrote: > > But my reaction comes without knowing the reason why a change is even being > > considered. Did I somehow miss a recent thread here in which this topic was > > "brought up again"? Or are you (Mike) getting off-list requests for revisions? > > Ray, > Yes. Some people want to move away from the SOHO definition to a broader > interpretation. This was discussed as a possibility in the past, but > wording was never agreed to. Ray, The other description change under consideration was a move away from firewall to something like framework. -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Project Description & Goals
On Thu, 2004-01-15 at 12:40, Ray Olszewski wrote: > But my reaction comes without knowing the reason why a change is even being > considered. Did I somehow miss a recent thread here in which this topic was > "brought up again"? Or are you (Mike) getting off-list requests for revisions? Ray, Yes. Some people want to move away from the SOHO definition to a broader interpretation. This was discussed as a possibility in the past, but wording was never agreed to. My attempt above was very poor. Sorry. It didn't convey the intended change. I'm open to suggestions. > Personally, I like the existing wording just fine. I like the new proposed goals better than our current ones. We've completed most of our current ones. I believe it's our description that people wish to work on. It's very hard to write a good description in 255 characters. Current goals: Create an inclusive environment for current developers of the Linux Router Project to release their modifications to the public. Support continued development of Linux Router Project derived LEAF images and packages. Create a new LEAF version based on an embedded Linux distribution with 2.4 kernel support, while retaining the option to install the target environment on a floppy attached to the target. Proposed change: Create an inclusive environment where LEAF project members and the extended community are free to release content to the public. Support continued development of current LEAF releases/branches. Create new LEAF releases/branches with current Linux kernels and libraries, while retaining the option to install the target environment on various devices attached to the target. Maintain as small a footprint as possible for release/branch target installations. Promote creation of packages usable by all LEAF releases/branches. Note: I don't want to change our goals while a change to our description is being considered. I only want to approach the SF staff once. -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Project Description & Goals
At 12:08 PM 1/15/2004 -0800, Mike Noyes wrote: Everyone, The subject of our current project description and goals was brought up again. I'd like feedback on the state of the new version I posted here: Description https://sourceforge.net/docman/display_doc.php?docid=1396&group_id=13751 I think this sentence should change from: An easy to use embedded Linux network appliance for use in small office, home office, and home automation environments. to: An easy to use embedded Linux network appliance for use in LAN, WAN, and WLAN environments. Why make this change? I don't know what the revised sentence is intended to convey. Really, any device that contains a NIC is "for use in LAN, WAN, and WLAN environments" ... making this new description not very ... well, not very descriptive of anything. The second sentence (not quoted above) identifies the main everyday use of LEAF quite nicely, without restricting us to routing and firewalling uses. But my reaction comes without knowing the reason why a change is even being considered. Did I somehow miss a recent thread here in which this topic was "brought up again"? Or are you (Mike) getting off-list requests for revisions? Personally, I like the existing wording just fine. Keep in mind, any change to our project description and goals must be approved by the SF.net staff. --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Project Description & Goals
Everyone, The subject of our current project description and goals was brought up again. I'd like feedback on the state of the new version I posted here: Description https://sourceforge.net/docman/display_doc.php?docid=1396&group_id=13751 I think this sentence should change from: An easy to use embedded Linux network appliance for use in small office, home office, and home automation environments. to: An easy to use embedded Linux network appliance for use in LAN, WAN, and WLAN environments. Keep in mind, any change to our project description and goals must be approved by the SF.net staff. -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] [leaf-user] ANN: Bering-uClibc 2.1-rc1
Today, January 15th 2004, the Bering-uClibc team releases Bering-uClibc 2.1-rc1 As usual it can be downloaded from the FRS area: http://sourceforge.net/project/showfiles.php?group_id=13751&package_id=67534 This is the first release based on linux kernel 2.4.24. The packages and modules touched by the kernel version change are updated. Additionally dropbear and shorewall has been upgraded to latest version plus a reworked modutils script (provided Eric Wolzak). For a complete changelog please read http://leaf.sourceforge.net/mod.php?mod=userpage&menu=91003&page_id=39 If you like to only update the kernel, a few hints what has to be done for a Bering-uClibc 2.0/2.0.1 system: Replace the current kernel (linux), the modules.lrp (and if needed add packages from the Bering-uClibc 2.4.24-modules tarball) and iptables.lrp. For users who are using wireless and/or pcmcia (+ base instructions): Update the wireless, wireutil and pcmcia packages from cvs For users with ipv6: Replace the current kernel (linux), the modules.lrp (ipv6 version of course) (if needed add moduleses from the Bering-uClibc 2.4.24-modules tarball) and ip6table.lrp We ask everyone to test this release and report bugs on leaf-user list. thx for your attention kp --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
