- WLUG - wlug.mailman3.com

python regular expressions

by Brad Noyes

Hi All, I'm starting to learn python. I was looking for a python equivalent to a perl regular expression such as $_ = "FreeBSD"; /(.*)BSD/; where $1 would get what ever is between '(...)', 'Free' in this case. Is there a way i can make use of the () regex operator in python? I can't seem to find an equivalent in python's regex module (re). Thanks, --brad

Aug. 24, 2002

/dev/sequencer problems

by Wesley T Allen

Hi all, I'm full of problems this week. Hopefully this'll have a successful ending as well! Any time I try to open a midi file, I get an error "can't open /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate arts); and I can't figure this out. Anyone got an idea? Wes

Aug. 23, 2002

RE: [Wlug] orinoco driver

by Wesley Allen

can you edit the file directly with emacs or vi? Wes On Fri, 2002-08-23 at 15:21, Haines, Charles Allen wrote: > I've got a question relating to this. I've got a netgear wireless card also. The card is detected and i can plug and play with it but I can't seem to get it set and essid. First off, I'm not sure which config it reading from /etc/pcmcia/wireless.opts. I've tried manually configuring it with iwconfig, it accepts the WEIP key, however it will not accept my essid. I've tried typing iwconfig essid "WPI-Wireless-Network", but it doesn't seem to keep it. Once I put it in and type iwconfig again, it says ESSID="". Anyone have any ideas. I'm using gentoo linux with kernel 2.4.19. > > > -----Original Message----- > From: Andy Stewart [mailto:andystewart@attbi.com] > Sent: Thu 8/22/2002 11:20 PM > To: wlug(a)mail.wlug.org > Cc: > Subject: Re: [Wlug] orinoco driver > > > > > Hi Wes, > > I discovered on my laptop that I had to insure that my wireless card was > listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE > 8.0, I believe the description below is distribution agnostic). > > Try this as root: > > # cardctl ident > > Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with > an entry matching the manfid is present. In my case, there was no entry so I > added one thus: > > card "Andy's Linksys Wireless" > manfid 0x0274, 0x1613 > bind "orinoco_cs" > > The card string seems to be arbitrary text. The manfid comes from "cardctl > ident", and the bind is to a kernel module. I have hotplugging services > running, so when I plug in my wireless adapter, it automagically loads the > kernel module(s), starts the net, sets up routing, etc. > > Give it a try and let us know how it goes! > > Later, > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

RE: [Wlug] orinoco driver

by Haines, Charles Allen

I've got a question relating to this. I've got a netgear wireless card also. The card is detected and i can plug and play with it but I can't seem to get it set and essid. First off, I'm not sure which config it reading from /etc/pcmcia/wireless.opts. I've tried manually configuring it with iwconfig, it accepts the WEIP key, however it will not accept my essid. I've tried typing iwconfig essid "WPI-Wireless-Network", but it doesn't seem to keep it. Once I put it in and type iwconfig again, it says ESSID="". Anyone have any ideas. I'm using gentoo linux with kernel 2.4.19. -----Original Message----- From: Andy Stewart [mailto:andystewart@attbi.com] Sent: Thu 8/22/2002 11:20 PM To: wlug(a)mail.wlug.org Cc: Subject: Re: [Wlug] orinoco driver Hi Wes, I discovered on my laptop that I had to insure that my wireless card was listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE 8.0, I believe the description below is distribution agnostic). Try this as root: # cardctl ident Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with an entry matching the manfid is present. In my case, there was no entry so I added one thus: card "Andy's Linksys Wireless" manfid 0x0274, 0x1613 bind "orinoco_cs" The card string seems to be arbitrary text. The manfid comes from "cardctl ident", and the bind is to a kernel module. I have hotplugging services running, so when I plug in my wireless adapter, it automagically loads the kernel module(s), starts the net, sets up routing, etc. Give it a try and let us know how it goes! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Aug. 23, 2002

Re: [Wlug] Stupid Hardware Clock Tricks, aka: WTF?

by Theo Van Dinter

