Re: Airport support in 2.4.x kernel

2001-03-18 Thread Michel Dänzer
Alan DuBoff wrote: > I noticed that when I rsync'd to the linux-pmac-devel tree from Paulus, I > lost my .config all together and it replaced it with a new one...I'm more > careful now! I use this script to circumvent that: #!/bin/sh cp .config .config.bak rsync -arvz penguinppc.org::linux-2.4-

Re: Airport support in 2.4.x kernel

2001-03-18 Thread Ethan Benson
On Sat, Mar 17, 2001 at 10:45:57PM -0800, Alan DuBoff wrote: > > Certainly I won't argue after spending more time on getting the 2.4 kernel > operational than I would have liked. But I guess that is how Paulus is using > it. that is no excuse. you can leave devfs set to NOT automount and mount i

Re: Airport support in 2.4.x kernel

2001-03-18 Thread Alan DuBoff
Tuomas Kuosmanen wrote: > By the way, make sure you secure your wireless so it is not open for > everyone with DHCP.. There are WAY too many of these, while it may be > "convenient" to get free internet to a hotel room from a nearby new > media agency, it is not fun from their point of view. Very

Re: Airport support in 2.4.x kernel

2001-03-18 Thread Alan DuBoff
Ethan Benson wrote: > > ... > > ... > gratuitously breaking peoples systems like this is exceptionally > rude. > > Certainly I won't argue after spending more time on getting the 2.4 kernel operational than I would have liked. But I guess that is how Paulus is using it. I noticed that when I

Re: Airport support in 2.4.x kernel

2001-03-18 Thread Alan DuBoff
Alan DuBoff wrote: > > Michel Lanners wrote: > > > Rememebr the fine options to ifconfig ;-) running 'ifconfig' without > > options will only show you configured interfaces, not unconfigured ones. > > Running 'ifconfig -a' will show _all_ interfaces. > > No, that was not it as I was using ifconf

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Ethan Benson
On Sun, Mar 18, 2001 at 01:11:12AM +0200, Tuomas Kuosmanen wrote: > By the way, make sure you secure your wireless so it is not open for > everyone with DHCP.. There are WAY too many of these, while it may be > "convenient" to get free internet to a hotel room from a nearby new > media agency, it i

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Tuomas Kuosmanen
On 16 Mar 2001 22:47:56 -0800, Alan DuBoff wrote: > I am so excited to send you the first message over my airport using the > wireless in the room next to my office... By the way, make sure you secure your wireless so it is not open for everyone with DHCP.. There are WAY too many of these, while i

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Tuomas Kuosmanen
On 16 Mar 2001 22:47:56 -0800, Alan DuBoff wrote: > I am so excited to send you the first message over my airport using the > wireless in the room next to my office... By the way, make sure you secure your wireless so it is not open for everyone with DHCP.. There are WAY too many of these, while i

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Kevin van Haaren
At 01:21 -0900 3/17/2001, Ethan Benson wrote: in the past the included .config was useful for people since it was a generic config that worked on most powerpcs, this configuration will on the other hand BREAK on the majority of systems. I'd have to agree with this, I've always treated the defau

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Ethan Benson
On Sat, Mar 17, 2001 at 04:27:54AM +0200, Tuomas Kuosmanen wrote: > This sounds very much like DevFS. Install devfsd package that should set > up the partition names for you in /dev. The problem with devfs is all > the partitions look different, as it is not /dev/hda1 but something like > /dev/dis

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Alan DuBoff
Michel Lanners wrote: > Rememebr the fine options to ifconfig ;-) running 'ifconfig' without > options will only show you configured interfaces, not unconfigured ones. > Running 'ifconfig -a' will show _all_ interfaces. No, that was not it as I was using ifconfig -a to get all the interfaces. The

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Michel Lanners
On 17 Mar, this message from Tuomas Kuosmanen echoed through cyberspace: > On Fri, Mar 16, 2001 at 09:46:55PM -0800, thus said Alan DuBoff: >> You have set me on the right track here. I have the module now, and was able >> to insmod it, but I don't see any wireless interfaces, so will go to the >

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Alan DuBoff
Tuomas Kuosmanen wrote: > Whee :) It's always nice to see replies like this! It's always nice to send replies like that!;-) > It is "airport", not eth0 or wavelan0. So you can "ifconfig airport blah > blah" > ... > So how iwconfig works? Some examples: > ... > Yea. And I'm afraid there is no poi

