Re: 3com Driver and the 3XP Processor
On Thu, 14 Jun 2001, Kip Macy wrote: > As I mentioned previously IP heavy is a euphemism for commodity. ...and 3Com is notoriuos for putting out commodity, cheesy hardware. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com Driver and the 3XP Processor
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote: > Erm, that is going to be a problem. Crypto benifits more from open source > than any other market segment, and binary only drivers for linux are not > the way to go. I guess I need to get rid of my 5-10 3cr990s and replace > them with someone else's product? I would... 3Com hardware (as far as i'm concerned) is garbage Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com Driver and the 3XP Processor
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote: Erm, that is going to be a problem. Crypto benifits more from open source than any other market segment, and binary only drivers for linux are not the way to go. I guess I need to get rid of my 5-10 3cr990s and replace them with someone else's product? I would... 3Com hardware (as far as i'm concerned) is garbage Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com Driver and the 3XP Processor
On Thu, 14 Jun 2001, Kip Macy wrote: As I mentioned previously IP heavy is a euphemism for commodity. ...and 3Com is notoriuos for putting out commodity, cheesy hardware. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: temperature standard - global config option?
On 6 Jun 2001, David N. Welton wrote: > > [ please CC replies to me ] > > Perusing the kernel sources while investigating watchdog drivers, I > notice that in some places, Fahrenheit is used, and in some places, > Celsius. It would seem logical to me to have a global config option, > so that you *know* that you talk devices either in F or C. > > I searched the archives for discussions regarding this, but didn't > find anything, apologies if I missed something. If something is done, Celsius should be default (as the US is brain-dead like that; nearly everywhere else uses Celsius as the standard) and fahrenheit as an option. I wrote a patch for the 'sensors' utility in lm_sensors that did just that; supplied fahrenheit conversion for the sensors via a commandline option. Perhaps there could be a config option in the kernel (or a proc entry/ioctl?) that controls this. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: temperature standard - global config option?
On 6 Jun 2001, David N. Welton wrote: [ please CC replies to me ] Perusing the kernel sources while investigating watchdog drivers, I notice that in some places, Fahrenheit is used, and in some places, Celsius. It would seem logical to me to have a global config option, so that you *know* that you talk devices either in F or C. I searched the archives for discussions regarding this, but didn't find anything, apologies if I missed something. If something is done, Celsius should be default (as the US is brain-dead like that; nearly everywhere else uses Celsius as the standard) and fahrenheit as an option. I wrote a patch for the 'sensors' utility in lm_sensors that did just that; supplied fahrenheit conversion for the sensors via a commandline option. Perhaps there could be a config option in the kernel (or a proc entry/ioctl?) that controls this. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: select() - Linux vs. BSD
On Tue, 29 May 2001, John Chris Wren wrote: > Should the man pages be changed to reflect reality, or select() fixed to > act like BSD? > BSD should be destroyed :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: select() - Linux vs. BSD
On Tue, 29 May 2001, John Chris Wren wrote: Should the man pages be changed to reflect reality, or select() fixed to act like BSD? BSD should be destroyed :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] fbdev logo (fwd)
On Thu, 10 May 2001, Geert Uytterhoeven wrote: > - Political fixes: > o There were still some penguins left carrying a glass of beer or wine. > This problem is about 2 years old! I still don't understand why the penguin holding beer/wine was wrong... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] fbdev logo (fwd)
On Thu, 10 May 2001, Geert Uytterhoeven wrote: - Political fixes: o There were still some penguins left carrying a glass of beer or wine. This problem is about 2 years old! I still don't understand why the penguin holding beer/wine was wrong... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: gcc-2.95.3
cx863877-d% gcc --version 2.95.3 cx863877-d% uptime 3:26pm up 14 days, 15:15, 15 users, load average: 2.01, 2.01, 2.00 cx863877-d% uname -a Linux cx863877-d.cv1.sdca.home.com 2.4.3 #3 SMP Wed Apr 4 00:06:17 PDT 2001 i686 unknown No problems at all :) On Fri, 6 Apr 2001, Jeff Chua wrote: > Does anybody have bad experience with gcc-2.95.3? > > I'm using gcc-2.95.2 with linux 2.4.3 and have no problem with it. > > > Thanks, > Jeff > [ [EMAIL PROTECTED] ] > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: APIC errors ...
Um... Looks like when you clock the BX-chipset out of spec (>100MHz FSB) you get the error. Since BX wasn't ever designed to be run at >100MHz these errors are *expected*. You have a couple solutions: Upgrade the motherboard to one of the VIA 133MHz chipsets (I dont care for the VIA chipset so this really doesn't strike my fancy) or upgrade to that other Intel chipset that supports SMP; unfortunately it also is a rambus boardServerworks also has a chipset out that does dual intel chips at 133MHz; I've heard only good things about it. but, from what it looks like, your board is flakey up high... good luck, -kelsey On Fri, 6 Apr 2001, Kurt Garloff wrote: > Hi, > > lately having upgraded my DUal-BX motherboard to two PIII-850 CPUs, I run > into some trouble. > FIrst, I had had an assymetric configuration (iPIII-850 + iPII-350) , which > Linux did not support; I created a fix and sent it to LKML. It worked > perfectly, i.e. without the problems described below. > > Now, I have two iPIII-850, but I run into different kind of troubles: > (a) The BIOS will sometimes not recognize the second CPU > (b) Linux reports APIC errors and occasionally stops to process IRQs on the > second CPU or crashes (2.4.x kernel). > > Some details: DFI P2XBL/D, i440BX, BIOS Award mid 2000 (MPS 1.4), microcode > patches end 2000 patched into BIOS (which yields the rev. 08 for my pIII > (868)). The board is unable to supply the needed 1.7V for the CPUs, > therefore the Slot Adapter (from PowerLeap) contains voltage regulators and > VID is faked to 2.2V. The mainboard by specs supports up to 800MHz (max > multiplier 8 with FSB 100MHz). > > The config should be fine; the nmultipliers are fixe anyway nowadays. However: > (a) If I explicitly specify 100, 103 or 112 MHz FSB freq., the second CPU is > not recognized by the BIOS (and subsequently not by Linux) most of the > times. If set to automatic (yields 100MHz), it always recognizes the > 2nd CPU. Strange! Setting 83, 75, or 66 MHz FSB, the 2nd CPU is > recognized as well. > (b) The 2.2.16 kernel seems to be happy (did not run long enough to really > check stability), but the 2.4.x kernels reports lots of APIC errors. > Lots is smth in between 1/minute (almost idle computer) and more than > 1/second (gears Meas demo running). After some time, eventually the 2nd > CPU does not get IRQs any more; I've even seen some lockups (after a > day or so) of Linux, which I'm not used to :-( > Going back to 83/75/66 MHz FSB seems to also solve this problem, but > is not considered a solution by me. > > Here's some excerpt: (dmesg) > APIC error on CPU1: 02(02) > APIC error on CPU0: 01(01) > APIC error on CPU1: 02(02) > APIC error on CPU0: 01(05) > APIC error on CPU1: 02(02) > unexpected IRQ trap at vector d0 > unexpected IRQ trap at vector 88 > APIC error on CPU1: 02(02) > APIC error on CPU0: 05(01) > APIC error on CPU1: 02(02) > APIC error on CPU0: 01(01) > APIC error on CPU1: 02(02) > APIC error on CPU0: 01(01) > APIC error on CPU0: 01(01) > APIC error on CPU1: 02(02) > APIC error on CPU0: 01(01) > > pckurt:~ # cat /proc/interrupts >CPU0 CPU1 > 0:51805222357505IO-APIC-edge timer > 1: 24284 15803IO-APIC-edge keyboard > 2: 0 0 XT-PIC cascade > 3: 2 0IO-APIC-edge > 4: 0 2IO-APIC-edge serial > 5: 35031 27240IO-APIC-edge snd-card-als100 - DSP > 6: 1 2IO-APIC-edge > 7: 2 0IO-APIC-edge parport0 > 8: 0 1IO-APIC-edge rtc > 10: 1 0IO-APIC-edge snd-card-als100 - MPU-401 > 12: 5124 5959IO-APIC-edge PS/2 Mouse > 14: 18953 18258IO-APIC-edge ide0 > 17: 21728 20208 IO-APIC-level eth0 > 18: 23418 22327 IO-APIC-level sym53c8xx > 19: 9553 9442 IO-APIC-level aic7xxx, bttv > 28: 0 13none > 136: 0 35none > 140: 0 3none > 152: 0 1none > 156: 0 2none > 160: 0 2none > 172: 0 14none > 200: 0 1none > 204: 0 2none > 208: 0 13none > NMI: 0 0 > LOC:75387667538742 > ERR:777 > > (Note that I patched the IRQ reporting stuff, so you can get a count for > bogus IRQ vectors.) The AGP slot (MGA400) is mapped to IRQ16. (Not visible > above.) > > As you can see, the APIC on CPU1 seems eems to suffer under noise! > It gets APIC errors (which it acknowledges and causes CPU0 to also get an > error) and occasionally receives bogus IRQ vectors. > > So this looks like a HW problem. Some reports on LKML seem to indicate that > this is
Re: APIC errors ...
Um... Looks like when you clock the BX-chipset out of spec (100MHz FSB) you get the error. Since BX wasn't ever designed to be run at 100MHz these errors are *expected*. You have a couple solutions: Upgrade the motherboard to one of the VIA 133MHz chipsets (I dont care for the VIA chipset so this really doesn't strike my fancy) or upgrade to that other Intel chipset that supports SMP; unfortunately it also is a rambus boardServerworks also has a chipset out that does dual intel chips at 133MHz; I've heard only good things about it. but, from what it looks like, your board is flakey up high... good luck, -kelsey On Fri, 6 Apr 2001, Kurt Garloff wrote: Hi, lately having upgraded my DUal-BX motherboard to two PIII-850 CPUs, I run into some trouble. FIrst, I had had an assymetric configuration (iPIII-850 + iPII-350) , which Linux did not support; I created a fix and sent it to LKML. It worked perfectly, i.e. without the problems described below. Now, I have two iPIII-850, but I run into different kind of troubles: (a) The BIOS will sometimes not recognize the second CPU (b) Linux reports APIC errors and occasionally stops to process IRQs on the second CPU or crashes (2.4.x kernel). Some details: DFI P2XBL/D, i440BX, BIOS Award mid 2000 (MPS 1.4), microcode patches end 2000 patched into BIOS (which yields the rev. 08 for my pIII (868)). The board is unable to supply the needed 1.7V for the CPUs, therefore the Slot Adapter (from PowerLeap) contains voltage regulators and VID is faked to 2.2V. The mainboard by specs supports up to 800MHz (max multiplier 8 with FSB 100MHz). The config should be fine; the nmultipliers are fixe anyway nowadays. However: (a) If I explicitly specify 100, 103 or 112 MHz FSB freq., the second CPU is not recognized by the BIOS (and subsequently not by Linux) most of the times. If set to automatic (yields 100MHz), it always recognizes the 2nd CPU. Strange! Setting 83, 75, or 66 MHz FSB, the 2nd CPU is recognized as well. (b) The 2.2.16 kernel seems to be happy (did not run long enough to really check stability), but the 2.4.x kernels reports lots of APIC errors. Lots is smth in between 1/minute (almost idle computer) and more than 1/second (gears Meas demo running). After some time, eventually the 2nd CPU does not get IRQs any more; I've even seen some lockups (after a day or so) of Linux, which I'm not used to :-( Going back to 83/75/66 MHz FSB seems to also solve this problem, but is not considered a solution by me. Here's some excerpt: (dmesg) APIC error on CPU1: 02(02) APIC error on CPU0: 01(01) APIC error on CPU1: 02(02) APIC error on CPU0: 01(05) APIC error on CPU1: 02(02) unexpected IRQ trap at vector d0 unexpected IRQ trap at vector 88 APIC error on CPU1: 02(02) APIC error on CPU0: 05(01) APIC error on CPU1: 02(02) APIC error on CPU0: 01(01) APIC error on CPU1: 02(02) APIC error on CPU0: 01(01) APIC error on CPU0: 01(01) APIC error on CPU1: 02(02) APIC error on CPU0: 01(01) pckurt:~ # cat /proc/interrupts CPU0 CPU1 0:51805222357505IO-APIC-edge timer 1: 24284 15803IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3: 2 0IO-APIC-edge 4: 0 2IO-APIC-edge serial 5: 35031 27240IO-APIC-edge snd-card-als100 - DSP 6: 1 2IO-APIC-edge 7: 2 0IO-APIC-edge parport0 8: 0 1IO-APIC-edge rtc 10: 1 0IO-APIC-edge snd-card-als100 - MPU-401 12: 5124 5959IO-APIC-edge PS/2 Mouse 14: 18953 18258IO-APIC-edge ide0 17: 21728 20208 IO-APIC-level eth0 18: 23418 22327 IO-APIC-level sym53c8xx 19: 9553 9442 IO-APIC-level aic7xxx, bttv 28: 0 13none 136: 0 35none 140: 0 3none 152: 0 1none 156: 0 2none 160: 0 2none 172: 0 14none 200: 0 1none 204: 0 2none 208: 0 13none NMI: 0 0 LOC:75387667538742 ERR:777 (Note that I patched the IRQ reporting stuff, so you can get a count for bogus IRQ vectors.) The AGP slot (MGA400) is mapped to IRQ16. (Not visible above.) As you can see, the APIC on CPU1 seems eems to suffer under noise! It gets APIC errors (which it acknowledges and causes CPU0 to also get an error) and occasionally receives bogus IRQ vectors. So this looks like a HW problem. Some reports on LKML seem to indicate that this is indeed the case. Somebody is talking about the voltage regulators not giving a really stable
Re: gcc-2.95.3
cx863877-d% gcc --version 2.95.3 cx863877-d% uptime 3:26pm up 14 days, 15:15, 15 users, load average: 2.01, 2.01, 2.00 cx863877-d% uname -a Linux cx863877-d.cv1.sdca.home.com 2.4.3 #3 SMP Wed Apr 4 00:06:17 PDT 2001 i686 unknown No problems at all :) On Fri, 6 Apr 2001, Jeff Chua wrote: Does anybody have bad experience with gcc-2.95.3? I'm using gcc-2.95.2 with linux 2.4.3 and have no problem with it. Thanks, Jeff [ [EMAIL PROTECTED] ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Question about SysRq
On Wed, 4 Apr 2001, Boris Pisarcik wrote: > I looked a bit at the source of sysrq handling. I've found there is > rather big difference between sysrq+b and other killers handling. > Sysrq+b is just called with pretty straitforward fashion - stops other > processors on SMP and reboots directly (hardware impulse or triple fault) > or through the bios - so it just calls for the corruptions. ah, that would explain it... > On the other side sysrq+s marks a single variable, which will be tested > next cycle in the bdflush kernel threads' main loop, and adds bdflush to > scheduler runqueue list. So it gets possibility to check for emergency > sync onle when gets next scheduled. Does it ? > > Can you anyhow find something in your logs/console/serial console messages > like 13.13.2000 kernel : Sysrq: Emergency Sync (this should be present - is > written within keyboard handler, not after shedule) and what's next logs ? > We could determine, if the bdflush thread got scheduled and called emergency > syncing routine indeed. Nope, there was nothing in the logs. > As you wrote no of your processes does respond - probably telnet will > not help. You may try to write experimental programme, that only log > say current time every n seconds, and see, if it just stopped to > log messages after lockup-time. If not - it doesn't get scheduled. > If continues - there's problem with syncing. Again - try, as far > as i understand, log kernel messages to serial console or alike, because > the messages should not get written to logfiles - syslogd can't be woken up > eg. Telnet's disabled anyways :) Cleartext passwords SUCK. :) I've got a nifty LCD thingy I can hook up to the serial port and use as a console if need be. > Quick help against those corruptions, which comes on my mind, is use > the reiserfs. I have no real experiences with that and its reliability, > also as aj followed some of messages in this list about resierfs - it has > some problems too - but in definition it shoudn't get corrupted by not- > syncing reboot. But i see this not much helpfull ,cause if you really > would depend on big reliability, you wouldn't intall 2.3.x-pre kernel :) I'm not about to convert my filesystems over... It's too much a hassle for little gain. ext2 is faster anyways, IIRC. The problem disappeared when I installed 2.4.3 release; I think it was a DRM issue in the kernel that was causing the lockups Thanks for the help though Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Question about SysRq
On Wed, 4 Apr 2001, Boris Pisarcik wrote: I looked a bit at the source of sysrq handling. I've found there is rather big difference between sysrq+b and other killers handling. Sysrq+b is just called with pretty straitforward fashion - stops other processors on SMP and reboots directly (hardware impulse or triple fault) or through the bios - so it just calls for the corruptions. ah, that would explain it... On the other side sysrq+s marks a single variable, which will be tested next cycle in the bdflush kernel threads' main loop, and adds bdflush to scheduler runqueue list. So it gets possibility to check for emergency sync onle when gets next scheduled. Does it ? Can you anyhow find something in your logs/console/serial console messages like 13.13.2000 kernel : Sysrq: Emergency Sync (this should be present - is written within keyboard handler, not after shedule) and what's next logs ? We could determine, if the bdflush thread got scheduled and called emergency syncing routine indeed. Nope, there was nothing in the logs. As you wrote no of your processes does respond - probably telnet will not help. You may try to write experimental programme, that only log say current time every n seconds, and see, if it just stopped to log messages after lockup-time. If not - it doesn't get scheduled. If continues - there's problem with syncing. Again - try, as far as i understand, log kernel messages to serial console or alike, because the messages should not get written to logfiles - syslogd can't be woken up eg. Telnet's disabled anyways :) Cleartext passwords SUCK. :) I've got a nifty LCD thingy I can hook up to the serial port and use as a console if need be. Quick help against those corruptions, which comes on my mind, is use the reiserfs. I have no real experiences with that and its reliability, also as aj followed some of messages in this list about resierfs - it has some problems too - but in definition it shoudn't get corrupted by not- syncing reboot. But i see this not much helpfull ,cause if you really would depend on big reliability, you wouldn't intall 2.3.x-pre kernel :) I'm not about to convert my filesystems over... It's too much a hassle for little gain. ext2 is faster anyways, IIRC. The problem disappeared when I installed 2.4.3 release; I think it was a DRM issue in the kernel that was causing the lockups Thanks for the help though Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Question about SysRq
On Sat, 31 Mar 2001, Boris Pisarcik wrote: > on say tty2. The processes get created pretty fast. After a short while > I supposed a single solution to this to kill all session by alt+sysrq+k, > but nothing happened. Under normal averagely loaded situation, this will > imidiately kill all processes on current vt and bring getty prompt. > Shouldn't it function similiarily in former case ? I see all processes on vt > get SIGKILL, so what's hapenned ? Maybe I had to wait > a bit longer for kernel to accomplish that ? Killing all processes with init > (alt+sysrq+i) seems to be immediate. > > > Thought, i really love all sysrq properties of linux, so i need less often > to make hardware resets an then await and fear, what fsck will print. > One more property, that i'd like to have should be request key to force the > most basic text mode (say 80x25) on the console, when eg. X freezes and > i kill its session, then last gfx mode resides on the screen and see no way > to restore back the text mode - /usr/bin/reset or something alike will not > do it. But it seems to be not a good idea at all, does it ? I've noticed a similar situation: I recently upgraded to XFree86 4.0.3 and have been having nothing but problems with it. Often times, the machine will crash, with crap shot to the screen. Howver, the IP stack still functions, routes packets, but none of the user processes respond. I'll try and hit sysrq-s to sync the disks, sysrq-u to unmount them, and sysrq-b to boot the machine. Unfortunately, the only one that responds is sysrq-b, which boots the box without syncing or unmounting the disks. Not only does that piss me off but it's led to some fs corruption as well (which pisses me off even more). sysrq-b is the *only* combination I can get working when this happens. However, when the machine is *not* locked, sysrq-[su] work fine. Kernel is 2.4.3-pre6 on SMP i686. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Disturbing news..
On Wed, 28 Mar 2001, Jesse Pollard wrote: > Sure - very simple. If the execute bit is set on a file, don't allow > ANY write to the file. This does modify the permission bits slightly > but I don't think it is an unreasonable thing to have. Oh, honestly! Think about what you are saying here: What if you are developing something in an interpereted language such as perl or a shell script, where you *directly modify the executable file*? No, this won't work...Not wwithout being annoying as hell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Disturbing news..
On Wed, 28 Mar 2001, Jesse Pollard wrote: Sure - very simple. If the execute bit is set on a file, don't allow ANY write to the file. This does modify the permission bits slightly but I don't think it is an unreasonable thing to have. Oh, honestly! Think about what you are saying here: What if you are developing something in an interpereted language such as perl or a shell script, where you *directly modify the executable file*? No, this won't work...Not wwithout being annoying as hell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Question about SysRq
On Sat, 31 Mar 2001, Boris Pisarcik wrote: on say tty2. The processes get created pretty fast. After a short while I supposed a single solution to this to kill all session by alt+sysrq+k, but nothing happened. Under normal averagely loaded situation, this will imidiately kill all processes on current vt and bring getty prompt. Shouldn't it function similiarily in former case ? I see all processes on vt get SIGKILL, so what's hapenned ? Maybe I had to wait a bit longer for kernel to accomplish that ? Killing all processes with init (alt+sysrq+i) seems to be immediate. Thought, i really love all sysrq properties of linux, so i need less often to make hardware resets an then await and fear, what fsck will print. One more property, that i'd like to have should be request key to force the most basic text mode (say 80x25) on the console, when eg. X freezes and i kill its session, then last gfx mode resides on the screen and see no way to restore back the text mode - /usr/bin/reset or something alike will not do it. But it seems to be not a good idea at all, does it ? I've noticed a similar situation: I recently upgraded to XFree86 4.0.3 and have been having nothing but problems with it. Often times, the machine will crash, with crap shot to the screen. Howver, the IP stack still functions, routes packets, but none of the user processes respond. I'll try and hit sysrq-s to sync the disks, sysrq-u to unmount them, and sysrq-b to boot the machine. Unfortunately, the only one that responds is sysrq-b, which boots the box without syncing or unmounting the disks. Not only does that piss me off but it's led to some fs corruption as well (which pisses me off even more). sysrq-b is the *only* combination I can get working when this happens. However, when the machine is *not* locked, sysrq-[su] work fine. Kernel is 2.4.3-pre6 on SMP i686. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DPT Driver Status
I've got a DPT SmartCACHE IV with the raid adaptor... I'd like to get it working eventually. If you point me in the right direction I'll see if I can get that pesky driver to work, and even port over some code if need beall someone has to do is point me towards documnentation and I'll make it work. thanks, kelsey On Wed, 21 Mar 2001, Alan Cox wrote: > > Does anyone have a working patch for the 2.2.18 kernel? > > What is the most stable version of the kernel for the use of the patch? > > > > Has the native i2o driver been updated to handle what the dpt card is > > doing? > > I tried, I never managed to get the board and our i2o driver to be happy. As > far as I could tell the board was the problem end but its never easy to be 100% > sure about such things > > Alan > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec/DPT RAID Drivers [Was: Re: DPT Driver Status]
I've got a SmartCACHE IV...This driver seems not to recognize it. I applied it to 2.4.2...the patch didn't apply cleanly, however. I was able to manually patch the makefile to build the drivers for the card however, but it still didn't want to work. In any case, if you have any insight on this I'd much appreciate it, as I'd like to get the card into production ASAP. Thanks! -Kelsey On Fri, 16 Mar 2001, Omar Kilani wrote: > Marko/Dalton/Unfortunate person searching for working DPT drivers, > > I too once felt your pain. > Searched far and wide, etc. > But then I stumbled upon ftp://ftp.suse.com/pub/people/mantel/next/ > Which has patches for everything you could ever want, all integrated, if > you choose them to be. > Anyway, inside those .tgz's was version 2.0 of the DPT I2O drivers. > I've separated them from the .tgz, and stuck them up here: > > Kernel 2.2.18: > http://aurore.net/source/dpt_i2o-2.0-2.2.18.gz > > Kernel 2.4.2 > http://aurore.net/source/dpt_i2o-2.0-2.4.2.gz > > Try 'em! :-) Not sure how they compare to Markos' version. > I exchanged my ASR2100S for a Mylex AcceleRAID 170 - because DAC960 support > is so much better ;-) and I loved reading through the DAC960 sources - so > clean and easy to understand! > > Regards, > Omar Kilani > > At 03:15 PM 3/14/01 +0200, Marko Kreen wrote: > >On Wed, Mar 14, 2001 at 01:32:18AM -0500, Dalton Calford wrote: > > > I have searched the archives, hunted through the adaptec site, tried > > > multiple patches, compilers, revisions. > > > >Me too... > > > > > > > > I have a DPT/Adaptec DPT RAID V century card. This has been a topic of > > > much discussion in the past on this list. > > > > > > What I have found is that almost every file I find has a patch that is 6 > > > months old at best. > > > >When I last contacted them, couple of months ago, through > >I-dunno-how-many-middle[wo]men they assured that > >"driver is in developement" and "soon we make a release"... > > > > > I even contacted Deanna Bonds at Adaptec, but she has been unresponsive. > > > > > > Does anyone have a working patch for the 2.2.18 kernel? > > > What is the most stable version of the kernel for the use of the patch? > > > >I have ported the 1.14 version of the driver to 2.2.18. > >Basically converted their idea of patching with cp to > >normal diff and dropped all reverse changes. > > > > http://www.l-t.ee/marko/linux/dpt114-2.2.18p22.diff.gz > > > >It was for pre22 but applies cleanly to final 2.2.18. > >The other soft was most current in valinux site: > > > > http://ftp.valinux.com/pub/mirrors/dpt/ > > > > > Has the native i2o driver been updated to handle what the dpt card is > > > doing? > > > >No, the DPT driver has not been updated to native Linux i2o. > > > >Note: the driver compiles only with gcc 2.7.2.3, (dunno about > >egcs). 2.95.2 makes it acting weird. I do not know if > >thats gcc or driver problem. > > > >-- > >marko > > > >- > >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > >the body of a message to [EMAIL PROTECTED] > >More majordomo info at http://vger.kernel.org/majordomo-info.html > >Please read the FAQ at http://www.tux.org/lkml/ > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DPT Driver Status
I've got a DPT SmartCACHE IV with the raid adaptor... I'd like to get it working eventually. If you point me in the right direction I'll see if I can get that pesky driver to work, and even port over some code if need beall someone has to do is point me towards documnentation and I'll make it work. thanks, kelsey On Wed, 21 Mar 2001, Alan Cox wrote: Does anyone have a working patch for the 2.2.18 kernel? What is the most stable version of the kernel for the use of the patch? Has the native i2o driver been updated to handle what the dpt card is doing? I tried, I never managed to get the board and our i2o driver to be happy. As far as I could tell the board was the problem end but its never easy to be 100% sure about such things Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec/DPT RAID Drivers [Was: Re: DPT Driver Status]
I've got a SmartCACHE IV...This driver seems not to recognize it. I applied it to 2.4.2...the patch didn't apply cleanly, however. I was able to manually patch the makefile to build the drivers for the card however, but it still didn't want to work. In any case, if you have any insight on this I'd much appreciate it, as I'd like to get the card into production ASAP. Thanks! -Kelsey On Fri, 16 Mar 2001, Omar Kilani wrote: Marko/Dalton/Unfortunate person searching for working DPT drivers, I too once felt your pain. Searched far and wide, etc. But then I stumbled upon ftp://ftp.suse.com/pub/people/mantel/next/ Which has patches for everything you could ever want, all integrated, if you choose them to be. Anyway, inside those .tgz's was version 2.0 of the DPT I2O drivers. I've separated them from the .tgz, and stuck them up here: Kernel 2.2.18: http://aurore.net/source/dpt_i2o-2.0-2.2.18.gz Kernel 2.4.2 http://aurore.net/source/dpt_i2o-2.0-2.4.2.gz Try 'em! :-) Not sure how they compare to Markos' version. I exchanged my ASR2100S for a Mylex AcceleRAID 170 - because DAC960 support is so much better ;-) and I loved reading through the DAC960 sources - so clean and easy to understand! Regards, Omar Kilani At 03:15 PM 3/14/01 +0200, Marko Kreen wrote: On Wed, Mar 14, 2001 at 01:32:18AM -0500, Dalton Calford wrote: I have searched the archives, hunted through the adaptec site, tried multiple patches, compilers, revisions. Me too... I have a DPT/Adaptec DPT RAID V century card. This has been a topic of much discussion in the past on this list. What I have found is that almost every file I find has a patch that is 6 months old at best. When I last contacted them, couple of months ago, through I-dunno-how-many-middle[wo]men they assured that "driver is in developement" and "soon we make a release"... I even contacted Deanna Bonds at Adaptec, but she has been unresponsive. Does anyone have a working patch for the 2.2.18 kernel? What is the most stable version of the kernel for the use of the patch? I have ported the 1.14 version of the driver to 2.2.18. Basically converted their idea of patching with cp to normal diff and dropped all reverse changes. http://www.l-t.ee/marko/linux/dpt114-2.2.18p22.diff.gz It was for pre22 but applies cleanly to final 2.2.18. The other soft was most current in valinux site: http://ftp.valinux.com/pub/mirrors/dpt/ Has the native i2o driver been updated to handle what the dpt card is doing? No, the DPT driver has not been updated to native Linux i2o. Note: the driver compiles only with gcc 2.7.2.3, (dunno about egcs). 2.95.2 makes it acting weird. I do not know if thats gcc or driver problem. -- marko - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: binfmt_script and ^M
On Tue, 6 Mar 2001, Peter Samuelson wrote: > [Dr. Kelsey Hudson] > > umm, last i checked a carriage return wasn't whitespace... space, > > horizontal tab, vertical tab, form feed constitute whitespace IIRC... > > Where and when did you check? Several sources disagree with you. a long while ago... i should have checked before i opened my mouth :p Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: binfmt_script and ^M
On Tue, 6 Mar 2001, Peter Samuelson wrote: [Dr. Kelsey Hudson] umm, last i checked a carriage return wasn't whitespace... space, horizontal tab, vertical tab, form feed constitute whitespace IIRC... Where and when did you check? Several sources disagree with you. a long while ago... i should have checked before i opened my mouth :p Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: binfmt_script and ^M
On Mon, 5 Mar 2001, John Kodis wrote: > On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote: > > > Somebody must have missed the boat entirely. Unix does not, never > > has, and never will end a text line with '\r'. > > Unix does not, never has, and never will end a text line with ' ' (a > space character) or with \t (a tab character). Yet if I begin a shell > script with '#!/bin/sh ' or '#!/bin/sh\t', the training white space is > striped and /bin/sh gets exec'd. Since \r has no special significance > to Unix, I'd expect it to be treated the same as any other whitespace > character -- it should be striped, and /bin/sh should get exec'd. umm, last i checked a carriage return wasn't whitespace... space, horizontal tab, vertical tab, form feed constitute whitespace IIRC... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: binfmt_script and ^M
On Mon, 5 Mar 2001, John Kodis wrote: On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote: Somebody must have missed the boat entirely. Unix does not, never has, and never will end a text line with '\r'. Unix does not, never has, and never will end a text line with ' ' (a space character) or with \t (a tab character). Yet if I begin a shell script with '#!/bin/sh ' or '#!/bin/sh\t', the training white space is striped and /bin/sh gets exec'd. Since \r has no special significance to Unix, I'd expect it to be treated the same as any other whitespace character -- it should be striped, and /bin/sh should get exec'd. umm, last i checked a carriage return wasn't whitespace... space, horizontal tab, vertical tab, form feed constitute whitespace IIRC... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.x very unstable on 8-way IBM 8500R
On Thu, 1 Mar 2001, Matilainen Panu (NRC/Helsinki) wrote: > I've been playing around with 8-way IBM8500R (8x700MHz Xeon) with 4.5GB > memory & AIC7xxx SCSI-controller. It's perfectly stable with 2.2-kernel > (from Red Hat 7) but very erratic on all 2.4-kernels I've tried it with > (2.4.[012], compiled both with egcs and RH7's gcc-2.96, both share the Under redhat 7 you should use kgcc to compile the kernel, since gcc2.96 is inherently broken(*). > same symptoms). It did have a ServeRAID controller too but IBM suggested > we take it out since 4500R also had problems with it on 2.4 but it didn't > make any difference at all. Also tried to turn off highmem support but > didn't make difference either. (*) redhat chose to ship an experimental compiler with this release of the distribution that has a great many bugs. to ensure proper kernel compillation another proven version of gcc was included, but called kgcc instead. You should always use this to compile your kernels under redhat 7 until the newer version of gcc is released. talk to you later, Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: negative mod use count
On Wed, 28 Feb 2001, Boris Dragovic wrote: > what does negative module use count mean? That means that there's a bug in someone's driver. For some reason, the function to decrement the module use is called more than once when a controlling process releases use of a module. This will prevent you from being able to 'rmmod' or 'modprobe -r' it; a "Device or resource busy" error or similar will result IIRC. Submit a bug to the driver maintainer. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: negative mod use count
On Wed, 28 Feb 2001, Boris Dragovic wrote: what does negative module use count mean? That means that there's a bug in someone's driver. For some reason, the function to decrement the module use is called more than once when a controlling process releases use of a module. This will prevent you from being able to 'rmmod' or 'modprobe -r' it; a "Device or resource busy" error or similar will result IIRC. Submit a bug to the driver maintainer. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.x very unstable on 8-way IBM 8500R
On Thu, 1 Mar 2001, Matilainen Panu (NRC/Helsinki) wrote: I've been playing around with 8-way IBM8500R (8x700MHz Xeon) with 4.5GB memory AIC7xxx SCSI-controller. It's perfectly stable with 2.2-kernel (from Red Hat 7) but very erratic on all 2.4-kernels I've tried it with (2.4.[012], compiled both with egcs and RH7's gcc-2.96, both share the Under redhat 7 you should use kgcc to compile the kernel, since gcc2.96 is inherently broken(*). same symptoms). It did have a ServeRAID controller too but IBM suggested we take it out since 4500R also had problems with it on 2.4 but it didn't make any difference at all. Also tried to turn off highmem support but didn't make difference either. (*) redhat chose to ship an experimental compiler with this release of the distribution that has a great many bugs. to ensure proper kernel compillation another proven version of gcc was included, but called kgcc instead. You should always use this to compile your kernels under redhat 7 until the newer version of gcc is released. talk to you later, Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Linux stifles innovation...
On Wed, 21 Feb 2001, Leif Sawyer wrote: > > From: Dr. Kelsey Hudson [mailto:[EMAIL PROTECTED]] > > > > 'good' in this case was meant to mean working properly, well-coded, > > does-what-it's-suppossed-to-do, eg not broken in one way or > > another. English should have a better word that 'good...' > > > > Functional, perfect, clean, documented, readable, understandable, > tight, tuned, grok-able. exactly what i meant, with the exception possibly of 'grok-able' as i'm not familiar with that term. > Don't use one word to mean multiple things if you're trying to make > a clear case. Otherwise you sound like a Micro$oft lawyer. :-) How dare you compare me to that scum-of-the-earth! :) I do agree, though... I should have been more clear. > Really, this thread should just DIE already. It should! > We now return you to your regularly scheduled kernel bashing. Let the flames begin. :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Thu, 22 Feb 2001, Augustin Vidovic wrote: > On Wed, Feb 21, 2001 at 03:00:26PM -0800, Dr. Kelsey Hudson wrote: > > By saying this, you are implying that all pieces of code released under > > the GPL are 'good' pieces of code. > > If you want to rephrase it like that, ok, but then you must not forget > why these pieces of code are 'good' : because everybody have access to the > source code and may debug or improve it as needed. 'good' in this case was meant to mean working properly, well-coded, does-what-it's-suppossed-to-do, eg not broken in one way or another. English should have a better word that 'good...' Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Linux stifles innovation...
On Sat, 17 Feb 2001, Torrey Hoffman wrote: > On the other hand, they make excellent mice. The mouse wheel and > the new optical mice are truly innovative and Microsoft should be > commended for them. The idea of an optical mouse is nothing new: I've got an optical mouse sitting to the side of my keyboard as we speak, dated ::turns mouse over:: 1987. Produced for Sun Microsystems by Mouse Systems. Microsoft being innovative? Hell no... They stole that idea from someone else, as they have for decades (and will undoubtedly continue to do). It also wouldn't surprise me if MS is mimicing someone else's idea with the wheel... I can remember purchasing a Logitech mouse with that wheel long before I had seen a Micros~1 equivalent. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sat, 17 Feb 2001, Alan Olsen wrote: > "You keep using that word. i don't think it means what you think it > means." ...To quote Indigo Montoya, speaking to Vuzinni, from "The Princess Bride" :) One hell of a story :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sat, 17 Feb 2001, Augustin Vidovic wrote: > 1- GPL code is the opposite of crap By saying this, you are implying that all pieces of code released under the GPL are 'good' pieces of code. I can give you several examples of code where this is not the case; several I have written for my own use, as a matter of fact. Software is only as 'good' as the effort the programmer who wrote it put into it. Spend an hour writing a device driver while watching TV, eating food, and after a couple dozen beers, and release it under the GPL. Is it good code? probably not. :p This isn't, however, to say that I think commercial code is better than GPL code... They both have their merits and deficiencies, so I value both equally based upon this (although all software *should* be free...) Just my .02. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sat, 17 Feb 2001, Augustin Vidovic wrote: 1- GPL code is the opposite of crap By saying this, you are implying that all pieces of code released under the GPL are 'good' pieces of code. I can give you several examples of code where this is not the case; several I have written for my own use, as a matter of fact. Software is only as 'good' as the effort the programmer who wrote it put into it. Spend an hour writing a device driver while watching TV, eating food, and after a couple dozen beers, and release it under the GPL. Is it good code? probably not. :p This isn't, however, to say that I think commercial code is better than GPL code... They both have their merits and deficiencies, so I value both equally based upon this (although all software *should* be free...) Just my .02. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sat, 17 Feb 2001, Alan Olsen wrote: "You keep using that word. i don't think it means what you think it means." ...To quote Indigo Montoya, speaking to Vuzinni, from "The Princess Bride" :) One hell of a story :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Linux stifles innovation...
On Sat, 17 Feb 2001, Torrey Hoffman wrote: On the other hand, they make excellent mice. The mouse wheel and the new optical mice are truly innovative and Microsoft should be commended for them. The idea of an optical mouse is nothing new: I've got an optical mouse sitting to the side of my keyboard as we speak, dated ::turns mouse over:: 1987. Produced for Sun Microsystems by Mouse Systems. Microsoft being innovative? Hell no... They stole that idea from someone else, as they have for decades (and will undoubtedly continue to do). It also wouldn't surprise me if MS is mimicing someone else's idea with the wheel... I can remember purchasing a Logitech mouse with that wheel long before I had seen a Micros~1 equivalent. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Thu, 22 Feb 2001, Augustin Vidovic wrote: On Wed, Feb 21, 2001 at 03:00:26PM -0800, Dr. Kelsey Hudson wrote: By saying this, you are implying that all pieces of code released under the GPL are 'good' pieces of code. If you want to rephrase it like that, ok, but then you must not forget why these pieces of code are 'good' : because everybody have access to the source code and may debug or improve it as needed. 'good' in this case was meant to mean working properly, well-coded, does-what-it's-suppossed-to-do, eg not broken in one way or another. English should have a better word that 'good...' Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Linux stifles innovation...
On Wed, 21 Feb 2001, Leif Sawyer wrote: From: Dr. Kelsey Hudson [mailto:[EMAIL PROTECTED]] 'good' in this case was meant to mean working properly, well-coded, does-what-it's-suppossed-to-do, eg not broken in one way or another. English should have a better word that 'good...' Functional, perfect, clean, documented, readable, understandable, tight, tuned, grok-able. exactly what i meant, with the exception possibly of 'grok-able' as i'm not familiar with that term. Don't use one word to mean multiple things if you're trying to make a clear case. Otherwise you sound like a Micro$oft lawyer. :-) How dare you compare me to that scum-of-the-earth! :) I do agree, though... I should have been more clear. Really, this thread should just DIE already. It should! We now return you to your regularly scheduled kernel bashing. Let the flames begin. :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: *grin* Windows 2000 & HPC: Scalable, Inexpensive
On Wed, 14 Feb 2001, Mike Harrold wrote: > > The sad thing is, 3/4 of the page is an outright lie. It isn't > a first, W2k is not the de facto standard OS, and the TCO is > significantly higher than any cluster running Linux. No shit, not to mention that Linux is going to be faster and better suited to the task. > It's a sad day when companies can get away with blatant lies > all in the name of "marketing." Unfortunately that happens all too often. I'd _LOVE_ to be in a legal position where I could slap M$ (and any other company that does this, for that matter) and put them in their place. Feeding off the ignorance in society is counterproductive. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: *grin* Windows 2000 HPC: Scalable, Inexpensive
On Wed, 14 Feb 2001, Mike Harrold wrote: The sad thing is, 3/4 of the page is an outright lie. It isn't a first, W2k is not the de facto standard OS, and the TCO is significantly higher than any cluster running Linux. No shit, not to mention that Linux is going to be faster and better suited to the task. It's a sad day when companies can get away with blatant lies all in the name of "marketing." Unfortunately that happens all too often. I'd _LOVE_ to be in a legal position where I could slap M$ (and any other company that does this, for that matter) and put them in their place. Feeding off the ignorance in society is counterproductive. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spelling of disc (disk) in /devfs
On Thu, 1 Feb 2001, Alan Chandler wrote: > I accidentally built my 2.4.1 kernel with /devfs so had a interesting > few minutes looking round it to see what it was doing. > > The thing that struck me most was the spelling of disc with a 'c'. As > an Englishman this is the correct spelling for me most of the time, > but I have come to accept "as a technical term" disk (as in American) > is the right name for these devices. > > I now find myself confused with the new approach. It had always been my assumption that non-optical storage media used the 'disk' spelling, whereas optical media, such as CDs, DVDs, and MO, were reffered to using the 'disc' spelling. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Request: increase in PCI bus limit
On Wed, 31 Jan 2001, Scott Laird wrote: > On Wed, 31 Jan 2001, George wrote: > > Also account for anything else funny in the system. > > > > Then panic on boot if they're wrong (sort of like processor type). > > Where do cards with PCI-PCI bridges, like multiport PCI ethernet cards, > fit into this? I can easily add 3 or 4 extra busses into a box just by > grabbing a couple extra Intel dual-port Ethernet cards. Notice the 'also account for anything funny' line. Multiport ethernet cards IMO fall under this category. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: seti@home and es1371
You might also want to run setiathome with the -nice option...for instance i *always* run it with -nice 19 so that it lays in the background consuming otherwise idle cycles. anything wanting cpu time will then take it from seti. On Wed, 31 Jan 2001, Alex Deucher wrote: > Rainer, > > I'm not too familiar with the ct5880 sound chip that comes built onto > motherboards. I do know that alot of the AC'97 compliant built in sound > chips tend to let the host cpu do most of the processing involved in > playing the sound. That being said, even if you have a dedicated sound > processor, mp3 decoding is very processor intensive. It just so happens > that seti is also very processor intensive. Both of these processes are > vying for time on the cpu. Since both of these processes are so > processor intensive and the cpu can only do one thing at a time, the > performance of one or the other process will suffer from time to time. > > Alex > > > > > Hi, > > I hope you can help me. I have a problem with my on board soundcard and > seti. I have a Gigabyte GA-7ZX Creative 5880 sound chip. I use the > kernel > driver es1371 and it works goot. But when I run seti@home I got some > noise > in my sound when I play mp3 and other sound. But it is not every time > 10s > play good than for 2 s bad and than 10s good 2s bad and so on. When I > kill > seti@home every thing is ok. So what can I do? > > I have a Athlon 800 Mhz and 128 MB RAM > > cu > Rainer > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: bttv problems in 2.4.0/2.4.1
Do you have framebuffer console compiled into your kernel? I noticed similar behavior on my system when I had framebuffer console compiled in, ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as modules. System would power off when ACPI was loaded. Other times it would do other stupid things like hang abruptly for no apparent reason. On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote: > In 2.4.0 and 2.4.1, when I try to load the bttv driver, one of two > things happens: the system hangs (even alt-sysrq doesn't work!), or the > system powers off by itself (ATX mobo). Instant power-off usually > happens after a soft reboot (init 6), while it usually hangs up after a > hard reboot (power cycling). > > When it hangs, I noticed a very strange thing. If I push the power > on/off button briefly, it un-hangs and seems to proceed as normal. The > kernel does report an APIC error on each cpu (dual p3 700 system) when > this happens. > > These errors all occur in the same way (as near as I can tell) in > kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel), > 0.7.53, and 0.7.55. > > I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine. > > I have sent all this info to Gerd Knorr but, as far as I know, he hasn't > been able to track down the bug yet. I thought that by posting here, > more eyes might at least make more reports of similar situations that > might help track down the problem. > > PS: I'm not on the linux-kernel list, so please CC replies to me. > > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: bttv problems in 2.4.0/2.4.1
Do you have framebuffer console compiled into your kernel? I noticed similar behavior on my system when I had framebuffer console compiled in, ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as modules. System would power off when ACPI was loaded. Other times it would do other stupid things like hang abruptly for no apparent reason. On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote: In 2.4.0 and 2.4.1, when I try to load the bttv driver, one of two things happens: the system hangs (even alt-sysrq doesn't work!), or the system powers off by itself (ATX mobo). Instant power-off usually happens after a soft reboot (init 6), while it usually hangs up after a hard reboot (power cycling). When it hangs, I noticed a very strange thing. If I push the power on/off button briefly, it un-hangs and seems to proceed as normal. The kernel does report an APIC error on each cpu (dual p3 700 system) when this happens. These errors all occur in the same way (as near as I can tell) in kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel), 0.7.53, and 0.7.55. I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine. I have sent all this info to Gerd Knorr but, as far as I know, he hasn't been able to track down the bug yet. I thought that by posting here, more eyes might at least make more reports of similar situations that might help track down the problem. PS: I'm not on the linux-kernel list, so please CC replies to me. -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: seti@home and es1371
You might also want to run setiathome with the -nice option...for instance i *always* run it with -nice 19 so that it lays in the background consuming otherwise idle cycles. anything wanting cpu time will then take it from seti. On Wed, 31 Jan 2001, Alex Deucher wrote: Rainer, I'm not too familiar with the ct5880 sound chip that comes built onto motherboards. I do know that alot of the AC'97 compliant built in sound chips tend to let the host cpu do most of the processing involved in playing the sound. That being said, even if you have a dedicated sound processor, mp3 decoding is very processor intensive. It just so happens that seti is also very processor intensive. Both of these processes are vying for time on the cpu. Since both of these processes are so processor intensive and the cpu can only do one thing at a time, the performance of one or the other process will suffer from time to time. Alex Hi, I hope you can help me. I have a problem with my on board soundcard and seti. I have a Gigabyte GA-7ZX Creative 5880 sound chip. I use the kernel driver es1371 and it works goot. But when I run seti@home I got some noise in my sound when I play mp3 and other sound. But it is not every time 10s play good than for 2 s bad and than 10s good 2s bad and so on. When I kill seti@home every thing is ok. So what can I do? I have a Athlon 800 Mhz and 128 MB RAM cu Rainer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Request: increase in PCI bus limit
On Wed, 31 Jan 2001, Scott Laird wrote: On Wed, 31 Jan 2001, George wrote: Also account for anything else funny in the system. Then panic on boot if they're wrong (sort of like processor type). Where do cards with PCI-PCI bridges, like multiport PCI ethernet cards, fit into this? I can easily add 3 or 4 extra busses into a box just by grabbing a couple extra Intel dual-port Ethernet cards. Notice the 'also account for anything funny' line. Multiport ethernet cards IMO fall under this category. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: spelling of disc (disk) in /devfs
On Thu, 1 Feb 2001, Alan Chandler wrote: I accidentally built my 2.4.1 kernel with /devfs so had a interesting few minutes looking round it to see what it was doing. The thing that struck me most was the spelling of disc with a 'c'. As an Englishman this is the correct spelling for me most of the time, but I have come to accept "as a technical term" disk (as in American) is the right name for these devices. I now find myself confused with the new approach. It had always been my assumption that non-optical storage media used the 'disk' spelling, whereas optical media, such as CDs, DVDs, and MO, were reffered to using the 'disc' spelling. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Wed, 17 Jan 2001, Werner Almesberger wrote: > "no", because you don't have to do it in the kernel. You can mount by > uuid or label. For the root FS, you do this from an initrd. Problem > solved. > > The only cases when you really need to know the name of a disk is when > - doing disk-level management, e.g. partitioning or creating file >systems (*) > - adding a swap partition (sigh) > - telling your boot loader where to put its boot sector > > (* in principle, you could even avoid this, if you have some means of >identifying a disk (e.g. via the uuid of a file system). However, >I would consider such a solution to be overly fragile.) That's exactly my point...It doesn't need to be there; there are already ways around it. They just need to be documented, that's all. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: APIC errors
On Wed, 17 Jan 2001, Dominik Kubla wrote: > Just switched to 2.4.0-ac9 (+crypto patches) on our Dual-Pentium MMX > webserver yesterday. Works fine so far, except i keep seeing those > APIC erros (about 14 in 12 hrs) indicating receive, send and CS errors. Make sure your system is free of dust...dust can cause small errors like this to occur. Also make sure that the temperature of the system is within tolerable levels. Also, a capacitor on your motherboard could be failing...there are many different things that could cause this error. > Should i be concerned? Probably not. The errors were there before yo upgraded the kernel; they just weren't reported. Those messages are merely letting you know that an APIC retry happened. The message still got to the controller; it just had to get sent twice. good luck, -kelsey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: APIC errors
On Wed, 17 Jan 2001, Dominik Kubla wrote: Just switched to 2.4.0-ac9 (+crypto patches) on our Dual-Pentium MMX webserver yesterday. Works fine so far, except i keep seeing those APIC erros (about 14 in 12 hrs) indicating receive, send and CS errors. Make sure your system is free of dust...dust can cause small errors like this to occur. Also make sure that the temperature of the system is within tolerable levels. Also, a capacitor on your motherboard could be failing...there are many different things that could cause this error. Should i be concerned? Probably not. The errors were there before yo upgraded the kernel; they just weren't reported. Those messages are merely letting you know that an APIC retry happened. The message still got to the controller; it just had to get sent twice. good luck, -kelsey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Wed, 17 Jan 2001, Werner Almesberger wrote: "no", because you don't have to do it in the kernel. You can mount by uuid or label. For the root FS, you do this from an initrd. Problem solved. The only cases when you really need to know the name of a disk is when - doing disk-level management, e.g. partitioning or creating file systems (*) - adding a swap partition (sigh) - telling your boot loader where to put its boot sector (* in principle, you could even avoid this, if you have some means of identifying a disk (e.g. via the uuid of a file system). However, I would consider such a solution to be overly fragile.) That's exactly my point...It doesn't need to be there; there are already ways around it. They just need to be documented, that's all. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.0.37 crashes immediately
On Wed, 17 Jan 2001, Stefan Ring wrote: > 2.0.37+ kernels crash even before I can see the "Uncompressing linux..." > message. I use the same configuration for 2.0.36 and 2.0.37 (basically > it's the default configuration without anything interesting changed), and > the latter just won't work. It also doesn't matter if I use zImage or > bzImage. Kernel compiled with a stock redhat 4.2 (gcc 2.7.2.1). My machine > configuration is as follows: > > ASUS CUBX-E MB > PIII Coppermine > 512MB SDRAM > 3c905-tx > guillemot tnt2 m64 > ibm dtla-307030 & 305020, quantum fireball ex 6.4 Is there a reason you are using a relatively new machine like that with such an outdated and arcane kernel (and distribution, for that matter)? I'd suggest you upgrade to a more recent kernel and/or distribution...it'll be a lot more stable (and not to mention secure!) Good luck to you! Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Wed, 17 Jan 2001, J . A . Magallon wrote: > You want to make things SOOO easy for a 'dummy' user, and that user will never > use them. The average user you are targetting says: 'daddy, buy me a PC to > run Quake and do my school jobs' or 'please, dear vendor, I want a PC to > do my housekeeping'. I have seen so many cases (A buys PC, A tries to run > brand new racing game that does not work, A goes shop and says: don't know > what's wrong with this PC, look at it and call me when MyCarRacingGame > works...). Yup. Dummies dont need things to be done for them; they need to learn how to do it themselves. That, IMO, is the beauty of UNIX. Nothing is sugar coated, and almost everything gets back down to the K.I.S.S. approach. > Average users you are targetting with that automagical > card detection even do not know there are SCSI and IDE disks. They just > want a 30Gb ide disk to install linux and play. If they involve with SCSI > and ID numbers and multiple cards and so on they can read some docs and > rebuild a kernel. Amen! I couldn't have said it better myself. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Michael Meissner wrote: > > you're forgetting that in /etc/lilo.conf there is a directive called > > 'append='... all the user has to do is merely add > > 'append="scsihosts=whatever,whatever"' into their config file and rerun > > lilo. problem solved > > That's assuming you are using lilo. Not everybody does or can use lilo, please > don't assume that the way your system gets booted is the way everybody's does, > particularly those on platforms other than the x86. And I wasn't assuming that. There are several bootloaders for intel alone, eg syslinux and grub, to name a couple. sparc has silo, alpha has something elsewhatever. > I must say, as a 5 year Linux user (and 23 year UNIX user/administrator), I do > get tired of having to hunt down and deal with each of these changes that come > up from time to time with Linux (ie, switching from ipfwadm to ipchains to > netfilter, or in this case reordering how scsi adapters/network adapters are > looked up). I've been a Linux user/administrator for 3 years now. Before that I worked on and administered UNIX machines for about 10 years, including SunOS, HP/UX, and AIX. If you think that Linux is the only operating system to undergo vast changes like that you're wrong: look at the SunOS to Solaris switchBasically the same operating system, no? However, many things were differentOK its off topic but im sure you get the idea. > > besides, how many 'end-users' do you know of that will have multiple scsi > > adapters in one system? how many end-users -period- will have even a > > *single* scsi adapter in their systems? do we need to bloat the kernel > > with automatic things like this? no... i think it is handled fine the way > > it is. if the user wants to add more than one scsi adapter into his > > system, let him read some documentation on how to do so. (is this even a > > documented feature? if not, i think it should be added to the docs...) > > I'm an end-user, and I have 3 scsi-adapters of two different brands in my > system. Many of the people using Linux in high end things like servers, > etc. will have multiple scsi controlers. People are using Linux in lots of > things from small embedded devices to large systems, and Linux needs to address > needs in every area. see, thats where you and i disagree...I wouldn't call you an end user based upon that fact. End users (IMO) are those people who sit back and buy a PC and expect it to Just Work(tm). Servers, embedded devices, et al (read: high-end applications) do not equate to end-user applications, IMNSHO. Besides, *most* (and I say most because I've seen a sharp decline in the mentality of Linux users as of late) people who are going to manage a high-scale server are going to know what the hell they are doing in the first place, so I highly doubt that the end-user argument holds merit against this. Linux, whether you like it or not, is a full-scale UNIX. It takes a good (read: talented) system administrator to manage any UNIX properly...A good sysadmin reads documentationSeems clear enough to me. But, then again, this is coming from an experienced sysadmin so my opinion *must* be biased. Talk to you later, Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote: > [Venkatesh Ramamurthy] Dont you think that mounting and booting > based on disk label names is better, then relying on device nodes which can > change when a new card is added?. The existing patch for 2.2.xx is quite > small and it does not bloat the kernel too much either. I think we can port > it for 2.4.XX with ease.In my words it is worth the effort Of course that would be better. The only complaint I have with such a system is that of backwards compatibility...as long as the legacy device names are still supported i would have no problem with it at all. however, this brings up an interesting question: what happens if two disks (presumably from two different machines) have the same disk label? what happens then? for instance, i have several linux machines both at my workplace and my home. if for some reason one of these machines dies due to hardware failure and i want to get stuff off the drives, i put the disk containing the /home partition on the failed machine into a working machine and reboot. What /home gets mounted then? the original /home or the new one from the dead machine? (and don't say end users wouldn't possibly do that... if they are adding hardware into their systems this is by no means beyond their capabilities) at least with physical device nodes i can say 'computer, you will mount this partition on this mountpoint!' and be done with it. so tell me then, how would one discern between two partitions with the same label? just a thought Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote: > > This is due to the fixed ordering of the scsi drivers. You can change the > > order of the scsi hosts with the "scsihosts" kernel parameter. See > > linux/drivers/scsi/scsi.c > [Venkatesh Ramamurthy] I think it would be a nice idea if we can > make this process automatic , with out user typing in the order and > remembering it. The fact that a kernel developer is not using the machines > daily to get his work done should be in our minds. If we do this Linux would > become more user friendly you're forgetting that in /etc/lilo.conf there is a directive called 'append='... all the user has to do is merely add 'append="scsihosts=whatever,whatever"' into their config file and rerun lilo. problem solved besides, how many 'end-users' do you know of that will have multiple scsi adapters in one system? how many end-users -period- will have even a *single* scsi adapter in their systems? do we need to bloat the kernel with automatic things like this? no... i think it is handled fine the way it is. if the user wants to add more than one scsi adapter into his system, let him read some documentation on how to do so. (is this even a documented feature? if not, i think it should be added to the docs...) just my thoughts on the matter Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Michael Meissner wrote: you're forgetting that in /etc/lilo.conf there is a directive called 'append='... all the user has to do is merely add 'append="scsihosts=whatever,whatever"' into their config file and rerun lilo. problem solved That's assuming you are using lilo. Not everybody does or can use lilo, please don't assume that the way your system gets booted is the way everybody's does, particularly those on platforms other than the x86. And I wasn't assuming that. There are several bootloaders for intel alone, eg syslinux and grub, to name a couple. sparc has silo, alpha has something elsewhatever. I must say, as a 5 year Linux user (and 23 year UNIX user/administrator), I do get tired of having to hunt down and deal with each of these changes that come up from time to time with Linux (ie, switching from ipfwadm to ipchains to netfilter, or in this case reordering how scsi adapters/network adapters are looked up). I've been a Linux user/administrator for 3 years now. Before that I worked on and administered UNIX machines for about 10 years, including SunOS, HP/UX, and AIX. If you think that Linux is the only operating system to undergo vast changes like that you're wrong: look at the SunOS to Solaris switchBasically the same operating system, no? However, many things were differentOK its off topic but im sure you get the idea. besides, how many 'end-users' do you know of that will have multiple scsi adapters in one system? how many end-users -period- will have even a *single* scsi adapter in their systems? do we need to bloat the kernel with automatic things like this? no... i think it is handled fine the way it is. if the user wants to add more than one scsi adapter into his system, let him read some documentation on how to do so. (is this even a documented feature? if not, i think it should be added to the docs...) I'm an end-user, and I have 3 scsi-adapters of two different brands in my system. Many of the people using Linux in high end things like servers, etc. will have multiple scsi controlers. People are using Linux in lots of things from small embedded devices to large systems, and Linux needs to address needs in every area. see, thats where you and i disagree...I wouldn't call you an end user based upon that fact. End users (IMO) are those people who sit back and buy a PC and expect it to Just Work(tm). Servers, embedded devices, et al (read: high-end applications) do not equate to end-user applications, IMNSHO. Besides, *most* (and I say most because I've seen a sharp decline in the mentality of Linux users as of late) people who are going to manage a high-scale server are going to know what the hell they are doing in the first place, so I highly doubt that the end-user argument holds merit against this. Linux, whether you like it or not, is a full-scale UNIX. It takes a good (read: talented) system administrator to manage any UNIX properly...A good sysadmin reads documentationSeems clear enough to me. But, then again, this is coming from an experienced sysadmin so my opinion *must* be biased. Talk to you later, Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.0.37 crashes immediately
On Wed, 17 Jan 2001, Stefan Ring wrote: 2.0.37+ kernels crash even before I can see the "Uncompressing linux..." message. I use the same configuration for 2.0.36 and 2.0.37 (basically it's the default configuration without anything interesting changed), and the latter just won't work. It also doesn't matter if I use zImage or bzImage. Kernel compiled with a stock redhat 4.2 (gcc 2.7.2.1). My machine configuration is as follows: ASUS CUBX-E MB PIII Coppermine 512MB SDRAM 3c905-tx guillemot tnt2 m64 ibm dtla-307030 305020, quantum fireball ex 6.4 Is there a reason you are using a relatively new machine like that with such an outdated and arcane kernel (and distribution, for that matter)? I'd suggest you upgrade to a more recent kernel and/or distribution...it'll be a lot more stable (and not to mention secure!) Good luck to you! Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
On Wed, 17 Jan 2001, J . A . Magallon wrote: You want to make things SOOO easy for a 'dummy' user, and that user will never use them. The average user you are targetting says: 'daddy, buy me a PC to run Quake and do my school jobs' or 'please, dear vendor, I want a PC to do my housekeeping'. I have seen so many cases (A buys PC, A tries to run brand new racing game that does not work, A goes shop and says: don't know what's wrong with this PC, look at it and call me when MyCarRacingGame works...). Yup. Dummies dont need things to be done for them; they need to learn how to do it themselves. That, IMO, is the beauty of UNIX. Nothing is sugar coated, and almost everything gets back down to the K.I.S.S. approach. Average users you are targetting with that automagical card detection even do not know there are SCSI and IDE disks. They just want a 30Gb ide disk to install linux and play. If they involve with SCSI and ID numbers and multiple cards and so on they can read some docs and rebuild a kernel. Amen! I couldn't have said it better myself. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote: This is due to the fixed ordering of the scsi drivers. You can change the order of the scsi hosts with the "scsihosts" kernel parameter. See linux/drivers/scsi/scsi.c [Venkatesh Ramamurthy] I think it would be a nice idea if we can make this process automatic , with out user typing in the order and remembering it. The fact that a kernel developer is not using the machines daily to get his work done should be in our minds. If we do this Linux would become more user friendly you're forgetting that in /etc/lilo.conf there is a directive called 'append='... all the user has to do is merely add 'append="scsihosts=whatever,whatever"' into their config file and rerun lilo. problem solved besides, how many 'end-users' do you know of that will have multiple scsi adapters in one system? how many end-users -period- will have even a *single* scsi adapter in their systems? do we need to bloat the kernel with automatic things like this? no... i think it is handled fine the way it is. if the user wants to add more than one scsi adapter into his system, let him read some documentation on how to do so. (is this even a documented feature? if not, i think it should be added to the docs...) just my thoughts on the matter Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Linux not adhering to BIOS Drive boot order?
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote: [Venkatesh Ramamurthy] Dont you think that mounting and booting based on disk label names is better, then relying on device nodes which can change when a new card is added?. The existing patch for 2.2.xx is quite small and it does not bloat the kernel too much either. I think we can port it for 2.4.XX with ease.In my words it is worth the effort Of course that would be better. The only complaint I have with such a system is that of backwards compatibility...as long as the legacy device names are still supported i would have no problem with it at all. however, this brings up an interesting question: what happens if two disks (presumably from two different machines) have the same disk label? what happens then? for instance, i have several linux machines both at my workplace and my home. if for some reason one of these machines dies due to hardware failure and i want to get stuff off the drives, i put the disk containing the /home partition on the failed machine into a working machine and reboot. What /home gets mounted then? the original /home or the new one from the dead machine? (and don't say end users wouldn't possibly do that... if they are adding hardware into their systems this is by no means beyond their capabilities) at least with physical device nodes i can say 'computer, you will mount this partition on this mountpoint!' and be done with it. so tell me then, how would one discern between two partitions with the same label? just a thought Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: APIC ERRor on CPU0: 00(02) ...
On Sat, 13 Jan 2001, Roeland Th. Jansen wrote: > you can say about the BP6 what you want but it appears that there are > (if your vision is right) many other low end SMP boards categorized > trash. there has been one mistake with it and that's the capacitor > behind a regulator that may have been mis-dimentioned due to the > partchange of that particular capacitor. ::nods:: Yes, I realize that there are other low-end SMP boards categorized trash, but when someone asks me what low-end SMP motherboard to get, the first thing I tell them is to /not/ get the BP6. > my 2.2 kernel running on the BP6 proves that it may work very well, > unless you think that uptimes of > 40 days is bad. If you think that a stream of APIC retries is 'working very well,' then I'm sorry to say, you've got another thing coming. :p Besides, a 40 day uptime is *not* all that spectacular; I've had uptimes in excess of 200 days before, running on garbage hardware (worse than even the BP6). anyways, the fact remains that it was your motherboard that is causing these errors. The retries are still there in 2.2, they just aren't reported. ciau -Kelsey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: APIC ERRor on CPU0: 00(02) ...
This is due to your piece of trash motherboard. The reason that the older kernel didn't catch these errors is because (IIRC) it wasn't looking for them; they were there even then. The BP6 is a low-end mainboard and was engineered very poorly; these errors are due to that fact alone. Talk to you later, -Kelsey On Fri, 12 Jan 2001, V.P. wrote: > I have a Motherboard BP6 with two Celeron 500 (Not overclocked) and > Linux Kernel-2.4 > > and I have de message > > APIC error on CPU0: 00(02) > APIC error on CPU1: 00(08) > APIC error on CPU1: 08(04) > APIC error on CPU0: 02(08) > APIC error on CPU0: 08(08) > APIC error on CPU1: 04(04) > APIC error on CPU0: 08(02) > APIC error on CPU1: 04(02) > > > What wrongs ? > > This message doesn 't appears in Kernel-2.2.17 only in Kernel-2.4 > > Any Help is apreciated > > > V.P. *** Linux ** Porto *** Portugal > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: APIC ERRor on CPU0: 00(02) ...
This is due to your piece of trash motherboard. The reason that the older kernel didn't catch these errors is because (IIRC) it wasn't looking for them; they were there even then. The BP6 is a low-end mainboard and was engineered very poorly; these errors are due to that fact alone. Talk to you later, -Kelsey On Fri, 12 Jan 2001, V.P. wrote: I have a Motherboard BP6 with two Celeron 500 (Not overclocked) and Linux Kernel-2.4 and I have de message APIC error on CPU0: 00(02) APIC error on CPU1: 00(08) APIC error on CPU1: 08(04) APIC error on CPU0: 02(08) APIC error on CPU0: 08(08) APIC error on CPU1: 04(04) APIC error on CPU0: 08(02) APIC error on CPU1: 04(02) What wrongs ? This message doesn 't appears in Kernel-2.2.17 only in Kernel-2.4 Any Help is apreciated V.P. *** Linux ** Porto *** Portugal - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 'console=' kernel parameter questions
append="console=/dev/ttyS0" that should do the trick enjoy -kelsery On Mon, 8 Jan 2001, Paul Powell wrote: > Hello, > > I am running an unmodified RedHat 6.2 kernel > (kernel version 2.2.14-5.0) > > I am trying to redirect the linux startup messages to > the serial port. I've added the 'console=' parameter > to my lilo.conf file. I've tried several iterations > such as > 'console=ttys0','console=cua0','console=ttys0,9600n8', > etc > > They all fail to produce any output to the serial port > although they do remove the text from my screen. When > I have booted RedHat I can type 'echo blah > > /dev/cua0' and I see text output from the serial port. > Interestingly when I try to echo to /dev/ttys0 I get > an IO error message. I'm using a null modem cable > connect to a windows machine to watch the serial port. > > My question: why can I see output when booted into > RedHat but not when booting the OS? I've read that > you have to compile this feature into the kernel. > Does anyone know if RedHat's kernel come with this > feature built in? > > Your help appreciated, > Paul > > > __ > Do You Yahoo!? > Yahoo! Photos - Share your holiday photos online! > http://photos.yahoo.com/ > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test13-pre1 changelog
On Thu, 14 Dec 2000, David Riley wrote: > Did I miss a post from Linus on the list, or is there no posted > changelog for test13-pre1? Nothing's posted at kernel.org yet, either. > I musta missed the post too... But then again I went back and looked for it and couldnt find it so... i'd like to know what changed, anyways :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Is this a compromise and how?
It looks like you've been r00ted, dude! Someone installed a r00tk1t and you are now seeing the after-effects of it. What I'd do, in your case: back up /usr/local, /home, /etc, then reload the system clean, and replace teh backups. The system should be in a close state (read: no root kit) to before you reloaded it. Good luck! On Thu, 14 Dec 2000 [EMAIL PROTECTED] wrote: > Sorry is this is too far off topic, but it seems to me the > kernel may be helping in this break in or maybe some magic > aspect of the filesystem. > > I noted in an ls that > > -rwxr-xr-x 1 root root36784 Jul 17 05:06 rpc.mountd* > -rwxr-xr-x 1 root root 3368 Jul 17 05:06 rpc.nfsd* > -rwxr-xr-x 1 root ftp22 Sep 8 22:15 rpc.rcmd* > -rwxr-xr-x 1 root root 9872 Jul 17 05:06 rpc.rquotad* > -rwxr-xr-x 1 root root13936 Feb 9 2000 rpc.rstatd* > -rwxr-xr-x 1 root root 7952 Feb 9 2000 rpc.rusersd* > -rwxr-xr-x 1 root root 6512 Feb 11 2000 rpc.rwalld* > -rwxr-xr-x 1 root root17624 Mar 7 2000 rpc.yppasswdd* > -rwxr-xr-x 1 root root23984 Mar 7 2000 rpc.ypxfrd* > -rwxr-xr-x 1 root root10692 Sep 5 16:03 rpcinfo* > > rpc.rcmd look a little suspicious? > > And guess what it contains? > > %cat /usr/sbin/rpc.rcmd > /usr/include/strlib.h > > H. > > %ls -l /usr/include/strlib.h > -rwxr-xr-x 1 root root16768 Sep 16 09:55 /usr/include/strlib.h* > > %file /usr/include/strlib.h > /usr/include/strlib.h: ELF 32-bit LSB executable, Intel 80386, version 1, >dynamically linked (uses shared libs), not stripped > > %/usr/include/strlib.h > bind: Address already in use > > Now watch this magic trick: > > %mkdir foo > %cd foo > %touch strlib.h > %ls > %find . -print > . > ./strlib.h > % > > Get it? strlib.h never appears in the file system via ls whereever > it may be created. > > More fun: > > %echo hello >strlib.h > %ls > %cat strlib.h > hello > % > > Pretty cool huh? > > Let me know if you would like a copy of the code. > > A quick strace shows that it binds to port 24000. > > It also contains a list of 5 IP addrs. I suspect it doesn't > broadcast, but allows people in from those IPs. > > Anyone know what has happened? I religiously install the redhat > updates, and am subscribed to the CERT advistors and install > the fixes the moment I get them. > > The system was RedHat 6.2, linux 2.2.17pre14 at the time the > breakin occured. > > I've been running firewalled with only services I provide turned > on for access, and in /etc/inetd.conf. > > What is keeping strlib.h from appearing ls's? A hacked ls command? > > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: DVD on Linux
nope, DVD discs all use UDF. it'd be nice if they used something more common, but hey... On Wed, 13 Dec 2000, Gregoire Favre wrote: > zink wrote: > > > The final 2.2.18 is out - I didn't see UDF option under filesystems, altough it >should > > have been there - maybe we'll wait (for ages) untilfinal 2.4 is out. > > I haven't used 2.2 for ages, but as far as I remember, you could just use iso9660 >for DVD... > (Well since 2.2.n with n great enough...). > > Greg > > http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: DVD on Linux
nope, DVD discs all use UDF. it'd be nice if they used something more common, but hey... On Wed, 13 Dec 2000, Gregoire Favre wrote: zink wrote: The final 2.2.18 is out - I didn't see UDF option under filesystems, altough it should have been there - maybe we'll wait (for ages) untilfinal 2.4 is out. I haven't used 2.2 for ages, but as far as I remember, you could just use iso9660 for DVD... (Well since 2.2.n with n great enough...). Greg http://ulima.unil.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Is this a compromise and how?
It looks like you've been r00ted, dude! Someone installed a r00tk1t and you are now seeing the after-effects of it. What I'd do, in your case: back up /usr/local, /home, /etc, then reload the system clean, and replace teh backups. The system should be in a close state (read: no root kit) to before you reloaded it. Good luck! On Thu, 14 Dec 2000 [EMAIL PROTECTED] wrote: Sorry is this is too far off topic, but it seems to me the kernel may be helping in this break in or maybe some magic aspect of the filesystem. I noted in an ls that -rwxr-xr-x 1 root root36784 Jul 17 05:06 rpc.mountd* -rwxr-xr-x 1 root root 3368 Jul 17 05:06 rpc.nfsd* -rwxr-xr-x 1 root ftp22 Sep 8 22:15 rpc.rcmd* -rwxr-xr-x 1 root root 9872 Jul 17 05:06 rpc.rquotad* -rwxr-xr-x 1 root root13936 Feb 9 2000 rpc.rstatd* -rwxr-xr-x 1 root root 7952 Feb 9 2000 rpc.rusersd* -rwxr-xr-x 1 root root 6512 Feb 11 2000 rpc.rwalld* -rwxr-xr-x 1 root root17624 Mar 7 2000 rpc.yppasswdd* -rwxr-xr-x 1 root root23984 Mar 7 2000 rpc.ypxfrd* -rwxr-xr-x 1 root root10692 Sep 5 16:03 rpcinfo* rpc.rcmd look a little suspicious? And guess what it contains? %cat /usr/sbin/rpc.rcmd /usr/include/strlib.h H. %ls -l /usr/include/strlib.h -rwxr-xr-x 1 root root16768 Sep 16 09:55 /usr/include/strlib.h* %file /usr/include/strlib.h /usr/include/strlib.h: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses shared libs), not stripped %/usr/include/strlib.h bind: Address already in use Now watch this magic trick: %mkdir foo %cd foo %touch strlib.h %ls %find . -print . ./strlib.h % Get it? strlib.h never appears in the file system via ls whereever it may be created. More fun: %echo hello strlib.h %ls %cat strlib.h hello % Pretty cool huh? Let me know if you would like a copy of the code. A quick strace shows that it binds to port 24000. It also contains a list of 5 IP addrs. I suspect it doesn't broadcast, but allows people in from those IPs. Anyone know what has happened? I religiously install the redhat updates, and am subscribed to the CERT advistors and install the fixes the moment I get them. The system was RedHat 6.2, linux 2.2.17pre14 at the time the breakin occured. I've been running firewalled with only services I provide turned on for access, and in /etc/inetd.conf. What is keeping strlib.h from appearing ls's? A hacked ls command? -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test13-pre1 changelog
On Thu, 14 Dec 2000, David Riley wrote: Did I miss a post from Linus on the list, or is there no posted changelog for test13-pre1? Nothing's posted at kernel.org yet, either. I musta missed the post too... But then again I went back and looked for it and couldnt find it so... i'd like to know what changed, anyways :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Big IDE HD unclipping and IBM drive
Yeah, get yourself one of those nifty add-in IDE controllers that CAN see drives greater than 32GB. S'What I did and it works fine. On Fri, 8 Dec 2000, Matan Ziv-Av wrote: > > Hi, > > > I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with > large disks. I use a jumper to clip it to 32GB size, so the bios can > boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB, > and not the true size, and even trying to set the correct size with > WIN_SET_MAX fails. Is there a way to use this combination (Bios, HD, > Linux)? > > > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Signal 11
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote: > On Thu, 7 Dec 2000, Jeff V. Merkey wrote: > > > I think there may be a case when a process forks, that the MMU or some > > other subsystem is either not setting the page bits correctly, or > > mapping in a bad page. It's a LEVEL I bug in 2.4 is this is the case, > > BTW. In core dumps (I've looked at 2 of them from SSH) it barfs right > > after executing fork() or one of the exec functions and at some places > > in the code where there's not any obvious coding bugs. Looks like some > > type of mapping problem. I reported it three months ago, but it was > > pretty much ignored. > > > > Linus needs to add this one to the pre-12 list -- looks like some type > > of mapping bug. > > Now that you mention it, every app that has bombed has been the type > that forks a lot. MpegTV, gtv, and make spring to mind. All apps drive > the CPU load up quite a lot, which was why I initially suspected > overheating. I don't see it on my other 2.4 boxes though which is > suspicious. But they don't get as much of a beating as this, which was > up until last week my main workstation. Just to add some input and insight on here, I loaded the system down with some FFT algorithms, and then ran an 8-way kernel compile. The machine in question is a dual P3/600 with 512MB RAM, 2.4.0-test11. The load skyrocketed to a mere 13.6. xmms was still running, didn't skip even once. The FFT algorithms didn't bitch at all. Neither did the kernel compile. In fact, it compiled without a hitch... I dunno what to say about these boxes that segfault all the time... Probably just bad hardware somewhere along the lines. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Signal 11
On Thu, 7 Dec 2000, Peter Samuelson wrote:
>
> [Dick Johnson]
> > Do:
> >
> > char main[]={0xff,0xff,0xff,0xff};
>
> Oh come on, at least pick an *interesting* invalid opcode:
>
> char main[]={0xf0,0x0f,0xc0,0xc8}; /* try also on NT (: */
What's funny, is that this actually executes on SPARC hardware, but
immediately segfaults. On Intel hardware though, you get a message similar
to:
zsh: illegal hardware instruction (core dumped) a.out
I wrote relatively the same program in college. It exploits the F0 0F bug
found in early Pentium hardware.
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies, Inc (619) 725-0771
---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Signal 11
On Thu, 7 Dec 2000, Peter Samuelson wrote:
[Dick Johnson]
Do:
char main[]={0xff,0xff,0xff,0xff};
Oh come on, at least pick an *interesting* invalid opcode:
char main[]={0xf0,0x0f,0xc0,0xc8}; /* try also on NT (: */
What's funny, is that this actually executes on SPARC hardware, but
immediately segfaults. On Intel hardware though, you get a message similar
to:
zsh: illegal hardware instruction (core dumped) a.out
I wrote relatively the same program in college. It exploits the F0 0F bug
found in early Pentium hardware.
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies, Inc (619) 725-0771
---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Signal 11
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote: On Thu, 7 Dec 2000, Jeff V. Merkey wrote: I think there may be a case when a process forks, that the MMU or some other subsystem is either not setting the page bits correctly, or mapping in a bad page. It's a LEVEL I bug in 2.4 is this is the case, BTW. In core dumps (I've looked at 2 of them from SSH) it barfs right after executing fork() or one of the exec functions and at some places in the code where there's not any obvious coding bugs. Looks like some type of mapping problem. I reported it three months ago, but it was pretty much ignored. Linus needs to add this one to the pre-12 list -- looks like some type of mapping bug. Now that you mention it, every app that has bombed has been the type that forks a lot. MpegTV, gtv, and make spring to mind. All apps drive the CPU load up quite a lot, which was why I initially suspected overheating. I don't see it on my other 2.4 boxes though which is suspicious. But they don't get as much of a beating as this, which was up until last week my main workstation. Just to add some input and insight on here, I loaded the system down with some FFT algorithms, and then ran an 8-way kernel compile. The machine in question is a dual P3/600 with 512MB RAM, 2.4.0-test11. The load skyrocketed to a mere 13.6. xmms was still running, didn't skip even once. The FFT algorithms didn't bitch at all. Neither did the kernel compile. In fact, it compiled without a hitch... I dunno what to say about these boxes that segfault all the time... Probably just bad hardware somewhere along the lines. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: D-LINK DFE-530-TX
It uses the via-rhine driver on my system On Thu, 7 Dec 2000, James Bourne wrote: > On Wed, 6 Dec 2000, Mike A. Harris wrote: > > > Which ethernet module works with this card? 2.2.17 kernel > > Should be the rtl8139 driver. > > Regards, > Jim > > > -- > > Mike A. Harris - Linux advocate - Open source advocate > > This message is copyright 2000, all rights reserved. > > Views expressed are my own, not necessarily shared by my employer. > > -- > > -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: D-LINK DFE-530-TX
It uses the via-rhine driver on my system On Thu, 7 Dec 2000, James Bourne wrote: On Wed, 6 Dec 2000, Mike A. Harris wrote: Which ethernet module works with this card? 2.2.17 kernel Should be the rtl8139 driver. Regards, Jim -- Mike A. Harris - Linux advocate - Open source advocate This message is copyright 2000, all rights reserved. Views expressed are my own, not necessarily shared by my employer. -- -- Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote: > No, it does not. Distributing does. You will never get this right. You > can compile into your kernel anything you like as long as you don't > give it away. You are wrong: If you modify the kernel you have to make it available for anyone who wishes to use it; that's also in the GPL. You can't add stuff to it and then not distribute it, that's in violation. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote: No, it does not. Distributing does. You will never get this right. You can compile into your kernel anything you like as long as you don't give it away. You are wrong: If you modify the kernel you have to make it available for anyone who wishes to use it; that's also in the GPL. You can't add stuff to it and then not distribute it, that's in violation. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: mount /mnt/cdrom ok!but ls segmentation fault...
On Sun, 19 Nov 2000, Vincent wrote: > Using linux-2.4.0-test11-pre7 right now..., here's what i did, > mount /mnt/cdrom > cd /mnt/cdrom > ls > Segmentation fault > ls > *NOT Responding* > can't kill /sbin/ls > can't umount /mnt/cdrom > ps , shows ; > > 613 ?D 0:00 /bin/ls --color=auto -F -b -T 0 >^ > > i didn't want to reboot... > CDRom door is locked.. > > BTW, what does D mean in ps? It's somewhat comforting to know that someone else has the same problem as I do. I'd be willing to bet that he's using SCSI hostadapter emulation with this. I am, and it only started happening as soon as I enabled it. Any ideas? I need the sg stuff for my CD recorder to work properly... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: mount /mnt/cdrom ok!but ls segmentation fault...
On Sun, 19 Nov 2000, Vincent wrote: Using linux-2.4.0-test11-pre7 right now..., here's what i did, mount /mnt/cdrom cd /mnt/cdrom ls Segmentation fault ls *NOT Responding* can't kill /sbin/ls can't umount /mnt/cdrom ps , shows ; 613 ?D 0:00 /bin/ls --color=auto -F -b -T 0 ^ i didn't want to reboot... CDRom door is locked.. BTW, what does D mean in ps? It's somewhat comforting to know that someone else has the same problem as I do. I'd be willing to bet that he's using SCSI hostadapter emulation with this. I am, and it only started happening as soon as I enabled it. Any ideas? I need the sg stuff for my CD recorder to work properly... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Dual XEON - >>SLOW<< on SMP
> This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII > chipset. Strange, I've got a dual Katmai (non-Xeon) and notice the same... CPU0 CPU1 0: 95135438 95720832IO-APIC-edge timer 1: 579101 572402IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3:14149121423496IO-APIC-edge serial 5:55632315551230IO-APIC-edge soundblaster 9: 0 0IO-APIC-edge acpi 10: 10945738 10944261 IO-APIC-level eth0 11: 696382 700477 IO-APIC-level ide0, ide1 12:72511647251575IO-APIC-edge PS/2 Mouse 13: 0 0 XT-PIC fpu 14:30792383079438 IO-APIC-level eth1 15:111130 IO-APIC-level bttv NMI: 190856196 190856196 LOC: 190858464 190858463 ERR: 0 This cannot be good... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Dual XEON - SLOW on SMP
This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII chipset. Strange, I've got a dual Katmai (non-Xeon) and notice the same... CPU0 CPU1 0: 95135438 95720832IO-APIC-edge timer 1: 579101 572402IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3:14149121423496IO-APIC-edge serial 5:55632315551230IO-APIC-edge soundblaster 9: 0 0IO-APIC-edge acpi 10: 10945738 10944261 IO-APIC-level eth0 11: 696382 700477 IO-APIC-level ide0, ide1 12:72511647251575IO-APIC-edge PS/2 Mouse 13: 0 0 XT-PIC fpu 14:30792383079438 IO-APIC-level eth1 15:111130 IO-APIC-level bttv NMI: 190856196 190856196 LOC: 190858464 190858463 ERR: 0 This cannot be good... Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Off-Topic (or maybe on-topic)
On Fri, 27 Oct 2000 [EMAIL PROTECTED] wrote: > If Bill said 'screw you' to the blackmailer and made the press release, > we should see the source on web sites soon. Then we can see how bad it > really is. Maybe even fix it. Why bother fixing it? It's too bloated and stupid in the first place...That's why we run Linux. Anyways, this is really causing too much clutter for this list. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Off-Topic (or maybe on-topic)
On Fri, 27 Oct 2000 [EMAIL PROTECTED] wrote: If Bill said 'screw you' to the blackmailer and made the press release, we should see the source on web sites soon. Then we can see how bad it really is. Maybe even fix it. Why bother fixing it? It's too bloated and stupid in the first place...That's why we run Linux. Anyways, this is really causing too much clutter for this list. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PC speaker driver patch for 2.4.0-test10-pre3
> Is there a major compelling reason that this patch isn't included > in the standard kernel tree? > > > -- > Mike A. Harris - Linux advocate - Open source advocate > Computer Consultant - Capslock Consulting > Copyright 2000 all rights reserved > -- Apparently Linus doesn't like the way it handles interrupts or something, and is therefore 'wrong.' ::shrug:: As long as it's available though, I'll use it ;p Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PC speaker driver patch for 2.4.0-test10-pre3
Is there a major compelling reason that this patch isn't included in the standard kernel tree? -- Mike A. Harris - Linux advocate - Open source advocate Computer Consultant - Capslock Consulting Copyright 2000 all rights reserved -- Apparently Linus doesn't like the way it handles interrupts or something, and is therefore 'wrong.' ::shrug:: As long as it's available though, I'll use it ;p Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
aaaah! complete lockup 2.4.0-test9 SPARC32
I just had my box completely lock up under 2.4.0-test9. I had insmodded the dbri.o audio driver, which for some reason was refusing to work, at all. So I rmmodded it, and at that point, the screen flickered once and wham, complete lockup, nothing responds at all, no network, no SysRQ, anything...Not even an oops printed to the screen. Machine: SPARCstation 20, 1xTMS390Z55 50MHz SuperSPARC II w/1MB SuperCACHE 48MB RAM, about 9G total disk space spanned over 3 drives, TGX... Lemme know if you need more info. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre8 on SPARC build failure
On Wed, 4 Oct 2000, Jakub Jelinek wrote: > This does tell nothing if the pcibios thing is fixed or not, because you > most probably did not configure PCI on your sparc32 (why would you do that, > when you don't have a JavaStation?). > So you have to either look at the code or configure PCI in... Of course it does. When I compiled it before I didn't have PCI support on either, but it tried to compile it anyways, and barfed and died. It no longer barfs and dies, so yes, it is fixed. :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre8 on SPARC build failure
On Wed, 4 Oct 2000, Jakub Jelinek wrote: This does tell nothing if the pcibios thing is fixed or not, because you most probably did not configure PCI on your sparc32 (why would you do that, when you don't have a JavaStation?). So you have to either look at the code or configure PCI in... Of course it does. When I compiled it before I didn't have PCI support on either, but it tried to compile it anyways, and barfed and died. It no longer barfs and dies, so yes, it is fixed. :) Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
aaaah! complete lockup 2.4.0-test9 SPARC32
I just had my box completely lock up under 2.4.0-test9. I had insmodded the dbri.o audio driver, which for some reason was refusing to work, at all. So I rmmodded it, and at that point, the screen flickered once and wham, complete lockup, nothing responds at all, no network, no SysRQ, anything...Not even an oops printed to the screen. Machine: SPARCstation 20, 1xTMS390Z55 50MHz SuperSPARC II w/1MB SuperCACHE 48MB RAM, about 9G total disk space spanned over 3 drives, TGX... Lemme know if you need more info. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre8 on SPARC build failure
> Question is, is this still broken on -test9-final or did > the fix Linus merged earlier today get rid of your problems? Let me try this and find out... Hmm. I get an error when trying to run 'make xconfig': gmake[1]: Entering directory `/usr/src/linux-2.4.0-test9/scripts' cat header.tk >> ./kconfig.tk ./tkparse < ../arch/sparc/config.in >> kconfig.tk -: 97: unknown command gmake[1]: *** [kconfig.tk] Error 1 OK, Big deal. I'll use menuconfig. That seems to work... making dep... ::curses his SS20 for being so SLOW!:: I need better than a 50MHz processor in this damn thing. :) Better yet, I need a better machine! :) Got any donations? Just kidding. ...Ok...Making boot... Damn. A good 2 hours later and it looks as though the compile exited cleanly :) yaaay! The answer to your question is yes, the fix Linus put in today fixed the problem :) Talk to you later, Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre8 on SPARC build failure
> pcic.c: At top level: > pcic.c:39: redefinition of `pcibios_present' > /usr/src/linux-2.4.0-test/include/linux/pci.h:562: `pcibios_present' previously >defined here > make[1]: *** [pcic.o] Error 1 > make[1]: Leaving directory `/usr/src/linux-2.4.0-test/arch/sparc/kernel' > make: *** [_dir_arch/sparc/kernel] Error 2 I can confirm this. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre8 on SPARC build failure
pcic.c: At top level: pcic.c:39: redefinition of `pcibios_present' /usr/src/linux-2.4.0-test/include/linux/pci.h:562: `pcibios_present' previously defined here make[1]: *** [pcic.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.0-test/arch/sparc/kernel' make: *** [_dir_arch/sparc/kernel] Error 2 I can confirm this. Kelsey Hudson [EMAIL PROTECTED] Software Engineer Compendium Technologies, Inc (619) 725-0771 --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
