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.
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.
I am installing my kernel and i got all the way up to the very last step but it give me and error. the step i mean is: /sbin/mkinitrd /boot/initrd-2.6.7.img 2.6.7
when i type that in it gives the error:
/boot/initrd-2.6.7.img/var/tmp is not a directory
and i tried some other things, and i may possibly have it up, but im afraid to shut down my computer for fear of not booting up again. What i did was. I manually deleted the symlink to my old initrd file (not a .img, something to do with gzip according to konquerer) and i made a new symlink to the initrd-2.6.7 (konquerer says gzip file) file and my /boot/grub/menu.lst file seems to be right if what i did is not wrong, but i really have no idea. can someone tell me if it will work, or if ive messed it up.
oh and also when i run the /sbin/mkinitrd alone i get this (may have some consequence to the help i recieve)
Root device: /dev/hda3 (mounted on / as reiserfs)
Module list: reiserfs
You may have selected the reiserfs as builtin instead of a module (make menuconfig -> File Systems -> Reiser FS ) while the /etc/sysconfig/kernel file contains INITRD_MODULES = "reiserfs". Either you remove reiserfs from the INITRD_MODULES variable or you set ReiserFS as a module <M> instead of being built-in <*>...
I just had the same problem stucking me for the last 2 hours ....
P.S. Yes it is safe to reboot since the old kernel will still be accessible, but trying to boot from the new one will certainly crash.... unless you solve that "reiserfs" problem
P.P.S. BTW, just "mkinitrd" alone will do ... unless you have dozen of kernels in /boot (and are concerned about time taken by mkinitrd), you don't need to specify the one for which you want to built the initrd