Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Yesterday, i started to install tightVNC on my system and it failed the make with error2 so i didn't finish with make install, i just halted the sysytem.
This morning, i could not boot this kernel 2.4.20.19.9 i started with sshd failed and boom: kernel panic. I had to start with an older kernel.
Is there a way to save this kernel... or am i getting to sentimental over it?
There's not a lot of info you've provided us, if you didn't ever do a make install with TightVNC, then none of the system files should have been changed. It's likely something else. Since you can boot an older kernel though, I'd just look into compiling a new one and be done with it.
But I'm curious as to what else you did, a:
./configure
make
Wouldn't affect system files unless something was wrong with the code (don't do those with root...).
If you are getting as far as sshd attempting to start, maybe it's just a problem with the initrd image.
Unless you are in the habit of looking at the Makefile and source code of your applications before 'making' them, you should do that portion as a non-priv'd user. Why? Because if something accidently made a typo:
rm -rf /usr
When they meant:
rm -rf . usr
in the Makefile, then you'll sadly be missing a /usr directory now. Whereas with a non-priv'd user it would complain about permissions and error out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.