Re: Airport support in 2.4.x kernel

2001-03-17 Thread Tuomas Kuosmanen
On Fri, Mar 16, 2001 at 09:46:55PM -0800, thus said Alan DuBoff: > Bingo! A million thanks for posting that response Tuomas!!! I went into > the kernel configuration and saw the auto mount option set to yes, set it to > no, recompiled and I've just boot for the first time with the 2.4.3-pre3 >

Re: Airport support in 2.4.x kernel

2001-03-16 Thread Alan DuBoff
Tuomas Kuosmanen wrote: > This sounds very much like DevFS. Install devfsd package that should set > up the partition names for you in /dev. The problem with devfs is all > the partitions look different, as it is not /dev/hda1 but something like > /dev/disks/ide/lun0/partition-foo/blah/eek/1, whic

Re: Airport support in 2.4.x kernel

2001-03-16 Thread Tuomas Kuosmanen
On 13 Mar 2001 19:08:06 -0800, Alan DuBoff wrote: > > > After I get my airport module, I think I need to add my network wireless > > > network name as an argument when the module loads, correct? > > > > If the network requires it, yes. I don't remember what the option names > > are. I > > underst

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Alan DuBoff
Michel Dänzer wrote: > > Alan DuBoff wrote: > > > My only complaint so far is that if you leave the machine running, and close > > the lid, it gets hotter than a well digger's @$$, when I open it, it seems > > like you can fry and egg on the palm rest areas on each side of the > > trackpad... >

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Kevin van Haaren
At 00:02 -0800 3/13/2001, Alan DuBoff wrote: My only complaint so far is that if you leave the machine running, and close the lid, it gets hotter than a well digger's @$$, when I open it, it seems like you can fry and egg on the palm rest areas on each side of the trackpad...In comparison to the

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Michel Dänzer
Alan DuBoff wrote: > My only complaint so far is that if you leave the machine running, and close > the lid, it gets hotter than a well digger's @$$, when I open it, it seems > like you can fry and egg on the palm rest areas on each side of the > trackpad... Don't do that! Sleep isn't supported y

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Alan DuBoff
Michel Dänzer wrote: > But you said you also had the airport.c file, right? And whether or not it's > available in the configuration only depends on Config.in, which can't differ > in two trees rsynced at the same time. Yes, the airport.c file was there, even before the Airport showed up in Confi

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Alan DuBoff
Michel Dänzer wrote: > > Michel Lanners wrote: > > > > Look harder, guys ;-) > > Dunno, but believe me, it wasn't in my tree yesterday - .config didn't even > contain AIRPORT after oldconfig. It wasn't there, but is now. I just did an rsync from the ppc.linuxcare.com::linux-pmac-devel and it is i

Re: Airport support in 2.4.x kernel

2001-03-13 Thread Michel Dänzer
Alan DuBoff wrote: > > No way. The point of rsync is that it makes all local copies of the files > > in the repository identical to the originals (using a very interesting > > protocol BTW - look for the RFC which describes it if you are interested). > > Yes, that is the point. However, if you us

Airport support in 2.4.x kernel

2001-03-12 Thread Alan DuBoff
Michel Dänzer wrote: > No way. The point of rsync is that it makes all local copies of the files in > the repository identical to the originals (using a very interesting protocol > BTW - look for the RFC which describes it if you are interested). Yes, that is the point. However, if you use --dele