On Wed, Aug 21, 2002 at 07:53:33PM -0400, Theo Van Dinter wrote: > it got funky, but I know what you're saying. I'll test externally after > dinner. Ok, so I got caught up after dinner ... ;) I did go and change the BIOS settings again, around 11pm on Wednesday. The problem then stayed away until ~4:12am on the 23rd. > I suggest writing down the value, counting five minutes with an EXTERNAL > clock, such as a stopwatch, and then writing down the value again. > (value2 - value1) / (60*5) should equal about 100. Ok, here we go: (date as reported from different system) Fri Aug 23 09:50:26 EDT 2002 CPU0 0: 13720765 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 753652 XT-PIC serial 8: 1 XT-PIC rtc 10: 320822 XT-PIC eth0, eth1 11: 996123 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13720778 ERR: 4588 MIS: 0 Fri Aug 23 10:28:45 EDT 2002 CPU0 0: 13950661 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 761173 XT-PIC serial 8: 1 XT-PIC rtc 10: 326570 XT-PIC eth0, eth1 11: 1008701 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13950673 ERR: 4622 MIS: 0 The first thing I notice is that int 4 is getting hit quite a bit, and I have no idea why. The device hooked up to that serial port is a UPS, and shouldn't be generating so many interrupts. Hmmm. Anyway, between the two times is 38:19, or 2299 seconds. So: (13950661-13720765) / 2299 = 99.9982601130927 So that part seems ok. :| -- Randomly Generated Tagline: That is a known bug in 5.00550. Either an upgrade or a downgrade will fix it. -- Larry Wall in <6vu1vo$89c(a)kiev.wall.org>

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Wesley Allen

Andy, I just typed the pass-phrase into my router's config utility; since it only does up to 128-bit, I don't have to worry about 256! So I got the key and put that in /etc/network-scripts/eth1-config (after testing it by putting it in iwconfig) and it works. I didn't want to send a plain-text passphrase! But it WORKS! Wes On Fri, 2002-08-23 at 07:58, Andy Stewart wrote: > > Hi Wes, > > I discovered that I could only get 64 and 128 bit WEP working. Although my > hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making > it work. > > I also discovered that typing a pass phrase on a Windows based appliance would > yield a different hex string than typing the same pass phrase on Linux. So, > what I did was to pick my pass phrase, type it into one machine, and then > copy the resulting hex code directly to the other machine ("machine" meaning > access point, Linux wireless software, etc). > > On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm > not sure whether that is a SuSE specific file. The syntax of the important > line is: > > WIRELESS_KEY="s:xxxxx" > > where the "s:" indicates a string (the pass phrase) and the xxxx are the > characters. For 64 bit encryption, you need 5 characters, while with 128 bit > encryption, you need 13 characters. > > Have fun! > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

Re: [Wlug] LUG's rule

by Andy Stewart

On Friday 23 August 2002 6:52 am, Wesley Allen wrote: > Gang, can I just tell you how much I love the Linux community. You > figure stuff out part way, and the community fills in the gaps! > > orinoco_cs is loaded, and wep is FINALLY enabled on my wlan! > > Thank you! > > Wes Way to go, Wes. Congratulations! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Andy Stewart

Hi Wes, I discovered that I could only get 64 and 128 bit WEP working. Although my hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making it work. I also discovered that typing a pass phrase on a Windows based appliance would yield a different hex string than typing the same pass phrase on Linux. So, what I did was to pick my pass phrase, type it into one machine, and then copy the resulting hex code directly to the other machine ("machine" meaning access point, Linux wireless software, etc). On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm not sure whether that is a SuSE specific file. The syntax of the important line is: WIRELESS_KEY="s:xxxxx" where the "s:" indicates a string (the pass phrase) and the xxxx are the characters. For 64 bit encryption, you need 5 characters, while with 128 bit encryption, you need 13 characters. Have fun! Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 23, 2002

LUG's rule

by Wesley Allen

Gang, can I just tell you how much I love the Linux community. You figure stuff out part way, and the community fills in the gaps! orinoco_cs is loaded, and wep is FINALLY enabled on my wlan! Thank you! Wes -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Wesley Allen

Andy, Worked like a charm. There was an entry with my manfid in /etc/pcmcia/config and the bound driver was wvlan_cs; I switched it to orinoco_cs and, taking the cheesy way of rebooting, the network came up with the orinoco driver! Now I need to see if I can get wep working! Thanks, I love learning new tricks. Wes On Thu, 2002-08-22 at 23:20, Andy Stewart wrote: > > Hi Wes, > > I discovered on my laptop that I had to insure that my wireless card was > listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE > 8.0, I believe the description below is distribution agnostic). > > Try this as root: > > # cardctl ident > > Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with > an entry matching the manfid is present. In my case, there was no entry so I > added one thus: > > card "Andy's Linksys Wireless" > manfid 0x0274, 0x1613 > bind "orinoco_cs" > > The card string seems to be arbitrary text. The manfid comes from "cardctl > ident", and the bind is to a kernel module. I have hotplugging services > running, so when I plug in my wireless adapter, it automagically loads the > kernel module(s), starts the net, sets up routing, etc. > > Give it a try and let us know how it goes! > > Later, > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002