Re: [leaf-devel] WISP-Dist
Darrin Eden wrote: Hello LEAF Development Crew, I'm just beginning to get my head wrapped around the scope of what you folks have been working on for the past few years. You've done a ton of work so please excuse my naivety. I've started to compare[1] WISP-Dist against Pebble[2] in an attempt to understand the strengths of the various free software dedicated to wireless embedded devices and the value that these may bring to community wireless networks such as the PersonalTelco project in my hometown of Portland, Oregon. I am reading furiously but I would be most appreciative if a team member would care to introduce me to the organization of the WISP-Dist project and its relation to LEAF; especially concerning the build and package management architectures? Well, all I can say that WISP-Dist is quite different, especially in the networking and packages. However, it is backwards compatible with LRP packages, provided they do not rely on network initialization system as done in Bering. NoCatAuth and its successor NoCatSplash[3] are such core functions of community wireless networking that I'd like to hear your take on how it may be integrated and if you could use more development help for embedded wireless where is the first point to focus? I don't think there would be a problem to integrate NoCatSplash. I already use WISP-Dist for hotspots but unfortunately have to keep the hotspot implementation closed. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] ML volume
Mike Noyes wrote about "Re: [leaf-devel] ML volume": > > Everyone, > > Is this solution acceptable? If so, I'll create release/branch specific > > lists upon LEAF release/branch lead developer request. > > +1 to Ray's solution. You didn't count me in yet? :) -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] ML volume
> How hard is it to subscribe to the list, ask questions, get the problem > resolved and un-subscribe? I'd like to see consistant feedback from existing users, not only when they experience a problem. Because of this, I don't want them to unsubscribe. In order for that to happen, content of the mailing list should be of general interest to WISP-Dist users. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: Light a candle, curse the glare (was: Re: [leaf-devel] ML volume)
Mike Noyes wrote about "Re: Light a candle, curse the glare (was: Re: [leaf-devel] ML volume)": > Ray, > One of our project members sent me a message off-list expressing a > concern over leaf-user list volume. I have no idea how many of our users No need to keep it secret - that developer was me. I receive about 50% of my support requests via e-mail. That's not much and the total traffic would be much lower than leaf-user's. However, I don't want to force those people to subscribe to the mailing list and at the same time I don't like to answer the same questions again. > > All of that is a Baid-Aid, though. The real question that needs to be asked > > is how the people who *answer* requests for help want to do it. That's > > mainly the branch lead developers; a few branch-agnostic developers like And the reason might be because knowledgeable users unsubscribe from the mailing lists due to lack of time to wade through high traffic. If the traffic would have been lower they would stay on the list and provide answers on a "day-in-day-out" basis. At least that's the case with me - in case of high traffic lists I usually just subscribe, send my question, wait for answers, and then leave. However, in case of low traffic lists, I usually don't mind staying and answering questions myself as time permits. > > Personally, my interest here is in helping people who want to develop their > > own skills and knowledge, people who will some day cross to the other side > > of the line and become the next generation of developers, troubleshooters, > > and the like. People like many of you here on leaf-devel. In contrast, > > people who want only to consume Open Source software do not interest me as > > much, and they can turn to paid sources of support, buy closed source > > products like Linksys routers, or endure the inconvenience of having to > > read (or delete) "too many" messages. This interest leads me to favor a > > general list like leaf-user, which has the virtue of exposing its > > subscribers to a wide range of LEAF and routing problems, not just offering > > a source of free, personal tech support. My reasons for publishing WISP-Dist were different, though. First is to share benefits that I get from Open Source software, and secondly, to help people roll out broadband access to Internet where it is not currently available. I agreed to join LEAF project because I hoped that it would help present WISP-Dist to a wider audience. I don't have a problem giving support to people who don't have a lot of free time or knowledge - if their questions are reasonable, of course. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] ML volume
Mike Noyes wrote about "Re: [leaf-devel] ML volume": > Vladimir, > If we decide to create release/branch specific lists, I will create one > for each of our releases/branches. It's the only fair thing to do. Mike, depends on how you view it. If we treat mailing lists as some kind of benefits to the branch authors, then yes, we need to be fair and everybody should have the same benefits. I wouldn't treat them like that. I'd rather treat mailing lists as a tool for communication and their splitting as a way to reduce load on the readers. As for web-based forums - personally I don't like them because they're inconvinient. Especially considering that I have 500+ ms ping to Sourceforge. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] ML volume
Michael D. Schleif wrote about "Re: [leaf-devel] ML volume": > Add to d) leaf-general, or some such. If this is divvied up to fine, > then how will the generalists lend support? I have a feeling that nobody will subscribe to it. IMHO you need to make lists for branches which have big differences from each other. I see at least two: Bering and WISP-Dist. From what I understand Bering is mostly backwards compatible with Dachstein, so maybe same mailing list can be used for both Bering & Dachstein. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] ML volume
Mike Noyes wrote about "[leaf-devel] ML volume": > Everyone, > It has come to my attention that our leaf-user list volume is > discouraging some/many users from using it. We have a variety of options > to address this issue. I'd vote for separate mailing lists, at least for WISP-Dist. Apart from other reasons it is also hard for me to keep with all the traffic in leaf-user and basically what I do is filter out all messages which have "wisp" inside them and read the rest of leaf-user as time permits. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] FRS pseudo-directory structure
Mike Noyes wrote about "Re: [leaf-devel] FRS pseudo-directory structure": > K.-P., > The end of my message was just an example of our current system to > clarify my proposed change. I guess it didn't successfully achieve my > desired goal. I apologize for confusing the dialog. > > One vote for omitting node3 from our future FRS releases. Looks useless to me as well. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] WISP and Atmel AT76C503A
Jaime Nebrera Herrera wrote: There shouldn't be a problem to integrate it. I know that linux-wlan-ng supports it (in client infrastructure mode) and support form hostap_cs is coming. Sorry for my ignorance, but know ver few about wireless technology. What do you mean by "in client infrastructure mode"? Can I use it as an access point? Client mode means as a client to an Access Point. What is hostap_cs? hostap_cs is a driver which let's you use the card as an Access Point. We are thinking about one of those "wireless community projects". I guess this means working as an AP for wireless clients and at the same time talking with other "routers" to propagate the signal and internet access. Can this be achieved? Yes, however only with hostap_cs driver with USB patch. I heard that it is going to be released in a few weeks. Other solution is to use linux-wlan-ng with tertriary firmware, but this firmware is not free (from what I heard license from Intersil costs about $20k). -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] WISP and Atmel AT76C503A
There shouldn't be a problem to integrate it. I know that linux-wlan-ng supports it (in client infrastructure mode) and support form hostap_cs is coming. Jaime Nebrera Herrera wrote: Hi all, A quick and easy question, does WISP support an Atmel AT76C503A based USB wireless devices? We are preparing an offer based on that board. If its not directly supported but could be integrated (the tools and code are there), if the offer is approved we could "donate or pay" for such a feature. Thanks in advance. Regards. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project
You may want to look into using CramFS like WISP-Dist does. You will save RAM on this. Jaime Nebrera Herrera wrote: > Hi all, > > We are developing a Bering evolution focused in Compact Flash or DOM > systems. Yes, Bering is great, but sticking to the floppie paradigma poses > some limitations to its functionallity. Yes, you can do this adding more > floppies into the equation but its not a practicall solution. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Kernel sources for Wisp-Dist 2348?
Yes. You know any other drivers which don't require closed tertriary firmware? Dominik Strnad wrote about "RE: [leaf-devel] Kernel sources for Wisp-Dist 2348?": > Thanks for reply, > but Is that AP support by driver mentioned earlier - > http://hostap.epitest.fi/ ? > Thank you. > Litin > > -Original Message- > From: Vladimir I. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 4:48 PM > To: Dominik Strnad > Subject: Re: [leaf-devel] Kernel sources for Wisp-Dist 2348? > > > Yes, WISP-Dist supports AP mode and you can configure via its menu > interface. > > Dominik Strnad wrote: > > Thank you, > > BTW: I now that you insert support for WiFi Prism 2 chipset. > > Is this driver that one: > > > http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers. > > html#Prism2-hostAP ?? > > > > Mean, if it have with AP node functionality? > > > > Thank you. > > Litin > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Vladimir I. > > Sent: Thursday, October 03, 2002 11:45 AM > > To: Dominik Strnad > > Cc: [EMAIL PROTECTED] > > Subject: Re: [leaf-devel] Kernel sources for Wisp-Dist 2348? > > > > > > Sources from 2290 are compatible. > > > > Dominik Strnad wrote: > > > >>Can I found it anywhere? I need to compile some modules which needs kernel > >>sources. > >>Thanks > >>Litin > >> > >> > >> > >> > >>--- > >>This sf.net email is sponsored by:ThinkGeek > >>Welcome to geek heaven. > >>http://thinkgeek.com/sf > >> > >>___ > >>leaf-devel mailing list > >>[EMAIL PROTECTED] > >>https://lists.sourceforge.net/lists/listinfo/leaf-devel > >> > > > > > > > > -- > > Best Regards, > > Vladimir > > Systems Engineer (RHCE) > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > > > ___ > > leaf-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/leaf-devel > > > > > > > -- > Best Regards, > Vladimir > Systems Engineer (RHCE) > > -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Kernel sources for Wisp-Dist 2348?
Sources from 2290 are compatible. Dominik Strnad wrote: > Can I found it anywhere? I need to compile some modules which needs kernel > sources. > Thanks > Litin > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > > ___ > leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel > -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] WISP-DIST cfs and lrp layout
CFS layout is the same as for LRP. Actually dhcpd is already included. Michael Shuler wrote: > How should a layout a CFS file for adding a dhcpd server (single binary > that I want to go under /usr/bin or something within the path)? What > about the .lrp file for it's config file /etc/dhcpd.conf? How do I make > it part of the "save" option under the menus? Sorry about so many > questions but I can't seem to find any documentation anywhere. > > FYI: I am planning on adding tftpd, dhcpd, Mobile IP FA, HA, and Client. > I am also working on a billing gateway i.e. out of town customer wants > wireless access from your hotspot. They will be prompted for a > username/password or credit card info. If anyone else is already > working on any of these please let me know. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] new busybox, tinylogin at busybox.net
David Douthitt wrote about "Re: [leaf-devel] new busybox, tinylogin at busybox.net": > Oxygen does not use glibc at all in starting up, but relies on busybox > and snarf compiled with uClibc. It doesn't use sed at all during the > loading process. BTW, WISP-Dist uses busybox staticly compiled against uClibc during start-up as well. However, static version of sed is used during start-up, which is later dropped in favour of a dynamic one. -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs src tree
> src +bering > +dachstein > +oxygen > +packetfilter > +wisp-dist > +packages +glibc-2.0 > +glibc-2.1 > +glibc-none +glibc-2.2 For WISP-Dist ;) Actually WISP-Dist CFSLRP packages are not backwards compatible with LRP. Any ideas about a good place for them? -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Bering RC3 uClibc
Hmm... Don't remember exactly now. I think it was Zebra. Richard Doyle wrote: > On Tue, 2002-07-09 at 07:40, Vladimir I. wrote: > >>In my experience you have to be careful with uClibc.. I also tried migrating to >>it and while the binaries seemed to run, I got various glitches and strange >>behavior. > > > Which binaries caused problems? uClibc gets better and better all the > time and now supports many applications. > > -Richard > -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Bering RC3 uClibc
In my experience you have to be careful with uClibc.. I also tried migrating to it and while the binaries seemed to run, I got various glitches and strange behavior. BTW, WISP-Dist's initrd is based on busybox/ash/sed compiled against uClibc. E.Spakman wrote: > I managed to build an (allmost) complete version of Bering RC3 against > uClibc 0.9.12. This version is *a lot* smaller than the original version > build against GLIBC2. I tested the following modules: weblet, root, > initrd, dhcpd, pump, ezipupd, dnscache... I don't use pppd, so I couldn't > test it but it compiled without a problem. I had some problems with the > symbolic links stdin, stdout and stderror to /dev/fd in root.dev.mk (I > couldn't log in) so I removed them, still everything works like > expected. I don't know exactly what the problem is with stdin etc but > maybe it's got something to do with uClibc, tinylogin or the version of > ash I use (slack 8.1). > I don't have the "ip patched" version of ifupdown and included ifconfig > and route. There is a new version of ifupdown (0.6.4-4.3) that makes it > possible to use udhcp and make things even smaller. > > I don't know if uClibc is the way to go for LEAF, but it's rappidly > evolving. Glibc 2.0.7 is not maintained and Glibc 2.2.x is just to big to > fit on a floppy. An other 'advantage' of uClibc is that you can get rid of > nss libs and nsswitch.conf. > > Regards, > Eric Spakman > > > > --- > This sf.net email is sponsored by:ThinkGeek > Stuff, things, and much much more. > http://thinkgeek.com/sf > > ___ > Leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel > -- Best Regards, Vladimir Systems Engineer (RHCE) --- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
