DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it normal to get errors when using 2.6?
I get /etc/network deprecated, also selinux error, I also get about 5 error's about devices already running EX alsa.
I have tried compiling the kernel about 20 times and the error's are still there.
Even when running debians kernel-image the same thing.
It shouldn't be this hard
Is it normal to get errors when using 2.6?
I get /etc/network deprecated, also selinux error, I also get about 5 error's about devices already running EX alsa.
I have tried compiling the kernel about 20 times and the error's are still there.
Even when running debians kernel-image the same thing.
It shouldn't be this hard
Actually, yeah... every kernel I've ever compiled has had a list of these. They're not errors, they're warnings. If they were errors, the make process would stop and not actually finish building your kernel. If you want to check to see if a process (such as make) terminated successfully, type "echo $?" at your bash prompt. By convention, this will produce a 0 if everything is okay and a non-zero value if something went wrong.
Usually, errors about deprecated usages and whatnot are harmless. A different way of doing things has been established and the deprecation is to point this out to people still using the old approach. Sometimes, though, source code is contributed and, because it works fine, isn't changed when something like this happens. So the code will still work, but the compiler will make a point of fussing about it just in case the code happens to be yours. This is my understanding of things, anyway.
Unless make refuses to build your kernel, you should be able to use it without worries. Anything that goes seriously wrong will most likely be reiterated to you at the end of the make's output, so you needn't go scrolling up looking for trouble.
I have no problem compiling the kernel it's on bootup after I install the new kernel I see all the error's. It double load's the sound and then i have a slash threw the volume icon in kde when booted. Tried compiling the kernel again without alsa support and it still double booted. But otherwise with the error's I still boot up and get into kde and use it.
Quote:
Originally Posted by tvynr
Actually, yeah... every kernel I've ever compiled has had a list of these. They're not errors, they're warnings. If they were errors, the make process would stop and not actually finish building your kernel. If you want to check to see if a process (such as make) terminated successfully, type "echo $?" at your bash prompt. By convention, this will produce a 0 if everything is okay and a non-zero value if something went wrong.
Usually, errors about deprecated usages and whatnot are harmless. A different way of doing things has been established and the deprecation is to point this out to people still using the old approach. Sometimes, though, source code is contributed and, because it works fine, isn't changed when something like this happens. So the code will still work, but the compiler will make a point of fussing about it just in case the code happens to be yours. This is my understanding of things, anyway.
Unless make refuses to build your kernel, you should be able to use it without worries. Anything that goes seriously wrong will most likely be reiterated to you at the end of the make's output, so you needn't go scrolling up looking for trouble.
I have no problem compiling the kernel it's on bootup after I install the new kernel I see all the error's. It double load's the sound and then i have a slash threw the volume icon in kde when booted. Tried compiling the kernel again without alsa support and it still double booted. But otherwise with the error's I still boot up and get into kde and use it.
If everything works fine, then don't worry about the errors. I have about 20 errors on my boot-up about PCIExpress and various other things, but that's because the driver are compiled into the kernel and I don't have a PCIExpress slot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.