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.
note: the system is on hda1.. and is there any way to even exit this command as I'm pretty sure it will go on forever (and persists through a forced reboot!)
It has nothing much to do with the kernel compile, but a lot to do with the file system. Boot from e.g. a livecd and run fsck on all partitions - do not fsck mounted partitions.
Code:
man fsck
It persists because it's usually stderr telling you that the disk is corrupt.
the man command is not found. what does the man part do? ironically, I had just ran fsck on /dev/hda1 right before this error came up. although running it again now has brought up errors.
the man command is not found. what does the man part do?
The standard response to that is
Code:
man man
"man" should open a man (manual) page for the referenced program if it's not being found then there is probably something wrong with your user path. Try running man as root, if that doesn't work, then we may have a missing man...
Quote:
Originally Posted by sdfi
ironically, I had just ran fsck on /dev/hda1 right before this error came up. although running it again now has brought up errors.
edit: seems to be building ok now...
You should not fsck a mounted partition... it's better to boot from a livecd and do it from there. That may be the source of your trouble in fact...
I did do the original fsck from a livecd; i wasn't going to ignore the 'DOING THIS *WILL* F UP YOUR SYSTEM' warning
I was running 'man' as root, it is not there i suppose. Anyway, it all worked.
Follow up ? about kernel building; is it OK to build the kernel in future witout running the command;
Code:
make-kpkg --rootcmd fakeroot clean
My understanding is that this means every module is rebuilt (instead of just those that are changed?), which takes a *looooooooong* time (especially running on this machine which is old).
And also; how do i set the new kernel as default in grub, and remove others?
To make your compilation more fast try "make localmodconfig" (or perhaps not, it might end in a lot of fidding, like in doing it again and again until it works. For me it works).
You kernel should/could be set to default automatically.
Else edit /etc/default/grub -> GRUB_DEFAULT=0 and change 0 to whatever integer fits (run update-grub after you edited).
PS: if you can't use "man" something is seriously wrong.
Just like any other package, with apt-get/aptitude/synaptic/etc
ls /boot
and then, for example:
apt-get -s remove --purge linux-image-2.6.38-2-686
apt-get -s remove --purge linux-headers-2.6.38-2-686
and make sure its remove from /lib/modules.
AFAICT the guide is just the same as the one i linked except it uses a non-root user instead of using the fakeroot. (NB i only have root user currently)
The how-to you link to uses a kernel source from kernel.org, the other one uses a debianized kernel source from the start
(hence they differ).
If that is what you want it is fine, but to me the other how-to works and is more straight forward (especially the short version, which you will also find in the discussion of the how-to you linked to).
You use "make localmodconfig" at the very beginning. At forums.debian.net there is a thread about it, which explains how exactly
(without checking much i would say between "cp" and "make menuconfig"; make sure all devices you use are plugged)
I see. Well i have my kernel source already (FWIW; from voyage, as i'm using that, which explains the lack of man etc.. definitely going to put that in my profile now), so it was only from 'make-kpkg (--rootcmd fakeroot) clean' onwards that i was refering to. Will have a look into the localmodconfig more next time i rebuild (just done it now).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.