- 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

Re: [Wlug] orinoco driver

by Andy Stewart

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

Aug. 23, 2002

orinoco driver

by Wesley Allen

Hi all, hope the BBQ went well, sorry I couldn't come (I was picking up my Brother-In-Law at Logan...sigh, one day I'll get to a meeting). I've got a netgear wifi card that works great in Mandrake Linux, with the exception of wep (I know, it's cracked). In doing some research on the card and the kernel module that loads wvlan_cs, I have found out that this module has been replaced (by and large) by orinoco_cs, which I understand to be more functional (i.e. maybe I can get wep working?). I tried modprobe -r wvlan_cs and modprobe orinoco_cs but it won't bind to my pcmcia card. So I figured, "Well, maybe my card is just one that can't use the newer driver..." WRONG! Just to see what it was like, I download Knoppix, burned it onto a cd, and booted it up. Guess what driver loaded? orinoco_cs!! And it worked well too. Well, since Knoppix is a cd-boot, run in memory distro; I'm not changing to it anytime soon. So I'm going to use this opportunity to learn something new. How can I bind the orinoco driver to my card? Wes -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

WLUG BBQ

by Andy Stewart

HI gang, I'm running late. I'm leaving my house now for the BBQ. I'll see ya there around 6:30 - 6:45 PM. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 22, 2002

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

by Theo Van Dinter

On Wed, Aug 21, 2002 at 07:33:01PM -0400, Charles R. Anderson wrote: > So let me get this straight...you are using the system clock to measure > the system clock? :) ;) The interrupt change would still be outside the 98 - 102 range if it got funky, but I know what you're saying. I'll test externally after dinner. > The program adjtimex may be interfering in some way. What does > /sbin/adjtimex --print display? <theo installs adjtimex> mode: 0 offset: 16038 frequency: 3138214 maxerror: 148248 esterror: 17792 status: 1 time_constant: 2 precision: 1 tolerance: 33554432 tick: 10000 raw time: 1029973970s 363977us = 1029973970.363977 -- Randomly Generated Tagline: "I sometimes think they choose guards basaed on the bone content of their heads." - Londo on Babylon 5

Aug. 21, 2002

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

by Charles R. Anderson

On Wed, Aug 21, 2002 at 07:15:14PM -0400, Theo Van Dinter wrote: felicity> That's about right, a quick 'while(1){grep ' 0' /proc/interrupts;sleep felicity> 1}' shows ~101 per second, with the overhead of doing the fork/grep... So let me get this straight...you are using the system clock to measure the system clock? :) 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. Of course, I don't see how a skew in the timer tick could cause the system time to change by a whole hour... There is also the possiblity of adjtime screwing up. There are syscalls related to adjusting the system clock used by NTP et. al. and I remember reading that xntpd had to keep up with changes between kernel revisions, or weird time setting issues would result. The program adjtimex may be interfering in some way. What does /sbin/adjtimex --print display? -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 21, 2002

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

by Theo Van Dinter

