Re: compiling the kernel
I've written a Mini-HOWTO on compiling the kernel: http://www.eclectic-cheval.net/linux/kr-mhowto.txt I've posted it here for two reasons: 1) In case it will help, and 2) To get suggestions from those who know more than I do. It's licensed under the FDL, so hack away. Daniel. -- Bash forehead on any key to continue... t-shirts still available for $15 Free shipping within the continental U.S. Call (316) 204-1700 to order or email me for details Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
On Tue, 7 Jan 2003 12:01:34 -0700 Craig Cameron [EMAIL PROTECTED] wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. I am a newbie, so any help is appreciated. Normally it's 'make xconfig or make menuconfig for kernels. Sice you installed minimal, I'd think 'make menuconfig' would suffice. If you have the Redhat kernel-source rpm installed, and if you don't want to start from scratch, there's one already started in /usr/src/linux-version/configs for whatever architecture you're using. It can help a lot for getting started. Basically, you copy the appropriate one to the top level of the source tree, rename it as .config, 'make oldconfig' then run menuconfig. Such as (this is a Rawhide kernel that you likely won't have): cd /usr/src/linux-2.4.20-0.pp.20 cp configs/kernel-2.4.20-athlon.config ./.config make oldconfig make menuconfig Then you set whatever options you want, get rid of things, etc. Beats having to do it all from scratch (usually). Things are different if you are using the tarball however. -- Me? A skeptic? Can you prove it? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
I have nothing under /src/linux No files or directory's. I really think I need to add an RPM. Thanks. -Original Message- From: ABrady [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:25 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel On Tue, 7 Jan 2003 12:01:34 -0700 Craig Cameron [EMAIL PROTECTED] wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. I am a newbie, so any help is appreciated. Normally it's 'make xconfig or make menuconfig for kernels. Sice you installed minimal, I'd think 'make menuconfig' would suffice. If you have the Redhat kernel-source rpm installed, and if you don't want to start from scratch, there's one already started in /usr/src/linux-version/configs for whatever architecture you're using. It can help a lot for getting started. Basically, you copy the appropriate one to the top level of the source tree, rename it as .config, 'make oldconfig' then run menuconfig. Such as (this is a Rawhide kernel that you likely won't have): cd /usr/src/linux-2.4.20-0.pp.20 cp configs/kernel-2.4.20-athlon.config ./.config make oldconfig make menuconfig Then you set whatever options you want, get rid of things, etc. Beats having to do it all from scratch (usually). Things are different if you are using the tarball however. -- Me? A skeptic? Can you prove it? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Jan 2003 12:01:34 -0700, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. Where the heck did you run that command? ;) You must install the kernel-source i386.rpm and then go into /usr/src/linux-2.4 for kernel configuration and compilation. It's there where the command would work. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Gy/T0iMVcrivHFQRAh9FAJ9WhK2mg97QIJGDm5HbdGqNMjDkSQCcDw1X OJEQ01lsFVXi6n+WRysW4Y0= =0XVO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
Thanks. After installing about 6 other dependency modules, I finally got the kernel source installed. Now I can run make. Thanks again. -Original Message- From: Michael Schwendt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:52 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Jan 2003 12:01:34 -0700, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. Where the heck did you run that command? ;) You must install the kernel-source i386.rpm and then go into /usr/src/linux-2.4 for kernel configuration and compilation. It's there where the command would work. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Gy/T0iMVcrivHFQRAh9FAJ9WhK2mg97QIJGDm5HbdGqNMjDkSQCcDw1X OJEQ01lsFVXi6n+WRysW4Y0= =0XVO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
I did try make menuconfig, but had the same result. What is the RPM for Kernal hacking? -Original Message- From: Daniel Callahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:19 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel On Tuesday 07 January 2003 13:01, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. Make sure you're root (no offense -- I mention this because this is still on my Top 10 Dumb Error List), and try: make menuconfig (in a terminal) make xconfig (only in Xwindows) You will need the developer tools, but RH will add those if you install the Kernel Hacking option in setup. Hope that helps! -- Daniel Callahan CIO, Castle Computer Consultants, Inc. (316) 304-7212 Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
On Tuesday 07 January 2003 13:01, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. Make sure you're root (no offense -- I mention this because this is still on my Top 10 Dumb Error List), and try: make menuconfig (in a terminal) make xconfig (only in Xwindows) You will need the developer tools, but RH will add those if you install the Kernel Hacking option in setup. Hope that helps! -- Daniel Callahan CIO, Castle Computer Consultants, Inc. (316) 304-7212 Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Well, I took the path of least resistance and compiled a static kernel. Seems to work ok :) However, I'm still wondering why I'm having trouble building a modular kernel. mkinitrd cannot find the ncr583cxx module, but it doe exist in the appropriate folder. Any thoughts? At 09:05 PM 12/10/2002 +0100, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Dec 2002 11:06:51 -0800, Jeff Davis wrote: No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? It should be in /lib/modules/$KERNEL_VERSION/kernel/drivers/scsi and whether or not it is found might depend on how you call mkinitrd. The module-info file is not used by mkinitrd. /etc/modules.conf is. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99kkd0iMVcrivHFQRAqmAAJ4p3M+PmojHcU9jSZ9TuCwM/pd5RACbB64a NwUhMZqd2GhgihTDaayWE3w= =kUJO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 09 Dec 2002 08:50:32 -0800, Jeff Davis wrote: The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99an/0iMVcrivHFQRApZnAJ95G49m8P3aZyVgTFErL/qUve2r0wCdHfyH Y63axYK4TVgsRa/AqpGQhyE= =517z -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
At 09:46 AM 12/10/2002 +0100, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 09 Dec 2002 08:50:32 -0800, Jeff Davis wrote: *snip* So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? Thanks -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Davis wrote: | Huh. So, if I want or need to create a ramdisk image for the new | kernel, how do I get mkinitrd to quite whining about not being able to | find my ncr53c8xx module. The file (ncr53c8xx.o) is in the | /lib/modules/scsi directory. Or should *I* quite whining and build a | static kernel? The real question is do you need a modular kernel? Do you plan on ever switching the hardware out on this machine or will the configuration remain static for the duration of this kernel's use? If it's going to remain static, there's nothing wrong w/ a static kernel - - or at a minimum, making the SCSI module staticly compiled (leaving the rest modular). Building a modular kernel that works right is a challenge, especially on non-standard hardware. - -Rick - -- Rick Johnson, RHCE - [EMAIL PROTECTED] (from home) Linux/WAN Administrator - Medata, Inc. PGP Key: https://mail.medata.com/pgp/rjohnson.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE99j0HIgQdhlSHZgMRAid6AKD+OaBNtALIH4V16jypDyYTM1YjFQCffUGt cRLzq8R4Vk47X6S3BUiafl4= =1stT -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Dec 2002 11:06:51 -0800, Jeff Davis wrote: No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? It should be in /lib/modules/$KERNEL_VERSION/kernel/drivers/scsi and whether or not it is found might depend on how you call mkinitrd. The module-info file is not used by mkinitrd. /etc/modules.conf is. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99kkd0iMVcrivHFQRAqmAAJ4p3M+PmojHcU9jSZ9TuCwM/pd5RACbB64a NwUhMZqd2GhgihTDaayWE3w= =kUJO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Why are you doing a make clean after the make dep? Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? -David Jeff Davis wrote: Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
At 05:01 PM 12/9/2002 -0600, you wrote: Why are you doing a make clean after the make dep? It's been a while since I've customized a kernel... According to the howto they recommended doing a make clean after make dep. Perhaps this was an old howto? Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? SCSI driver needs one to boot, as I understand it. I could be misinformed... -David Jeff Davis wrote: Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Jeff Davis wrote: At 05:01 PM 12/9/2002 -0600, you wrote: Why are you doing a make clean after the make dep? It's been a while since I've customized a kernel... According to the howto they recommended doing a make clean after make dep. Perhaps this was an old howto? Perhaps. The README in the src root dir is where the instructions that I use are. Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? SCSI driver needs one to boot, as I understand it. I could be misinformed... Hmm. What SCSI driver? I included a lot of SCSI stuff in my kernel even though I don't use 80% of it, and I never need one. Perhaps you could experiment with it once you get everything running and let us know. I'd be very interested to hear more on this. -David -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Cant connect to HTTPS after re-compiling the kernel
Hello, Do you know how come i cant connect to HTTPS sites after re-compiling my kernel to 2.4.19 and i un-installed ipchains... rpm -q ipchains Casue im going to use iptables?But i have not put in any rules. It was working before i re-compiled the kernel? Any ideas what could cause this? Im usuing Mozilla 1.1 Browser i also tryed it with netscape and still cant connect to websites HTTPS... RedHat 7.3 2.4.19 Kernel Kernel 2.4.18 is the kernel that it works with? Any ideeas __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 -- redhat-list mailing list unsubscribe mailto:redhat-list-request;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Cant connect to HTTPS after re-compiling the kernel
Hey, Do you know how come i cant connect to HTTPS sites after re-compiling my kernel to 2.4.19 and i un-installed ipchains...casue im going to use iptables? It was working before i re-compiled the kernel? Any ideas what could cause this? Im usuing Mozilla 1.1 Browser i also tryed it with netscape and still cant connect to websites... RedHat 7.3 2.4.19 Kernel __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 -- redhat-list mailing list unsubscribe mailto:redhat-list-request;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re-Compiling the kernel.
Hello all. I'm in the process of re-compiling the kernel, but I get to a point where there's an error. These are the steps up to the error: # cd /usr/src/linux-2.4.18-3 # make config (CONFIG_PCMCIA = no to achieve a kernel without PCMCIA support) # make dep # make clean # make bzImage # make modules # make modules_install ( this is where the error appears) ln: when making multiple links, last argument must be a directory make: *** [_modinst_] Error 1 # I read the man pages and it suggests that the directory it should make_install is /lib/modules/2.4.*/ My new kernel will be called 2.4.18-3no-pcmcia-cs so I tried: # make modules_install /lib/modules/2.4.18-3no-pcmcia-cs/ but the same error occurs. Please can you advise me where I'm going wrong. Thanks, Trevor. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re-Compiling the kernel.
Hello all. I'm in the process of re-compiling the kernel, but I get to a point where there's an error. These are the steps up to the error: # cd /usr/src/linux-2.4.18-3 # make config (CONFIG_PCMCIA = no to achieve a kernel without PCMCIA support) # make dep # make clean # make bzImage # make modules # make modules_install ( this is where the error appears) ln: when making multiple links, last argument must be a directory make: *** [_modinst_] Error 1 # I read the man pages and it suggests that the directory it should make_install is /lib/modules/2.4.*/ My new kernel will be called 2.4.18-3no-pcmcia-cs so I tried: # make modules_install /lib/modules/2.4.18-3no-pcmcia-cs/ but the same error occurs. Please can you advise me where I'm going wrong. Thanks, Trevor. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: compiling the kernel to recognize ntfs
So..., I recompile the kernel with NTFS suport, and copy to /boot, I modify grub.conf in /boot/grub to select the kernel to boot, but when select the kernel with NTFS suport the system freezing when the red hat 7.3 is begin to load..., then I have to rebooting the machine and select the kernel unmodifing to enter, but without NTFS suport, what is wrong with this procedure? --- Ricardo Mostalac [EMAIL PROTECTED] escribió: Hello friends, I want to recompile my kernel to recognize ntfs (in the kernel or as a module), but, anyone can tell me his experience doing this? My kernel is 2.4.18-3 and my red hat is 7.3 = Saludos desde México RAML _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list = Saludos desde México RAML _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEp5i79BpdPKTBGtEQJBIACffb+E72TCQ0Ctz0y/G9qwHNT8FHgAn1hw TULK1VDeHV8L9HlrCHKaMZ3N =oZAX -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
I'm currently using X-CD-Roast...but I'll look at some others at some point, too. On 19 Jan 2002, Brandon Robert Dorman wrote: I compiled most everything I'll need into the kernel. cdburner, visor, usb printer/scanner stuff, etc. but for next time, thanks for the info Bret, Mike and Werner. -Brandon p.s. this doesn't have to be a list question, but what do you guys recommend for a cd-burning software? Now that I have scsi support in there I'll actually be able to do it under linux... (that was the reason i recompiled.) On Sat, 2002-01-19 at 22:34, Mike Burger wrote: That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Simply put, I don't know. G On Sun, 20 Jan 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEp5i79BpdPKTBGtEQJBIACffb+E72TCQ0Ctz0y/G9qwHNT8FHgAn1hw TULK1VDeHV8L9HlrCHKaMZ3N =oZAX -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
On Sun, 20 Jan 2002, Mike Burger wrote: Simply put, I don't know. G On Sun, 20 Jan 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? if you look closely, you'll notice that red hat 7.2 gives you the option of building ext3 filesystems at install time, but the supplied kernel does not contain ext3 functionality -- the ext3 module is in fact in the initrd.img file shipped by red hat. rday ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 rpjday wrote: Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? if you look closely, you'll notice that red hat 7.2 gives you the option of building ext3 filesystems at install time, but the supplied kernel does not contain ext3 functionality -- the ext3 module is in fact in the initrd.img file shipped by red hat. Sure ... like I said, for a portable kernel, it makes sense. - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEqYE79BpdPKTBGtEQLFIQCgvyJXNXNcLAtjuSdeWTpo6XkTIDMAoNhi 1mhEaW/5TWtMQNTt52lVy3D2 =KlMI -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Check out man mkinitrd. seems like I have always just given it the kernel version and the imgfile name needed. I guess the real question is do you really need an initrd? Unless you need something like scsi drivers that you compiled as modules that need to be availible before the file systems are availible you should not need one. If unsure, comment out the line in lilo that refers to it, run lilo again and reboot. Bret On Sat, at 22:50, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. -Brandon [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
I compiled most everything I'll need into the kernel. cdburner, visor, usb printer/scanner stuff, etc. but for next time, thanks for the info Bret, Mike and Werner. -Brandon p.s. this doesn't have to be a list question, but what do you guys recommend for a cd-burning software? Now that I have scsi support in there I'll actually be able to do it under linux... (that was the reason i recompiled.) On Sat, 2002-01-19 at 22:34, Mike Burger wrote: That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
Stuart Why don't try http://www.linuxdoc.org. In here, you can find a detail how-to document for compliling the linux kernel. Regards, Andrew So Hing-pong Hidong Kim wrote: http://www.freeos.com/articles/2589/2/1-3/ among many others found from a google search on "compiling the linux kernel". Good luck, Stuart Clark wrote: Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Regards Stu ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
-BEGIN PGP SIGNED MESSAGE- Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Actually, the kernel docs (which you get when you install the kernel-doc package) have everything you'll need. Have you looked there? - -d - -- David Talkington Prairienet [EMAIL PROTECTED] 217-244-1962 PGP key: http://www.prairienet.org/~dtalk/dt000823.asc -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBOsDPTL1ZYOtSwT+tAQE6HggAuLyqPUFJF+WPyet+WvWQXam8G+q8uVmR mZGk8tocpNs+pQT1olSUEPZBWU5rvF9ywAsIV+CLkwOi8TPOxIlNFU9fjDumJA+9 C/IjVI2CZMex+POos0sgPOet0FlhYb2hhT21geAd1t6WIl2OTrRCdX/vFMBRSoDe nBElxe/Fi7Qrqlz+sTDgCybn4f2ykdBWUHS2unqw4z7A6D5I+06YEtxumUR+VTL9 gfcJM5Zw9NdikeZfPyMJZxEDwgE10bNo9PlOq6vVsrZ8YXgk/1Y0T9hO1CGdoIaH eBZqx5qM94VBZQUwDPuAvxRzI4z/8JWZZivPjH2yfZFsnJim5HEiEQ== =PZre -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
http://www.freeos.com/articles/2589/2/1-3/ among many others found from a google search on "compiling the linux kernel". Good luck, Stuart Clark wrote: Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Regards Stu ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling the Kernel
Ok.. I downloaded the patches... This is going to sound dumb but how do I install them :DOk... I feel like a newbie again ::grinz:: BTW, I also tried compiling the latest egcs source (1.1.2 I think). I'm getting a signal 11 error after I think 70% + complete with the build (make bootstrap). No issues with the config. Looks good. I read the FAQ on signal 11 errors. Is there perhaps a list of software that I should have upgraded prior to compiling egcs? I realize that it could be hardware related (the FAQ suggested this). I'm going over everything to rule that out. Thx for the help! Frank www.xmission.com/~dmacleod Bernhard Rosenkraenzer wrote: On Fri, 11 Feb 2000, Frank Carreiro wrote: sbni.c:1375: Invalid `asm' statement: sbni.c:1375: fixed or forbidden register 1 (sx) was spilled for class DREG. You're trying to compile this kernel with gcc 2.95.x. Either get the gcc 2.95.x kernel patch (http://people.redhat.com/bero/gcc295/) or use egcs 1.1.x/gcc 2.7.x/gcc 2.8.x to compile this kernel. LLaP bero -- The first time Microsoft makes something that doesn't suck is when they start making vacuum cleaners. -- This is Linux Country. On a quiet night, you can hear Windows NT reboot. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
Re: Compiling the Kernel
On Fri, 11 Feb 2000, Frank Carreiro wrote: sbni.c:1375: Invalid `asm' statement: sbni.c:1375: fixed or forbidden register 1 (sx) was spilled for class DREG. You're trying to compile this kernel with gcc 2.95.x. Either get the gcc 2.95.x kernel patch (http://people.redhat.com/bero/gcc295/) or use egcs 1.1.x/gcc 2.7.x/gcc 2.8.x to compile this kernel. LLaP bero -- The first time Microsoft makes something that doesn't suck is when they start making vacuum cleaners. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
