Messages in this thread | | | From | Denis Vlasenko <> | Subject | Re: ipw2100: firmware problem | Date | Thu, 9 Jun 2005 09:25:07 +0300 |
| |
On Thursday 09 June 2005 09:16, David S. Miller wrote: > From: Denis Vlasenko <vda@ilport.com.ua> > Date: Thu, 9 Jun 2005 09:09:55 +0300 > > > On Wednesday 08 June 2005 18:05, Alejandro Bonilla wrote: > > > Currently, when we install the driver, it associates to any open network on > > > boot. This is good, cause we don't want to be typing the commands all the > > > time just to associate. It works this way now and is pretty nice. > > > > What is so nice about this? That Linux novice user with his new lappie > > will join a neighbor's network every time he powers up the lappie, > > even without knowing that? > > I love this behavior, because it means that I don't have to do > anything special to get my setup at home working. > > Me caveman > Me plug in wireless router > Me watch pretty lights > Me turn on computer > Me up interface
You need to up interface? And surely you need ip addr? That's a knob also! :)
> Computer work > Me no care other cavemen use wireless link > > Configuration knobs are _madness_. Things should work with minimal > intervention and configuration.
Sure. I consider "iwconfig essid MyCave mode managed" a minimal intervention, just like I consider "ip a a dev eth0 123.123.123.2/24 brd +; ip l set dev eth0 up" a miniman interventian if I need IP configured. -- vda
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |