Re: gcc: internal compiler error: program cc1 got fatal signal 11
At 10:20 AM 6/29/01, you wrote: >Almost always ? >It seems like gcc is THE ONLY program which gets >signal 11 >Why the X server doesn't get signal 11 ? >Why others programs don't get signal 11 ? > >I remember that once Bill Gates was asked about >crashes in windows and he said: It's a hardware >problem. >It was also a joke on that subject: >Winerr xxx: Hardware problem (it's not our fault, it's >not, it's not, it's not, it's not...) > > >Seems to me like Micro$oft way of handling problems. > >We must agree that gcc is full of bugs (xanim does not >run corectly if it is compiled with gcc 2.95.3 >and other programs which use floating point >calculations do the same (spice 3f5)) All versions of gcc have bugs. They generally show up as incorrect complaints about the source code, as generated code that is less than optimal or that is flat out wrong. With this kind of bug, if you compile the program twice you'll get the same (buggy) result. Sig 11 is a bit different. With a compiler bug causing the sig 11, the problem will happen EVERY time you compile the given file - because the compiler is busted. This kind of problem is detected early in the compiler's life cycle and gets fixed. Then there are the intermittent sig 11 errors. If the software was broken, the sig 11 would happen whenever you do the same thing. Being able to compile a bunch of files, get a sig 11, compile a bunch more, sig 11, a bunch more ... is a sign that the problem isn't the compiler. Peoples' experience over the years has shown that symptoms of this type are cause by (intermittent) hardware problems. Why does this affect gcc more than other programs? Because gcc uses gazillions of pointers and bad memory causes bad pointers causes sig 11. Hope this helps. David P.S. Years ago, installing OS/2 on an apparently 100% working system would show similar problems. OS/2 was the first widely used 32 bit operating system on Intel hardware. It exercised the hardware differently from DOS, Windows, etc and flaky memory would make itself known. The usual reaction was "But my system worked fine before OS/2" The response was "different software exercises the hardware differently and may reveal unsuspected problems". David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: internal compiler error: program cc1 got fatal signal 11
At 10:20 AM 6/29/01, you wrote: Almost always ? It seems like gcc is THE ONLY program which gets signal 11 Why the X server doesn't get signal 11 ? Why others programs don't get signal 11 ? I remember that once Bill Gates was asked about crashes in windows and he said: It's a hardware problem. It was also a joke on that subject: Winerr xxx: Hardware problem (it's not our fault, it's not, it's not, it's not, it's not...) Seems to me like Micro$oft way of handling problems. We must agree that gcc is full of bugs (xanim does not run corectly if it is compiled with gcc 2.95.3 and other programs which use floating point calculations do the same (spice 3f5)) All versions of gcc have bugs. They generally show up as incorrect complaints about the source code, as generated code that is less than optimal or that is flat out wrong. With this kind of bug, if you compile the program twice you'll get the same (buggy) result. Sig 11 is a bit different. With a compiler bug causing the sig 11, the problem will happen EVERY time you compile the given file - because the compiler is busted. This kind of problem is detected early in the compiler's life cycle and gets fixed. Then there are the intermittent sig 11 errors. If the software was broken, the sig 11 would happen whenever you do the same thing. Being able to compile a bunch of files, get a sig 11, compile a bunch more, sig 11, a bunch more ... is a sign that the problem isn't the compiler. Peoples' experience over the years has shown that symptoms of this type are cause by (intermittent) hardware problems. Why does this affect gcc more than other programs? Because gcc uses gazillions of pointers and bad memory causes bad pointers causes sig 11. Hope this helps. David P.S. Years ago, installing OS/2 on an apparently 100% working system would show similar problems. OS/2 was the first widely used 32 bit operating system on Intel hardware. It exercised the hardware differently from DOS, Windows, etc and flaky memory would make itself known. The usual reaction was But my system worked fine before OS/2 The response was different software exercises the hardware differently and may reveal unsuspected problems. David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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/
Final Warning [ was: ECN is on! ]
At 10:18 AM 5/22/01, Steve Modica wrote: >Perhaps it's none of my business, but it doesn't seem very sporting to >just turn something on that breaks stuff and say "you had fair >warning". Why not shut it back off, issue a statement saying it works >now and will be re-enabled on June 10th or something, and everyone must >do thus and so or they will break on that day? > >Vague things like "it'll be turned on real soon now" or ASAP really mean >"never" since admins always have things with real deadlines at the top >of their list. I'd suggest something like: Final Warning. ECN is being turned on NOW. If your firewall doesn't support ECN, this will be the last message that gets through to you from us. Such a message will have the interesting characteristic of being the last message received. This will make it obvious why no further messages are arriving. David ---- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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/
Final Warning [ was: ECN is on! ]
At 10:18 AM 5/22/01, Steve Modica wrote: Perhaps it's none of my business, but it doesn't seem very sporting to just turn something on that breaks stuff and say you had fair warning. Why not shut it back off, issue a statement saying it works now and will be re-enabled on June 10th or something, and everyone must do thus and so or they will break on that day? Vague things like it'll be turned on real soon now or ASAP really mean never since admins always have things with real deadlines at the top of their list. I'd suggest something like: Final Warning. ECN is being turned on NOW. If your firewall doesn't support ECN, this will be the last message that gets through to you from us. Such a message will have the interesting characteristic of being the last message received. This will make it obvious why no further messages are arriving. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
At 12:17 PM 4/29/01, Steve 'Denali' McKnelly wrote: >Howdy J.A., > > Let me ask a possibly stupid question... How do you tell >what version of the Gibbs Adaptec driver you're using? Did I >misunderstand you when you said the 2.4.4 kernel is using 6.1.5? >Also, did I understand you to say the 6.1.12 version will fix >my unresolved symbol problem? > >Thanks, >Steve Steve, A message saying (roughly) AIC7XXX 6.1.xxx appears while the kernel is loading. You can also grep the aic7xxx.c source file or run the strings command ( strings /lib/modules/2.4.4/kernel/drivers/scsi/aic7xxx ). I'm not sure about your undefined symbols problem, but I was able to build 2.4.4 with 6.1.11 with no trouble. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
At 12:17 PM 4/29/01, Steve 'Denali' McKnelly wrote: Howdy J.A., Let me ask a possibly stupid question... How do you tell what version of the Gibbs Adaptec driver you're using? Did I misunderstand you when you said the 2.4.4 kernel is using 6.1.5? Also, did I understand you to say the 6.1.12 version will fix my unresolved symbol problem? Thanks, Steve Steve, A message saying (roughly) AIC7XXX 6.1.xxx appears while the kernel is loading. You can also grep the aic7xxx.c source file or run the strings command ( strings /lib/modules/2.4.4/kernel/drivers/scsi/aic7xxx ). I'm not sure about your undefined symbols problem, but I was able to build 2.4.4 with 6.1.11 with no trouble. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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 2940 and Linux 2.2.19
Subba, The 2940 uses an AIC7890 (or related) chip. Look for AIC7XXX in the options. David At 03:45 PM 4/17/01, Subba Rao wrote: >Hi, > >The kernel configuration menu items have been changing quite a bit. So, I >apologize for asking a trivial question in this forum. > >I am trying to configure and install linux kernel 2.2.19. This system has >a Adaptec 2940 SCSI adapter. I have enabled SCSI support kernel configuration >menu and also have selected all the Adaptec low-level drivers. They include >(actually what is offered), AHA152X/2825, AHA1542 and AHA1740. When the kernel >is booting up it still does not find the AHA2940 adapter. > >What (other) options should I configure to make Linux 2.2.19 find the adapter? > >Thank you in advance for any help. >-- > >Subba Rao >[EMAIL PROTECTED] >http://members.home.net/subba9/ > >GPG public key ID 27FC9217 >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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 2940 and Linux 2.2.19
Subba, The 2940 uses an AIC7890 (or related) chip. Look for AIC7XXX in the options. David At 03:45 PM 4/17/01, Subba Rao wrote: Hi, The kernel configuration menu items have been changing quite a bit. So, I apologize for asking a trivial question in this forum. I am trying to configure and install linux kernel 2.2.19. This system has a Adaptec 2940 SCSI adapter. I have enabled SCSI support kernel configuration menu and also have selected all the Adaptec low-level drivers. They include (actually what is offered), AHA152X/2825, AHA1542 and AHA1740. When the kernel is booting up it still does not find the AHA2940 adapter. What (other) options should I configure to make Linux 2.2.19 find the adapter? Thank you in advance for any help. -- Subba Rao [EMAIL PROTECTED] http://members.home.net/subba9/ GPG public key ID 27FC9217 - 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/ -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: aic7xxx 6.1.8 for 2.2.19
At 10:54 AM 4/1/01, Mike Bennett wrote: >Was getting ready to compile 2.2.19 this AM and went to >Justin's site to grab the latest aic7xxx driver. > >Unfortunately, he doesn't have a patch for 2.2.19 and the >2.2.18 patch doesn't apply cleanly because the stock driver >changed. > >It's a long story, but the short version is that the stock >driver has always given me timeouts with heavy disk activity. >Right now I'm using 6.0.8beta in 2.2.18 since Jan 12 and have >not had a single timeout problem. Needless to say, I won't be >upgrading kernels today. Damn, now I've got no excuse for >not mowing the lawn... :) No excuse needed here in Ann Arbor, Michigan. This morning lawn mowing is a non-issue. It's snowing merrily - just like it was winter. >Has anyone made a patch against 2.2.19 ? > >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: aic7xxx 6.1.8 for 2.2.19
At 10:54 AM 4/1/01, Mike Bennett wrote: Was getting ready to compile 2.2.19 this AM and went to Justin's site to grab the latest aic7xxx driver. Unfortunately, he doesn't have a patch for 2.2.19 and the 2.2.18 patch doesn't apply cleanly because the stock driver changed. It's a long story, but the short version is that the stock driver has always given me timeouts with heavy disk activity. Right now I'm using 6.0.8beta in 2.2.18 since Jan 12 and have not had a single timeout problem. Needless to say, I won't be upgrading kernels today. Damn, now I've got no excuse for not mowing the lawn... :) No excuse needed here in Ann Arbor, Michigan. This morning lawn mowing is a non-issue. It's snowing merrily - just like it was winter. Has anyone made a patch against 2.2.19 ? - 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/ -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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.2.18 - do_try_to_free_pages failed
Thiago, I know that 2.2.19 is still in the -pre state. Is it that much better? Have significant VM problems been fixed? Thanks. David At 08:48 PM 3/6/01, Thiago Rondon wrote: > > Mar 6 16:35:32 osage kernel: VM: do_try_to_free_pages failed for kswapd... > >Update your kernel to 2.2.19 and try again. > >- >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/
2.2.18 - do_try_to_free_pages failed
This is my first report of a kernel crash, so if there is more information wanted, please let me know and I'll do my best to supply it. I'm running Mandrake 7.2 with a 2.2.18 kernel and GNOME, PIII 500 mhz, 256MB ram, AIC789x SCSI on mobo, Fujitsu 18GB scsi HD, ATI video card. This evening, xscreensaver crashed with a message saying (roughly): "xscreensaver hypercube had(?) a SIGSEGV" I had to power down the machine and restart it. From /var/log/messages the last message before the reboot and the first message after the reboot are: Mar 6 16:35:32 osage kernel: VM: do_try_to_free_pages failed for kswapd... Mar 6 17:13:04 osage syslogd 1.4-0: restart. 2.2.18 has run for as long as 71 days on this machine (at which point I restarted it to include the Sangoma WANROUTER driver, which was NOT running at the time of the crash). I'll be glad to supply any additional info/files. Just let me know what's wanted. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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/
2.2.18 - do_try_to_free_pages failed
This is my first report of a kernel crash, so if there is more information wanted, please let me know and I'll do my best to supply it. I'm running Mandrake 7.2 with a 2.2.18 kernel and GNOME, PIII 500 mhz, 256MB ram, AIC789x SCSI on mobo, Fujitsu 18GB scsi HD, ATI video card. This evening, xscreensaver crashed with a message saying (roughly): "xscreensaver hypercube had(?) a SIGSEGV" I had to power down the machine and restart it. From /var/log/messages the last message before the reboot and the first message after the reboot are: Mar 6 16:35:32 osage kernel: VM: do_try_to_free_pages failed for kswapd... Mar 6 17:13:04 osage syslogd 1.4-0: restart. 2.2.18 has run for as long as 71 days on this machine (at which point I restarted it to include the Sangoma WANROUTER driver, which was NOT running at the time of the crash). I'll be glad to supply any additional info/files. Just let me know what's wanted. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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.2.18 - do_try_to_free_pages failed
Thiago, I know that 2.2.19 is still in the -pre state. Is it that much better? Have significant VM problems been fixed? Thanks. David At 08:48 PM 3/6/01, Thiago Rondon wrote: Mar 6 16:35:32 osage kernel: VM: do_try_to_free_pages failed for kswapd... Update your kernel to 2.2.19 and try again. - 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/
Re: Posible bug in gcc
At 01:02 PM 2/26/01, Alan Cox wrote: > > > Well gcc-bugs would be the better place to send it but this is a > known problem > > > fixed in CVS gcc 2.95.3, CVS gcc 3.0 branch and gcc 2.96 (unofficial, > Red Hat) > > > > I'm not sure if it is known, at least not known to me, but definitely not > > fixed in any of gcc 2.95.2, CVS gcc 3.0 branch, CVS gcc 3.1 head, gcc > 2.96-RH. > >Sorry my error for assuming it was the exsting known strength reduce bug It's broken in my copy of gcc.2.95.3 ... David - 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: Posible bug in gcc
At 01:02 PM 2/26/01, Alan Cox wrote: Well gcc-bugs would be the better place to send it but this is a known problem fixed in CVS gcc 2.95.3, CVS gcc 3.0 branch and gcc 2.96 (unofficial, Red Hat) I'm not sure if it is known, at least not known to me, but definitely not fixed in any of gcc 2.95.2, CVS gcc 3.0 branch, CVS gcc 3.1 head, gcc 2.96-RH. Sorry my error for assuming it was the exsting known strength reduce bug It's broken in my copy of gcc.2.95.3 ... David - 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: XOR [ was: Linux stifles innovation... ]
At 09:32 PM 2/16/01, Dan Hollis wrote: >On Fri, 16 Feb 2001, David Relson wrote: > > At 08:52 PM 2/16/01, you wrote: > > > On Fri, 16 Feb 2001, Michael H. Warfield wrote: > > > > > You know XOR is patented (yes, the logical bit operation XOR). > > > > But wasn't that Xerox that had that? > > > US Patent #4,197,590 held by NuGraphics, Inc. > > The patent was for using the technique of using XOR for dragging/moving > > parts of a graphics image without erasing other parts. Also, since the > > patent was granted in 1980, the inventors have had their 17 years of patent > > protection, and we're all free to use the technique - legally! > >So you approve of 4,197,590 and think it was an innovative and non obvious >invention in 1980? > >-Dan Dan, No, I didn't say I approved of the patent. I merely reported a bit of the when and what of the patent and said that that is no longer relevant, i.e. it's not a concern. I don't approve of software patents. I think the idea of granting software patents is a bad idea. As programmers solving problems everyday, we are constantly developing techniques for dealing with new problems or finding new and better solutions for old problems. This is a process of continuous invention carried out simultaneously and independently in many places. Putting patent restrictions on this process is a bad idea. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: XOR [ was: Linux stifles innovation... ]
At 09:32 PM 2/16/01, Dan Hollis wrote: On Fri, 16 Feb 2001, David Relson wrote: At 08:52 PM 2/16/01, you wrote: On Fri, 16 Feb 2001, Michael H. Warfield wrote: You know XOR is patented (yes, the logical bit operation XOR). But wasn't that Xerox that had that? US Patent #4,197,590 held by NuGraphics, Inc. The patent was for using the technique of using XOR for dragging/moving parts of a graphics image without erasing other parts. Also, since the patent was granted in 1980, the inventors have had their 17 years of patent protection, and we're all free to use the technique - legally! So you approve of 4,197,590 and think it was an innovative and non obvious invention in 1980? -Dan Dan, No, I didn't say I approved of the patent. I merely reported a bit of the when and what of the patent and said that that is no longer relevant, i.e. it's not a concern. I don't approve of software patents. I think the idea of granting software patents is a bad idea. As programmers solving problems everyday, we are constantly developing techniques for dealing with new problems or finding new and better solutions for old problems. This is a process of continuous invention carried out simultaneously and independently in many places. Putting patent restrictions on this process is a bad idea. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: XOR [ was: Linux stifles innovation... ]
At 08:52 PM 2/16/01, you wrote: > On Fri, 16 Feb 2001, Michael H. Warfield wrote: > > > You know XOR is patented (yes, the logical bit operation XOR). > >But wasn't that Xerox that had that? > > US Patent #4,197,590 held by NuGraphics, Inc. The patent was for using the technique of using XOR for dragging/moving parts of a graphics image without erasing other parts. Also, since the patent was granted in 1980, the inventors have had their 17 years of patent protection, and we're all free to use the technique - legally! David P.S. Given that XOR is a basic boolean operation, I don't think the USPTO would ever be so dumb as to grant a patent on it. But, then the PTO has shown a creative ability to grant patents to questionable ideas, so who can say what they would/could/will do? - 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: XOR [ was: Linux stifles innovation... ]
At 08:52 PM 2/16/01, you wrote: On Fri, 16 Feb 2001, Michael H. Warfield wrote: You know XOR is patented (yes, the logical bit operation XOR). But wasn't that Xerox that had that? US Patent #4,197,590 held by NuGraphics, Inc. The patent was for using the technique of using XOR for dragging/moving parts of a graphics image without erasing other parts. Also, since the patent was granted in 1980, the inventors have had their 17 years of patent protection, and we're all free to use the technique - legally! David P.S. Given that XOR is a basic boolean operation, I don't think the USPTO would ever be so dumb as to grant a patent on it. But, then the PTO has shown a creative ability to grant patents to questionable ideas, so who can say what they would/could/will do? - 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: make mrproper
Matti, My recollection as a 50+ american is that the household cleaner Mr. Clean has been around since at least the 1960's. I remember vividly the TV advertisements with the bald headed genie (or whatever) with his arms crossed and inspecting dirt or cleanliness or whatever. With my US-centric upbringing, I think that Mr. Clean originated here and then went overseas, with appropriate translations of the product name, hence the appearance of Mr. Proper. That's what I know about Mr. Clean vs. Mr. Proper. I believe it correct, but I'm not a Procter & Gamble historian. David At 09:21 AM 1/25/01, Matti Aarnio wrote: >On Thu, Jan 25, 2001 at 09:00:26AM -0500, James Lewis Nance wrote: > > On Wed, Jan 24, 2001 at 05:33:02PM +, [EMAIL PROTECTED] wrote: > > > Long ago, about January 24, Joseph wrote: > > > > >From John Levon on Wednesday, 24 January, 2001: > > > > >Idle curiosity, but what does the "mr" in make mrproper > > > > >stand for ? > >It does refer to Procter household cleaning product >titled "Mr Proper", which apparently more recently has been >renamed as "Mr Clean". (Or who knows how international companies >decide on what to call the products where...) > >A semi-joke which may or may not make sense to people depending >on if they have seen the adverts that at least Finns have seen.. >(I guess it was american advertisement dubbed into finnish.) > >"'make clean' is simple soap wash, 'make mrproper' cleans also > tougher stains by using stronger solvents; user is advised to > protect themselves." > >/Matti Aarnio >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: make mrproper
Matti, My recollection as a 50+ american is that the household cleaner Mr. Clean has been around since at least the 1960's. I remember vividly the TV advertisements with the bald headed genie (or whatever) with his arms crossed and inspecting dirt or cleanliness or whatever. With my US-centric upbringing, I think that Mr. Clean originated here and then went overseas, with appropriate translations of the product name, hence the appearance of Mr. Proper. That's what I know about Mr. Clean vs. Mr. Proper. I believe it correct, but I'm not a Procter Gamble historian. David At 09:21 AM 1/25/01, Matti Aarnio wrote: On Thu, Jan 25, 2001 at 09:00:26AM -0500, James Lewis Nance wrote: On Wed, Jan 24, 2001 at 05:33:02PM +, [EMAIL PROTECTED] wrote: Long ago, about January 24, Joseph wrote: From John Levon on Wednesday, 24 January, 2001: Idle curiosity, but what does the "mr" in make mrproper stand for ? It does refer to ProcterGamble household cleaning product titled "Mr Proper", which apparently more recently has been renamed as "Mr Clean". (Or who knows how international companies decide on what to call the products where...) A semi-joke which may or may not make sense to people depending on if they have seen the adverts that at least Finns have seen.. (I guess it was american advertisement dubbed into finnish.) "'make clean' is simple soap wash, 'make mrproper' cleans also tougher stains by using stronger solvents; user is advised to protect themselves." /Matti Aarnio - 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/ -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com tel: 734.821.8800 - 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: [PATCH] Processor autodetection (when configuring kernel)
Giacomo,
Further experimentation has revealed another problem with the script. The
use of curly braces in the case statement, i.e.
GenuineIntel:6:{8,9,11}) echo CONFIG_M686FXSR ;;
does not work. The construct below works, but I don't like it because of
its length:
GenuineIntel:6:8|GenuineIntel:6:9|GenuineIntel:6:11) echo
CONFIG_M686FXSR ;;
David
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
-
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: [PATCH] Processor autodetection (when configuring kernel)
Giacomo,
I don't think cpu_info.sh is quite right. It identified my 500 Mhz Pentium
III as CONFIG_M386. I think CONFIG_M686 is closer, but as I don't know the
significance of all the flags (MMX, TSC, etc), I'm not certain. Since the
flags do include fxsr, the correct answer may be CONFIG_M686FXSR.
Anyhow, here are my results:
[relson@osage relson]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping: 3
cpu MHz : 501.147
cache size : 512 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36
mmx fxsr xmm
bogomips: 999.42
[relson@osage relson]$ ARCH=i386 ; . cpu_detect.sh
GenuineIntel:6:7
CONFIG_M386
Also, here's a patch to make the script echo CONFIG_M686:
diff -urN cpu_detect.sh.orig cpu_detect.sh
--- cpu_detect.sh.orig Fri Dec 29 09:02:27 2000
+++ cpu_detect.sh Fri Dec 29 09:01:14 2000
@@ -18,7 +18,7 @@
case $cpu_id in
GenuineIntel:5:[0123] ) echo CONFIG_M586TSC ;;
GenuineIntel:5:[48]) echo CONFIG_M586MMX ;;
-GenuineIntel:6:[01356] ) echo CONFIG_M686 ;;
+GenuineIntel:6:[013567]) echo CONFIG_M686 ;;
GenuineIntel:6:{8,9,11}) echo CONFIG_M686FXSR ;;
AuthenticAMD:5:[0123] ) echo CONFIG_M586 ;;
AuthenticAMD:5:{8,9,10,11} ) echo CONFIG_MK6 ;;
David
P.S. I'm running 2.2.18, if it matters.
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
-
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: [PATCH] Processor autodetection (when configuring kernel)
Giacomo,
I don't think cpu_info.sh is quite right. It identified my 500 Mhz Pentium
III as CONFIG_M386. I think CONFIG_M686 is closer, but as I don't know the
significance of all the flags (MMX, TSC, etc), I'm not certain. Since the
flags do include fxsr, the correct answer may be CONFIG_M686FXSR.
Anyhow, here are my results:
[relson@osage relson]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping: 3
cpu MHz : 501.147
cache size : 512 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36
mmx fxsr xmm
bogomips: 999.42
[relson@osage relson]$ ARCH=i386 ; . cpu_detect.sh
GenuineIntel:6:7
CONFIG_M386
Also, here's a patch to make the script echo CONFIG_M686:
diff -urN cpu_detect.sh.orig cpu_detect.sh
--- cpu_detect.sh.orig Fri Dec 29 09:02:27 2000
+++ cpu_detect.sh Fri Dec 29 09:01:14 2000
@@ -18,7 +18,7 @@
case $cpu_id in
GenuineIntel:5:[0123] ) echo CONFIG_M586TSC ;;
GenuineIntel:5:[48]) echo CONFIG_M586MMX ;;
-GenuineIntel:6:[01356] ) echo CONFIG_M686 ;;
+GenuineIntel:6:[013567]) echo CONFIG_M686 ;;
GenuineIntel:6:{8,9,11}) echo CONFIG_M686FXSR ;;
AuthenticAMD:5:[0123] ) echo CONFIG_M586 ;;
AuthenticAMD:5:{8,9,10,11} ) echo CONFIG_MK6 ;;
David
P.S. I'm running 2.2.18, if it matters.
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
-
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: [PATCH] Processor autodetection (when configuring kernel)
Giacomo,
Further experimentation has revealed another problem with the script. The
use of curly braces in the case statement, i.e.
GenuineIntel:6:{8,9,11}) echo CONFIG_M686FXSR ;;
does not work. The construct below works, but I don't like it because of
its length:
GenuineIntel:6:8|GenuineIntel:6:9|GenuineIntel:6:11) echo
CONFIG_M686FXSR ;;
David
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
-
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/
test13p1 - NFS module problem
Greetings,
I just built test13-pre1 and have some unresolved nfs symbols.
Here's the relevant portion of .config:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
"make oldconfig dep bzImage modules" ran file.
"make modules_install" generated the following messages:
cd /lib/modules/2.4.0-test13p1; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.0-test13p1; fi
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13p1/kernel/fs/nfs/nfs.o
depmod: lockd_up_Rf6933c48
depmod: nlmclnt_proc_R4a4f5767
depmod: lockd_down_Ra7b91a7b
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13p1/kernel/fs/nfsd/nfsd.o
depmod: nlmsvc_ops_R9b9f6a7f
depmod: nlmsvc_invalidate_client_Rb1c3f825
depmod: lockd_up_Rf6933c48
depmod: lockd_down_Ra7b91a7b
Anybody know the fix for this?
Full .config available if necessary...
David
--------
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] 514 W. Keech Ave.
www.osagesoftware.com Ann Arbor, MI 48103
voice: 734.821.8800fax: 734.821.8800
-
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/
test13p1 - NFS module problem
Greetings,
I just built test13-pre1 and have some unresolved nfs symbols.
Here's the relevant portion of .config:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
"make oldconfig dep bzImage modules" ran file.
"make modules_install" generated the following messages:
cd /lib/modules/2.4.0-test13p1; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.0-test13p1; fi
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13p1/kernel/fs/nfs/nfs.o
depmod: lockd_up_Rf6933c48
depmod: nlmclnt_proc_R4a4f5767
depmod: lockd_down_Ra7b91a7b
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13p1/kernel/fs/nfsd/nfsd.o
depmod: nlmsvc_ops_R9b9f6a7f
depmod: nlmsvc_invalidate_client_Rb1c3f825
depmod: lockd_up_Rf6933c48
depmod: lockd_down_Ra7b91a7b
Anybody know the fix for this?
Full .config available if necessary...
David
--------
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] 514 W. Keech Ave.
www.osagesoftware.com Ann Arbor, MI 48103
voice: 734.821.8800fax: 734.821.8800
-
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: Pthreads, linux, gdb, oh my! (fwd)
Petr, It ran fine on my stock Mandrake 7.2 system - linux-2.2.17-21mdk and glibc-2.2-5mdk. The program ran fine in both environments - command line and gdb-5.0. Loadavg creeps up slowly as the program continues to run. At thread #37000, loadavb is 3.65. The ps command indicates 4 threads for the program (including gdb). David At 05:15 PM 12/8/00, Peter Berger wrote: >Petr, > >Thanks for testing this and finding a working counterexample! I am still >professionally interested to know if the difference is that you are >running a 2.4 kernel, or the glibc. Anyone running a 2.2 kernel with >glibc 2.2 want to drop me a line? > >-Peter -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: [Fwd: NTFS repair tools]
At 11:54 PM 12/7/00, Jeff V. Merkey wrote: >Linux today monitors this list. Some public education may be the best >route. How do we post a security advisory warning people that will get >posted? I'm sure folks see the DANGEROUS comments, but they don't seem >to stick in their heads. Then they get themselves into trouble, and >fortunately for them, I'm around. I am just concerned about the scope >of the black eye that will just keep getting bigger and bigger for Linux >NTFS. FWIW, Mandrake Linux includes a tool MandrakeUpdate which allows downloading of "Normal Updates" or "Development Updates". If you chose Devel Upd, you get the following warning: Caution ! These packages are NOT well tested. You really can screw up your system by installing them. Perhaps the configure tools could recognize a DANGEROUS status (or keyword or ???) and would display such a message ... David - 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: [Fwd: NTFS repair tools]
At 11:54 PM 12/7/00, Jeff V. Merkey wrote: Linux today monitors this list. Some public education may be the best route. How do we post a security advisory warning people that will get posted? I'm sure folks see the DANGEROUS comments, but they don't seem to stick in their heads. Then they get themselves into trouble, and fortunately for them, I'm around. I am just concerned about the scope of the black eye that will just keep getting bigger and bigger for Linux NTFS. FWIW, Mandrake Linux includes a tool MandrakeUpdate which allows downloading of "Normal Updates" or "Development Updates". If you chose Devel Upd, you get the following warning: Caution ! These packages are NOT well tested. You really can screw up your system by installing them. Perhaps the configure tools could recognize a DANGEROUS status (or keyword or ???) and would display such a message ... David - 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: Pthreads, linux, gdb, oh my! (fwd)
Petr, It ran fine on my stock Mandrake 7.2 system - linux-2.2.17-21mdk and glibc-2.2-5mdk. The program ran fine in both environments - command line and gdb-5.0. Loadavg creeps up slowly as the program continues to run. At thread #37000, loadavb is 3.65. The ps command indicates 4 threads for the program (including gdb). David At 05:15 PM 12/8/00, Peter Berger wrote: Petr, Thanks for testing this and finding a working counterexample! I am still professionally interested to know if the difference is that you are running a 2.4 kernel, or the glibc. Anyone running a 2.2 kernel with glibc 2.2 want to drop me a line? -Peter David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Advanced Linux Kernel/Enterprise Linux Kernel
At 11:41 AM 11/14/00, Richard B. Johnson wrote: >On Tue, 14 Nov 2000, Michael Rothwell wrote: > > > "Richard B. Johnson" wrote: > > > Multics??? [..] way too many persons on this list who know the > history of > > > Unix to try this BS. > > > > So, you're saying their nine goals were bullshit? Multics had a lot of > > problems. But it did a lot of ground-breaking. Perhaps you should reply > > to the nine goals, or the general topic of "Enterpriseness," rather than > > merely express your irrelevant hatred for Multics. > > > >Relating some "nine goals of 'Enterprise Computing'" to Multics is >the bullshit. When Multics was being developed, the singular goal >was to make an operating system that worked on DEC Equipment without >having to use DEC software. The emphasis was on trying to make it >work period. DEC? Try GE, specifically the GE-645 (if my memory hasn't lost any bits). Speaking of Multics, the last Multics system was just recently decomissioned. I think 35 years is a very impressive lifetime for a computer system. Linux, now at age 9, only has 26 years to go. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Advanced Linux Kernel/Enterprise Linux Kernel
At 11:20 AM 11/14/00, Mike Dresser wrote: >Michael Rothwell wrote: > > > Just some thoughts from 35 years ago. Please add your $0.02. > >What's that $0.02 worth after 35 years of inflation? > >=) I'd say inflation has been easily 12x since then. So $0.02 is now worth $0.25, i.e. the 2 cents of yesteryear is now 2 bits :-) -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Modprobe local root exploit
Daniel,
At 09:23 AM 11/14/00, you wrote:
I reserve the right to make coding errors, thanks for not letting it get
written into history :-)
I'm not going to give up my right to make errors until I'm ready to give up
my keyboard. I'll probably be pushing up daisies at that point in my life.
How about:
for ( ... ) if (!isalnum(*p) && !strchr("-_", *p)) return -EINVAL;
I think that is correct. However, it fails the "easy to understand"
criterion, so I don't like it.]
David
--------
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] 514 W. Keech Ave.
www.osagesoftware.com Ann Arbor, MI 48103
voice: 734.821.8800fax: 734.821.8800
-
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: Modprobe local root exploit
Daniel,
At 09:23 AM 11/14/00, you wrote:
I reserve the right to make coding errors, thanks for not letting it get
written into history :-)
I'm not going to give up my right to make errors until I'm ready to give up
my keyboard. I'll probably be pushing up daisies at that point in my life.
How about:
for ( ... ) if (!isalnum(*p) !strchr("-_", *p)) return -EINVAL;
I think that is correct. However, it fails the "easy to understand"
criterion, so I don't like it.]
David
--------
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] 514 W. Keech Ave.
www.osagesoftware.com Ann Arbor, MI 48103
voice: 734.821.8800fax: 734.821.8800
-
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: Advanced Linux Kernel/Enterprise Linux Kernel
At 11:20 AM 11/14/00, Mike Dresser wrote: Michael Rothwell wrote: Just some thoughts from 35 years ago. Please add your $0.02. What's that $0.02 worth after 35 years of inflation? =) I'd say inflation has been easily 12x since then. So $0.02 is now worth $0.25, i.e. the 2 cents of yesteryear is now 2 bits :-) David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Advanced Linux Kernel/Enterprise Linux Kernel
At 11:41 AM 11/14/00, Richard B. Johnson wrote: On Tue, 14 Nov 2000, Michael Rothwell wrote: "Richard B. Johnson" wrote: Multics??? [..] way too many persons on this list who know the history of Unix to try this BS. So, you're saying their nine goals were bullshit? Multics had a lot of problems. But it did a lot of ground-breaking. Perhaps you should reply to the nine goals, or the general topic of "Enterpriseness," rather than merely express your irrelevant hatred for Multics. Relating some "nine goals of 'Enterprise Computing'" to Multics is the bullshit. When Multics was being developed, the singular goal was to make an operating system that worked on DEC Equipment without having to use DEC software. The emphasis was on trying to make it work period. DEC? Try GE, specifically the GE-645 (if my memory hasn't lost any bits). Speaking of Multics, the last Multics system was just recently decomissioned. I think 35 years is a very impressive lifetime for a computer system. Linux, now at age 9, only has 26 years to go. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: anyone compiled 2.2.17 on RH7 successfully?
Corisen, RedHat 7.0's version of gcc, known as gcc 2.96, is incompatible with the kernel's code. Preprocessor changes cause the problem you encountered. It also has some defects in how it optimizes code that would cause the kernel to run incorrectly. The 7.0 distribution includes an older version of gcc, known as kgcc (for kernel gcc), that compiles code correctly and can be used for kernel compilation. Install the rpm and go for it! David At 08:44 PM 11/13/00, Corisen wrote: >has anyone running RedHat7(with kernel 2.2.16, gcc 2.96, kgcc 2.91.66) >complied 2.2.17 kernel successfully? > >i've downloaded the source and gunzip/untar to /root/linux-2.2.17 > >1. make menuconfig (ok) >2. make dep (ok) >3. make zImage >===> lots of warning message >===> error: checksum.S:231 badly punctuated parameter list in #define >===> error: checksum.S:237 badly punctuated parameter list in #define > >4. make CC=kgcc zImage >===> snapshot of errors reported: >In file included from init/main.c:15: >/usr/i386-glibc21-linux/include/linux/proc_fs.h:283: parse error before >`mode_t' >/usr/i386-glibc21-linux/include/linux/proc_fs.h:283: warning: no semicolon >at end of struct or union >/usr/i386-glibc21-linux/include/linux/proc_fs.h:284: warning: data >definition has no type or storage class >/usr/i386-glibc21-linux/include/linux/proc_fs.h:285: parse error before >`uid' >/usr/i386-glibc21-linux/include/linux/proc_fs.h:285: warning: data >definition has no type or storage class >/usr/i386-glibc21-linux/include/linux/proc_fs.h:286: parse error before >`gid' >/usr/i386-glibc21-linux/include/linux/proc_fs.h:286: warning: data >definition has no type or storage class >many more errors >many more errors > > >5. changed CC= kgcc in Makefile and execute "make zImage" >===> same error as 3 (strange, seems like the the compilation is still by >gcc and not kgcc despite the change) > >i was able to compile 2.4.0-test10 kernel image with "make CC=kgcc bzImage" > >pls kindly advise on the possible solutions. > >thanks. > > > > > >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: anyone compiled 2.2.17 on RH7 successfully?
Corisen, RedHat 7.0's version of gcc, known as gcc 2.96, is incompatible with the kernel's code. Preprocessor changes cause the problem you encountered. It also has some defects in how it optimizes code that would cause the kernel to run incorrectly. The 7.0 distribution includes an older version of gcc, known as kgcc (for kernel gcc), that compiles code correctly and can be used for kernel compilation. Install the rpm and go for it! David At 08:44 PM 11/13/00, Corisen wrote: has anyone running RedHat7(with kernel 2.2.16, gcc 2.96, kgcc 2.91.66) complied 2.2.17 kernel successfully? i've downloaded the source and gunzip/untar to /root/linux-2.2.17 1. make menuconfig (ok) 2. make dep (ok) 3. make zImage === lots of warning message === error: checksum.S:231 badly punctuated parameter list in #define === error: checksum.S:237 badly punctuated parameter list in #define 4. make CC=kgcc zImage === snapshot of errors reported: In file included from init/main.c:15: /usr/i386-glibc21-linux/include/linux/proc_fs.h:283: parse error before `mode_t' /usr/i386-glibc21-linux/include/linux/proc_fs.h:283: warning: no semicolon at end of struct or union /usr/i386-glibc21-linux/include/linux/proc_fs.h:284: warning: data definition has no type or storage class /usr/i386-glibc21-linux/include/linux/proc_fs.h:285: parse error before `uid' /usr/i386-glibc21-linux/include/linux/proc_fs.h:285: warning: data definition has no type or storage class /usr/i386-glibc21-linux/include/linux/proc_fs.h:286: parse error before `gid' /usr/i386-glibc21-linux/include/linux/proc_fs.h:286: warning: data definition has no type or storage class many more errors many more errors 5. changed CC= kgcc in Makefile and execute "make zImage" === same error as 3 (strange, seems like the the compilation is still by gcc and not kgcc despite the change) i was able to compile 2.4.0-test10 kernel image with "make CC=kgcc bzImage" pls kindly advise on the possible solutions. thanks. - 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/ -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Installing kernel 2.4
It seems to me that kernel/cpu matching can be broken into two relatively simple parts. 1 - Put a cpu "signature" in the kernel image indicating cpu requirements; and 2 - Have the bootloader (lilo) detect cpu type and match it against the cpu "signature". The bootloader would then load the kernel, or could give an informative diagnostic. David At 06:59 PM 11/7/00, Jeff Garzik wrote: >Sven Koch wrote: > > > > On Tue, 7 Nov 2000, David Lang wrote: > > > > > depending on what CPU you have the kernel (and compiler) can use > different > > > commands/opmizations/etc, if you want to do this on boot you have two > > > options. > > > > Wouldn't it be possible to compile the parts of the kernel needed to > > uncompress and to detect the cpu with lower optimizations and then abort > > with an error message? > > > > "Error: Kernel needs a PIII" sounds much better than just stoping dead. > >I agree... maybe we can solve this simply by giving the CPU detection >module the -march=i386 flag hardcoded, or editing the bootstrap, or >something like that... > > Jeff David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Installing kernel 2.4
It seems to me that kernel/cpu matching can be broken into two relatively simple parts. 1 - Put a cpu "signature" in the kernel image indicating cpu requirements; and 2 - Have the bootloader (lilo) detect cpu type and match it against the cpu "signature". The bootloader would then load the kernel, or could give an informative diagnostic. David At 06:59 PM 11/7/00, Jeff Garzik wrote: Sven Koch wrote: On Tue, 7 Nov 2000, David Lang wrote: depending on what CPU you have the kernel (and compiler) can use different commands/opmizations/etc, if you want to do this on boot you have two options. Wouldn't it be possible to compile the parts of the kernel needed to uncompress and to detect the cpu with lower optimizations and then abort with an error message? "Error: Kernel needs a PIII" sounds much better than just stoping dead. I agree... maybe we can solve this simply by giving the CPU detection module the -march=i386 flag hardcoded, or editing the bootstrap, or something like that... Jeff -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
At 05:44 AM 10/23/00, Horst von Brand wrote: >David Relson <[EMAIL PROTECTED]> said: > >Not just a preprocessor change. >... >This is true for a correct compiler (ever seen a correct piece of >software?) compiling strictly standard-conforming source. The kernel is >_not_ standard-conforming, and many places are writen just like they are to >trick the compiler into generating particular code, some places assume that >undefined behaviour (i.e., a[i] = b[i++] and such) works in a certain way, >that the compiler pads structures in a certain way, ... >... >Yes. The existing program is wrong in that it woprked by chance, not >because it was written right. Horst, What you say is correct. Early comments on gcc-2.96 reflected preprocessor changes which made it impossible to compile a kernel. Later comments, particularly David Wragg's "struct itimerval" example, show that compiler optimizations is broken. My recollection is that the behavior of "a[i] = b[i++]" is well defined, i.e. in the standard. However it's been years since I paid attention to those details, so I may be wrong. Anyhow, as we all know, gcc-2.96 is not ready for prime time. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
At 05:44 AM 10/23/00, Horst von Brand wrote: David Relson [EMAIL PROTECTED] said: Not just a preprocessor change. ... This is true for a correct compiler (ever seen a correct piece of software?) compiling strictly standard-conforming source. The kernel is _not_ standard-conforming, and many places are writen just like they are to trick the compiler into generating particular code, some places assume that undefined behaviour (i.e., a[i] = b[i++] and such) works in a certain way, that the compiler pads structures in a certain way, ... ... Yes. The existing program is wrong in that it woprked by chance, not because it was written right. Horst, What you say is correct. Early comments on gcc-2.96 reflected preprocessor changes which made it impossible to compile a kernel. Later comments, particularly David Wragg's "struct itimerval" example, show that compiler optimizations is broken. My recollection is that the behavior of "a[i] = b[i++]" is well defined, i.e. in the standard. However it's been years since I paid attention to those details, so I may be wrong. Anyhow, as we all know, gcc-2.96 is not ready for prime time. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
At 09:14 PM 10/22/00, Horst von Brand wrote: >Jurgen Kramer <[EMAIL PROTECTED]> said: > > > You can blame it on the compiler which is included with RH7.0. It's a > > pre-release version of some sort. It seems that the gcc people are not > > happy that RH included this version with RH7. > >It is the *kernel's* fault, as far as can be ascertained now. The compiler >is stricter, and implements new optimizations, for which the kernel (being >only ever compiled with gcc) is just unprepared. The problem, as I understand it, is that gcc-2.96 handles language constructs slightly different than older compilers. This is a preprocessor change, not an optimization problem. To say "new optimizations ... kernel ... unprepared" is incorrect. Having worked with compilers (some years ago), I always took it as an article of faith that the same answer(s) would be generated whether optimization was turned on or not. Optimization should always be a way to do a task either quicker (fewer instructions executing, less executing time, etc) or shorter (less memory needed for the instructions). Optimization should never, never give a different result. Having new optimizations break an executing program is simply wrong. David >-- >Horst von Brand [EMAIL PROTECTED] >Casilla 9G, Vin~a del Mar, Chile +56 32 672616 ---- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
Hamid, RedHat includes two versions of gcc. gcc-2.96 is a developmental snapshot of the compiler project and is not able to build a kernel. Also included is kgcc, as in KernelGCC, which is what you should be using. If you don't have the kgcc...rpm installed, install that and use it. David At 04:54 PM 10/22/00, Hamid Hashemi Golpayegani wrote: >Hi , > >I have download kernel-2.2.17 from kernel.org and wanna to compile it under >redhat 7 . when compiling start after few minutes show me this error message >: > >make[2]: Entering directory `/usr/src/linux/arch/arch/i386/lib' >gcc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -D__ASSEMBLY__ -D__SMP__ -t >raditional -c checksum.S -o checksum.o >checksum.S:231: badly punctuated parameter list in #define >checksum.S:237: badly punctuated parameter list in #define >make[2]: *** [checksum.o] Error 1 >make[2]: Leaving directory `/usr/src/linux/arch/i386/lib' >make[1]: *** [first_rule] Error 2 >make[1]: Leaving directory `/usr/src/linux/arch/i386/lib' >make: *** [_dir_arch/i386/lib] Error 2 > >I have install this kernel with same setting on RedHat 6.2 without any >problem ! >Any idea ? > >Thank You >Hamid Hashemi > >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
Hamid, RedHat includes two versions of gcc. gcc-2.96 is a developmental snapshot of the compiler project and is not able to build a kernel. Also included is kgcc, as in KernelGCC, which is what you should be using. If you don't have the kgcc...rpm installed, install that and use it. David At 04:54 PM 10/22/00, Hamid Hashemi Golpayegani wrote: Hi , I have download kernel-2.2.17 from kernel.org and wanna to compile it under redhat 7 . when compiling start after few minutes show me this error message : make[2]: Entering directory `/usr/src/linux/arch/arch/i386/lib' gcc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -D__ASSEMBLY__ -D__SMP__ -t raditional -c checksum.S -o checksum.o checksum.S:231: badly punctuated parameter list in #define checksum.S:237: badly punctuated parameter list in #define make[2]: *** [checksum.o] Error 1 make[2]: Leaving directory `/usr/src/linux/arch/i386/lib' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/linux/arch/i386/lib' make: *** [_dir_arch/i386/lib] Error 2 I have install this kernel with same setting on RedHat 6.2 without any problem ! Any idea ? Thank You Hamid Hashemi - 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/ -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Kernel 2.2.17 with RedHat 7 Problem !
At 09:14 PM 10/22/00, Horst von Brand wrote: Jurgen Kramer [EMAIL PROTECTED] said: You can blame it on the compiler which is included with RH7.0. It's a pre-release version of some sort. It seems that the gcc people are not happy that RH included this version with RH7. It is the *kernel's* fault, as far as can be ascertained now. The compiler is stricter, and implements new optimizations, for which the kernel (being only ever compiled with gcc) is just unprepared. The problem, as I understand it, is that gcc-2.96 handles language constructs slightly different than older compilers. This is a preprocessor change, not an optimization problem. To say "new optimizations ... kernel ... unprepared" is incorrect. Having worked with compilers (some years ago), I always took it as an article of faith that the same answer(s) would be generated whether optimization was turned on or not. Optimization should always be a way to do a task either quicker (fewer instructions executing, less executing time, etc) or shorter (less memory needed for the instructions). Optimization should never, never give a different result. Having new optimizations break an executing program is simply wrong. David -- Horst von Brand [EMAIL PROTECTED] Casilla 9G, Vin~a del Mar, Chile +56 32 672616 -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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 - isdn hisax - compilation error
At 12:56 PM 10/17/00, you wrote: >Greetings, > >I have compiled a 2.4.0 kernel for the first time, specifically >2.4.0-test9. Looking through the output for errors, I found >"config.c:311: #error "HiSax: No cards configured". Checking further, it >appears that isdn is being compiled, even though CONFIG_ISDN isn't >set. See below for the relevant parts of .config and "make modules" output. > >David Good morning! It's a new day and I have done some additional poking and prodding with this problem and have two things to report. First, the error happened during "make dep". Second, a second attempt at "make dep bzImage modules" was successful. Conclusion, I probably did something weird though I don't know what. If I can reproduce the problem, I'll report that. For now, don't worry about it. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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 - isdn hisax - compilation error
At 12:56 PM 10/17/00, you wrote: Greetings, I have compiled a 2.4.0 kernel for the first time, specifically 2.4.0-test9. Looking through the output for errors, I found "config.c:311: #error "HiSax: No cards configured". Checking further, it appears that isdn is being compiled, even though CONFIG_ISDN isn't set. See below for the relevant parts of .config and "make modules" output. David Good morning! It's a new day and I have done some additional poking and prodding with this problem and have two things to report. First, the error happened during "make dep". Second, a second attempt at "make dep bzImage modules" was successful. Conclusion, I probably did something weird though I don't know what. If I can reproduce the problem, I'll report that. For now, don't worry about it. David ---- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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/
2.4.0 - isdn hisax - compilation error
Greetings, I have compiled a 2.4.0 kernel for the first time, specifically 2.4.0-test9. Looking through the output for errors, I found "config.c:311: #error "HiSax: No cards configured". Checking further, it appears that isdn is being compiled, even though CONFIG_ISDN isn't set. See below for the relevant parts of .config and "make modules" output. David # # ISDN subsystem # # CONFIG_ISDN is not set make[4]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn' /usr/src/linux/scripts/mkdep isdn_audio.c isdn_audio.h isdn_bsdcomp.c isdn_cards.c isdn_cards.h isdn_common.c isdn_common.h isdn_concap.c isdn_concap.h isdn_net.c isdn_net.h isdn_ppp.c isdn_ppp.h isdn_tty.c isdn_ttyfax.c isdn_ttyfax.h isdn_tty.h isdn_v110.c isdn_v110.h isdn_x25iface.c isdn_x25iface.h > .depend make _sfdep_icn _sfdep_pcbit _sfdep_hisax _sfdep_avmb1 _sfdep_act2000 _sfdep_eicon _sfdep_divert _sfdep_hysdn _FASTDEP_ALL_SUB_DIRS="icn pcbit hisax avmb1 act2000 eicon divert hysdn" make[5]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn' make -C icn fastdep make[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/icn' /usr/src/linux/scripts/mkdep icn.c icn.h > .depend make[6]: Leaving directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/icn' make -C pcbit fastdep nmake[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/pcbit' /usr/src/linux/scripts/mkdep callbacks.c callbacks.h capi.c capi.h drv.c edss1.c edss1.h layer2.c layer2.h module.c pcbit.h > .depend make[6]: Leaving directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/pcbit' make -C hisax fastdep make[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/hisax' gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-strict-aliasing -E -D__GENKSYMS__ config.c | /sbin/genksyms -k 2.4.0 > /usr/src/linux/include/linux/modules/config.ver.tmp config.c:311: #error "HiSax: No cards configured" - 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/
2.4.0 - isdn hisax - compilation error
Greetings, I have compiled a 2.4.0 kernel for the first time, specifically 2.4.0-test9. Looking through the output for errors, I found "config.c:311: #error "HiSax: No cards configured". Checking further, it appears that isdn is being compiled, even though CONFIG_ISDN isn't set. See below for the relevant parts of .config and "make modules" output. David # # ISDN subsystem # # CONFIG_ISDN is not set make[4]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn' /usr/src/linux/scripts/mkdep isdn_audio.c isdn_audio.h isdn_bsdcomp.c isdn_cards.c isdn_cards.h isdn_common.c isdn_common.h isdn_concap.c isdn_concap.h isdn_net.c isdn_net.h isdn_ppp.c isdn_ppp.h isdn_tty.c isdn_ttyfax.c isdn_ttyfax.h isdn_tty.h isdn_v110.c isdn_v110.h isdn_x25iface.c isdn_x25iface.h .depend make _sfdep_icn _sfdep_pcbit _sfdep_hisax _sfdep_avmb1 _sfdep_act2000 _sfdep_eicon _sfdep_divert _sfdep_hysdn _FASTDEP_ALL_SUB_DIRS="icn pcbit hisax avmb1 act2000 eicon divert hysdn" make[5]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn' make -C icn fastdep make[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/icn' /usr/src/linux/scripts/mkdep icn.c icn.h .depend make[6]: Leaving directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/icn' make -C pcbit fastdep nmake[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/pcbit' /usr/src/linux/scripts/mkdep callbacks.c callbacks.h capi.c capi.h drv.c edss1.c edss1.h layer2.c layer2.h module.c pcbit.h .depend make[6]: Leaving directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/pcbit' make -C hisax fastdep make[6]: Entering directory `/usr/local/src/linux-2.4.0-test9/drivers/isdn/hisax' gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-strict-aliasing -E -D__GENKSYMS__ config.c | /sbin/genksyms -k 2.4.0 /usr/src/linux/include/linux/modules/config.ver.tmp config.c:311: #error "HiSax: No cards configured" - 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: Patch to remove undefined C code
At 01:21 PM 10/16/00, Jeff Garzik wrote: >Bernd Schmidt wrote: > > diff -x log.build -x .* -dru linux-2.4/drivers/net/tulip/tulip_core.c > linux-2.4-fixed/drivers/net/tulip/tulip_core.c > > --- linux-2.4/drivers/net/tulip/tulip_core.cMon Oct 16 13:51:23 2000 > > +++ linux-2.4-fixed/drivers/net/tulip/tulip_core.c Mon Oct 16 > 15:40:12 2000 >[...] > > @@ -944,9 +946,9 @@ > > > > /* Fill the final entry with our physical address. */ > > eaddrs = (u16 *)dev->dev_addr; > > - *setup_frm++ = *setup_frm++ = eaddrs[0]; > > - *setup_frm++ = *setup_frm++ = eaddrs[1]; > > - *setup_frm++ = *setup_frm++ = eaddrs[2]; > > + *setup_frm++ = eaddrs[0]; *setup_frm++ = eaddrs[0]; > > + *setup_frm++ = eaddrs[1]; *setup_frm++ = eaddrs[1]; > > + *setup_frm++ = eaddrs[2]; *setup_frm++ = eaddrs[2]; > > > > spin_lock_irqsave(>lock, flags); > > Looking at the above code, I noticed that there are a lot of ++ operations. I rewrote the code as: setup_from[0] = setup_from[1] = eaddrs[0]; setup_from[2] = setup_from[3] = eaddrs[1]; setup_from[4] = setup_from[5] = eaddrs[2]; setup_from += 6; I compiled using "gcc -S -Wall -O2 -fomit-frame-pointer -m486" to generate the assembler code. The old code is 17 instructions long and the new code is 11 instructions. As well as being shorter, simple timing test indicate that the new code is significantly quicker. David David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Patch to remove undefined C code
At 01:21 PM 10/16/00, Jeff Garzik wrote: Bernd Schmidt wrote: diff -x log.build -x .* -dru linux-2.4/drivers/net/tulip/tulip_core.c linux-2.4-fixed/drivers/net/tulip/tulip_core.c --- linux-2.4/drivers/net/tulip/tulip_core.cMon Oct 16 13:51:23 2000 +++ linux-2.4-fixed/drivers/net/tulip/tulip_core.c Mon Oct 16 15:40:12 2000 [...] @@ -944,9 +946,9 @@ /* Fill the final entry with our physical address. */ eaddrs = (u16 *)dev-dev_addr; - *setup_frm++ = *setup_frm++ = eaddrs[0]; - *setup_frm++ = *setup_frm++ = eaddrs[1]; - *setup_frm++ = *setup_frm++ = eaddrs[2]; + *setup_frm++ = eaddrs[0]; *setup_frm++ = eaddrs[0]; + *setup_frm++ = eaddrs[1]; *setup_frm++ = eaddrs[1]; + *setup_frm++ = eaddrs[2]; *setup_frm++ = eaddrs[2]; spin_lock_irqsave(tp-lock, flags); Looking at the above code, I noticed that there are a lot of ++ operations. I rewrote the code as: setup_from[0] = setup_from[1] = eaddrs[0]; setup_from[2] = setup_from[3] = eaddrs[1]; setup_from[4] = setup_from[5] = eaddrs[2]; setup_from += 6; I compiled using "gcc -S -Wall -O2 -fomit-frame-pointer -m486" to generate the assembler code. The old code is 17 instructions long and the new code is 11 instructions. As well as being shorter, simple timing test indicate that the new code is significantly quicker. David -------- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: problem with Compiling kernel sources.
Hiren, The gcc-2.96 released with RedHat 7.0 is a development snapshot of the compiler, not an offical gcc release. It has some changes which makes it impossible to build a kernel. RedHat 7.0 also includes a rpm with kgcc ( "Kernel GCC" ) which provides the compile you should use for this task. Over the past couple of weeks, there has been a lot of discussion on this mailing list of this topic. Check the archives for more of the gory details. Good luck! David At 06:17 PM 10/11/00, [EMAIL PROTECTED] wrote: >Hi All, > >Just 2 days back I bought RedHat Linux7. And I was trying to build >the kernel (make bzImage). But the build failed. It looks like >the compiler issue. But I am not sure and hence, I have posted this >on this list. > >Well, I tried one more thing. The RedHat Linux7 came with gcc package >gcc-2.96-54 And the build was failing with that. Then I >removed this package and installed egcs-1.1.2-30 package and tried >to build the kernel and I could build the kernel. If anybody has >faced the similar problem and could find the solution, please let >me know. > >Thanks and regards, >-hiren >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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: Upgrading a 2.2.14-5.0 kernel to 2.2.16-3 kernel
Alex, 'mkinitrd', which is in /sbin on my Mandrake 7.1 system can be used to create a new initrd. 'man mkinitrd' will tell you what you need to know about it. Don't forget that lilo allows you to define multiple boot configurations. An appropriate (second) entry in /etc/lilo.conf will set up your system so that you can choose to boot from your new 2.2.16 kernel or from your current 2.2.14 kernel. If the new kernel won't boot, you can still get to (and use) the old kernel. David At 01:56 AM 8/30/00, Alex Buell wrote: >I haven't been able to receive an answer from RedHat on this :o( > >We have a Dell PowerEdge server runninng RH 6.0 with the RH 2.2.14-5.0 >kernel. Now, I am aware there are some security issues with the 2.2.14 >kernel, however our Dell server requires the use of the third party >MegaTrends RAID driver which is loaded through initrd. > >Will upgrading the kernel to 2.2.16-3 affect the initrd image? Or will I >have to reinstall the initrd image with it? > >It's particularly important because if the MegaTrend driver isn't >correctly installed we will have a dead server! > >Cheers, >Alex. >-- >Bring on the music and lights! > > >http://www.tahallah.clara.co.uk > > >- >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/ David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] 514 W. Keech Ave. www.osagesoftware.com Ann Arbor, MI 48103 voice: 734.821.8800fax: 734.821.8800 - 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/