On Wed, Aug 21, 2002 at 06:37:25PM -0400, Charles R. Anderson wrote: > The hardware clock is only read during boot, so that couldn't be it... hmmm. > The system clock keeps time by the system timer interrupt, I believe. The > timer interrupt is generated by the system's RTC chip. On x86 platforms > it is fixed at 100 Hz (only Alpha uses a different value--1024 Hz). I > remember reading that the HZ timer could be changed on any platform now, > but maybe that was for 2.5 only. That's about right, a quick 'while(1){grep ' 0' /proc/interrupts;sleep 1}' shows ~101 per second, with the overhead of doing the fork/grep... > Take a look at IRQ 0 in /proc/interrupts. Take a sampling of values over > time, and figure out how many interrupts there are per second. Maybe > that will shed some light on this... I have a script checking per second and reporting if the differences is 90 > diff > 110. I figure a 2% skew in a second isn't horribly bad. Over 5 minutes, and nothing was displayed. :( -- Randomly Generated Tagline: "BUGS: This manpage is confusing." - man page for getopt

Aug. 21, 2002

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

by Michelle Vadeboncoeur

On Wed, 21 Aug 2002, Michael Frysinger wrote: MF> i run 2.4.1{6,8}-xfs w/out any time issues MF> (so as to dispell the source of the problem being kernel) MF> MF> From: "Theo Van Dinter" <felicity(a)kluge.net> MF> > BTW: If anyone is wondering, I'm running SGI's XFS patched 2.4.18 kernel: MF> > 2.4.18-SGI_XFS_1.1. I'm thinking about dropping back to a 2.4.9 kernel MF> > w/ XFS support and seeing if that works any better. :( I was running MF> > 2.4.18 on the P200 for quite a while though without problem. the kernel didn't change, so that's not likely the problem... (I did try to warn Theo to not change too many things at once, but... still did the hardware upgrade at the same time as the RH7.2->7.3 upgrade... <sigh>) -- --==*==-- --==*==-- Michelle R. Vadeboncoeur --==*==-- --==*==-- mrv(a)kluge.net: http://www.kluge.net/~mrv/

Aug. 21, 2002

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

by Charles R. Anderson

On Wed, Aug 21, 2002 at 05:31:28PM -0400, Theo Van Dinter wrote: felicity> I've tried "hwclock --systohc" to force the hardware clock to the same felicity> time as the system, didn't help. I'm running NTP and thought maybe The hardware clock is only read during boot, so that couldn't be it... The system clock keeps time by the system timer interrupt, I believe. The timer interrupt is generated by the system's RTC chip. On x86 platforms it is fixed at 100 Hz (only Alpha uses a different value--1024 Hz). I remember reading that the HZ timer could be changed on any platform now, but maybe that was for 2.5 only. So, I wonder if it has something to do with the timer interrupt? Take a look at IRQ 0 in /proc/interrupts. Take a sampling of values over time, and figure out how many interrupts there are per second. Maybe that will shed some light on this... -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 21, 2002

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

by Michael Frysinger

i run 2.4.1{6,8}-xfs w/out any time issues (so as to dispell the source of the problem being kernel) -mike ----- Original Message ----- From: "Theo Van Dinter" <felicity(a)kluge.net> To: "Worcester Linux User's Group" <wlug(a)wlug.org> Sent: Wednesday, August 21, 2002 17:31 Subject: [Wlug] Stupid Hardware Clock Tricks, aka: WTF? > Over this past weekend I upgraded my server from a P200/RedHat Linux > 7.2 to a new Athlon 850/RedHat Linux 7.3. The Athlon was my trusty > workstation for many a year. Everything's great, except for one problem: > the clock goes crazy! > > It seems to be a once per second issue: > > $ perl -e '$t=time;while(1){$t2=time; warn join("\n",scalar > localtime($t),scalar localtime($t2),"") if ($t2-$t>4); $t=$t2;}' > Wed Aug 21 17:17:28 2002 > Wed Aug 21 18:29:03 2002 > Wed Aug 21 17:17:29 2002 > Wed Aug 21 18:29:04 2002 > Wed Aug 21 17:17:30 2002 > Wed Aug 21 18:29:05 2002 > > > I use netsaint to monitor system health, and it keeps complaining about > the time jumps: > > Aug 21 18:28:03 eclectic netsaint: Warning: A system time change of 4296 > seconds (forwards in time) has been detected. Compensating... > Aug 21 17:16:31 eclectic netsaint: Warning: A system time change of 4293 > seconds (backwards in time) has been detected. Compensating... > Aug 21 18:29:42 eclectic netsaint: Warning: A system time change of 4296 > seconds (forwards in time) has been detected. Compensating... > Aug 21 17:18:10 eclectic netsaint: Warning: A system time change of 4293 > seconds (backwards in time) has been detected. Compensating... > > Of course, random checks start failing as well since they occasionally > run during the time jump, and if they're checking for time since something > occured (log entry, cron run, query response time, etc) ... > > I've tried "hwclock --systohc" to force the hardware clock to the same > time as the system, didn't help. I'm running NTP and thought maybe > it was having problems, so I tried turning that off, didn't help. > I went through BIOS and tweaked memory/IRQ settings -- I didn't think > it would really solve anything, but the setting changes and reboot kept > the behavior away for ~14-15 hours. > > > So I'm completely stumped as to what causes this problem. Has anyone > seen anything like this before? Any suggestions for things to look at? > I'm at the point where I'm planning to just buy a new bit of hardware, > migrate the drives and such again, and go from there. With my luck the > problem would follow me of course... :( > > Thanks in advance. :) > > BTW: If anyone is wondering, I'm running SGI's XFS patched 2.4.18 kernel: > 2.4.18-SGI_XFS_1.1. I'm thinking about dropping back to a 2.4.9 kernel > w/ XFS support and seeing if that works any better. :( I was running > 2.4.18 on the P200 for quite a while though without problem. > > -- > Randomly Generated Tagline: > I don't want to look like a weirdo. I'll just go with a muumuu. > > -- Homer Simpson > King-Size Homer > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Aug. 21, 2002

Stupid Hardware Clock Tricks, aka: WTF?

by Theo Van Dinter

Over this past weekend I upgraded my server from a P200/RedHat Linux 7.2 to a new Athlon 850/RedHat Linux 7.3. The Athlon was my trusty workstation for many a year. Everything's great, except for one problem: the clock goes crazy! It seems to be a once per second issue: $ perl -e '$t=time;while(1){$t2=time; warn join("\n",scalar localtime($t),scalar localtime($t2),"") if ($t2-$t>4); $t=$t2;}' Wed Aug 21 17:17:28 2002 Wed Aug 21 18:29:03 2002 Wed Aug 21 17:17:29 2002 Wed Aug 21 18:29:04 2002 Wed Aug 21 17:17:30 2002 Wed Aug 21 18:29:05 2002 I use netsaint to monitor system health, and it keeps complaining about the time jumps: Aug 21 18:28:03 eclectic netsaint: Warning: A system time change of 4296 seconds (forwards in time) has been detected. Compensating... Aug 21 17:16:31 eclectic netsaint: Warning: A system time change of 4293 seconds (backwards in time) has been detected. Compensating... Aug 21 18:29:42 eclectic netsaint: Warning: A system time change of 4296 seconds (forwards in time) has been detected. Compensating... Aug 21 17:18:10 eclectic netsaint: Warning: A system time change of 4293 seconds (backwards in time) has been detected. Compensating... Of course, random checks start failing as well since they occasionally run during the time jump, and if they're checking for time since something occured (log entry, cron run, query response time, etc) ... I've tried "hwclock --systohc" to force the hardware clock to the same time as the system, didn't help. I'm running NTP and thought maybe it was having problems, so I tried turning that off, didn't help. I went through BIOS and tweaked memory/IRQ settings -- I didn't think it would really solve anything, but the setting changes and reboot kept the behavior away for ~14-15 hours. So I'm completely stumped as to what causes this problem. Has anyone seen anything like this before? Any suggestions for things to look at? I'm at the point where I'm planning to just buy a new bit of hardware, migrate the drives and such again, and go from there. With my luck the problem would follow me of course... :( Thanks in advance. :) BTW: If anyone is wondering, I'm running SGI's XFS patched 2.4.18 kernel: 2.4.18-SGI_XFS_1.1. I'm thinking about dropping back to a 2.4.9 kernel w/ XFS support and seeing if that works any better. :( I was running 2.4.18 on the P200 for quite a while though without problem. -- Randomly Generated Tagline: I don't want to look like a weirdo. I'll just go with a muumuu. -- Homer Simpson King-Size Homer

Aug. 21, 2002

Red Hat, Westford MA career day

by Tim Burke

FYI - we're having an open house next Wednesday. http://bostonworks.boston.com/events/openhouses/redhat.shtml

Aug. 20, 2002

Re: [Wlug] REMINDER: WLUG BBQ

by desdinova＠soupforare.net

On 17 Aug 2002 at 20:59, Andy Stewart wrote: > > HI everybody, > > The WLUG BBQ will be held on Thursday, August 22nd starting at 6 PM. > Directions to Doug Waud's house, a.k.a BBQ Central, can be found on > the WLUG website. > > Please RSVP if you plan to attend. I've received 3 or 4 RSVPs and I'm > sure there will be more people than that. We need to have an idea how > much food to purchase. Je responde. That's the correct RSVP, isn't it? I don't remember my french teachings :) Thanks James KB1FJQ

Aug. 18, 2002

REMINDER: WLUG BBQ

by Andy Stewart

HI everybody, The WLUG BBQ will be held on Thursday, August 22nd starting at 6 PM. Directions to Doug Waud's house, a.k.a BBQ Central, can be found on the WLUG website. Please RSVP if you plan to attend. I've received 3 or 4 RSVPs and I'm sure there will be more people than that. We need to have an idea how much food to purchase. WLUG will supply the standard BBQ fare and some soda and munchies. If you want beer or wine, you may BYOB and we'll have a way to keep it cold. Feel free to bring your own dessert or cold salad items if you so choose. Doug's house has a pool so bring towels and such! If you can think of anything else, let me know. Otherwise, I'll see you all on Thursday. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 18, 2002

Kernel int-13 interface?

by Chuck Homic

Hey, this one goes out to all you kernel hackers out there. After 4 years, I've once again become interested in installing Linux on my HP OmniBook 300. Because it's an aswesome computer, and I think DOS 5 is a complete waste of its skill. [Background. The OB300 is a vintage 386-20, with a passive reflective 640x480 LCD display. Basically an oversize TI calculator running DOS] Anyway, from my first tests, I discovered that I can indeed boot the kernel using loadlin. But it immediately freaks out because it can't read (or even think about) my primary media... solid-state PCMCIA flash cards. Now, I briefly tried looking up some data on the OB300's PCMCIA chipset (I think the first standard was still being developed when this computer was made) and quickly decided that wasn't the route to go. And HP told me to go to hell when I asked. But DOS seems to work just fine using the int 13 interface to access the flash disks. So now my question... can I do that in Linux? I don't see any block device support (and most people would agree an int 13 block device would be stupid), but I think I can write one myself. All it would have to do is make the switch into real mode, call the int 13 interface, and then come back. Will Linux tolerate that? As far as I know, many drivers use a real mode interrupt on laptops to trigger their power saving capabilities (suspend, etc...), so I suspect it would be okay. Can anyone stop me before I go too far? Or should I go ahead and write this thing? -Chuck

Aug. 16, 2002

potential mailing list problems

by Frank Sweetser

Just a quick heads up - the WLUG mailing list server seems to be having some issues, and since I won't be around to fix it until Monday, it may not be stable over the weekend. I have a backup of the mailing list data, though, so nothing should be lost once things are all fixed up. -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 18 Full-time WPI Network Engineer, Part time Linux/Perl guy | Soitainly. I was assuming that came with the OO-ness of it. -- Larry Wall in <199710011802.LAA21692(a)wall.org>

Aug. 15, 2002