Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I downloaded this file (right file?) to the /usr/src directory:
So, have you now decided to make your own kernel? A linux-image is the complete source code for the kernel. I really don't think this is what you want. Why didn't you run the command I asked you to run? Generally, we do not manually expand .deb files. If this is what you've been doing, then this is probably the root of your problem. In the normal case of things, unless you really know what you're doing, you install a deb file with the command "dpkg -i whatever.deb". But, the download and installation are both done by the aptitude program.
Please run this and forget about expanding debs yourself for now.
I was very happy to see them there. But the make command run from /madwifi blew up again with:
Makefile.inc:113: *** KERNELPATH: /usr/src/linux-2.6.15-26-386 does not exist. Stop.
My assumption is there is something the make process wants to get to the source kernel files and so I put a copy of them there so make could use what it needed. In other words, a complete stab in the dark. But hey I am in my experimental phase.
Nonetheless make wont run and I am getting a few gray hairs.
/me takes a short timeout to scream and pull out a couple handfulls of hair.
hmm, hmm, hmm. I'm kinda running out of steam, here. Something must have happened to your /lib/modules as a result of the other stuff you did. Let's try this, then. Run this and tell me where the build directory is pointing. It should be pointing at the linux-headers directory that matches uname -r.
ls -l /lib/modules/`uname -r`
Tell me where the source directory points, too.
Last edited by Quakeboy02; 02-15-2007 at 01:39 PM.
I want you to notice something in the first line that has a error message. Notice that the command looks correct. But the difference in icredibly small. Originally I had copied your command stright into the command line and BOOM it failed. I then replaced your - stroke with my keyboards - stroke and viola the command worked. They look the same but the machine does not interpret them equally.
It may be nothing but it may be why nothing installed correctly from the beginning. My keyboard is Spanish.
(Can I assume that the space in "2 8" is a typing mistake?)
In other words, the madwifi error is correct. It can't find what it thinks should be the correct source (i.e. that from uname -r) because your /lib/modules points to something else. If it were me, I'd just correct it by hand. I'm not quite sure what to tell you to do, though, because I'd hate for you to bork your installation completely by accident.
What to do? I think that an aptitude reinstall of the linux-header package *might* fix it. The thing is that I'm not sure if you have "linux-2.6.15-28-386" installed or "linux-2.6.15-26-386" or what. aptitude has a search feature. Could you use that to see what is actually installed at this point? It might be easier to use the synaptic package manager. I've started using that for loading and unloading packages. The "correct" thing to do depends on what is actually installed that's borking this.
"I then replaced your - stroke with my keyboards - stroke and viola the command worked. They look the same but the machine does not interpret them equally.
It may be nothing but it may be why nothing installed correctly from the beginning. My keyboard is Spanish."
Well, I'll be damned. Thanks for clearing that up. This has been a big mystery to me from the beginning.
I've got to go grocery shopping, so it'll be awhile till I can get back to this, as we've got a bit of a snow problem up here. But, I'm not deserting you.
---(Can I assume that the space in "2 8" is a typing mistake?)
Yes, this must be from a copy/paste error.
---If it were me, I'd just correct it by hand.
No problem. Lets try it. But how do I do it? If it all goes up in smoke, I dont mind. All part of my break-in with LINUX. Actually years ago I built an IP Tables firewall complete with FreeSwan and as I remember it was not as tough as this. But then again my command line Kung-Fu has waned due to overuse of a different OS.
---Could you use that to see what is actually installed at this point?
I did a search for Kernel on the file system and among other things found were these:
"No problem. Lets try it." Said the fly to the spider.
OK, "uname -r" tells you that your kernel is actually 2.6.15-28-386. If I'm understanding what you inadvertently posted above, you have both a 2.6.15-26-386 kernel and a 2.6-15-28-386 kernel. So, grub gives you a choice of two different multi-user kernels. Right? If not, let me know.
So, instead of banging on your /lib/modules, what you really need to do is install the proper linux-headers package. It still boils down to "sudo aptitude install linux-headers-`uname -r`", except that you have to use the proper "-" from your keyboard. Give that a try and see what happens. If necessary, just type in "sudo install linux-headers-2.6.15-28-386".
Wait a minute. Did you accidentally install a new kernel as part of trying to get the linux-headers installed? Is that where the problem lies?
Bah, I'm an surly, argumentative, curmudgeonly old bastard, and everyone knows it. But thanks.
Relax...relax. I have been put in charge of putting together a few demonstrations for my company. There a very few companies in Madrid in the security space. And there is an incredible need because 99% of companies using wireless are using WEP and even some have open access. You could own Madrid pretty easily.
So my boss has an idea to put together a pen-testing package for potential clients. Part of the dog and pony show would be showing them a few exploits to get thier attention. You know kind of like putting the fear of God in them. Karma is one exploit, and seeing it work made me want to yank every piece of wireless equipment we have deployed at client sites.
And on a personal level I needed a challenge. The other operating system was turning me into a click master and I knew if I wanted to get into security LINUX was the only way to go.
So dont worry. You have contributed to a worthy cause and for that, I thank you.