LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   "Too many levels of symbolic links" Problem (https://www.linuxquestions.org/questions/linux-newbie-8/too-many-levels-of-symbolic-links-problem-203884/)

Corallis 07-11-2004 08:27 PM

"Too many levels of symbolic links" Problem
 
Currently running Slackware 10.0, kernel 2.4.26. Im attempting to install module-init-tools-3.0.tar.gz via the method listed below:

cd /usr/src
wget -c http://www.kernel.org/pub/linux/kern...ols-3.0.tar.gz
tar -zxvf module-init-tools-3.0.tar.gz
cd module-init-tools-3.0
./configure --prefix=""
make moveold
make install
./generate-modprobe.conf /etc/modprobe.conf

As soon as I get to the "make install", I get the following errors:

make[1]: Entering directory '/usr/src/module-init-tools-3.0'
/bin/sh ./mkinstalldirs /bin
/bin/sh ./install-with-care lsmod /bin/lsmod
install: cannot stat '/bin/lsmod': Too many levels of symbolic links
make[1]: *** [install-binPROGRAMS] Error 1
make[1]: Leaving directory '/usr/src/modules-init-tools-3.0'
make: *** [install-am] Error 2

Im assuming this isnt supposed to be happening, so I was wondering if anyone could help me make sense of this. I have been looking on google but havent been able to find anything of much interest.

Thanks in advance if anyone can help.

Tuttle 07-11-2004 09:44 PM

sounds like you have a link pointing to a link ad-infinitum, ie. a link ultimately pointing back on itself somewhere maybe? try looking at some libs (.so files)

Corallis 07-11-2004 10:04 PM

Ah, I see. This does seem to be the problem. It seems my /bin/lsmod is a link that pionts to my /sbin/lsmod, and my /lsmod is a link that points to my /bin/lsmod. The problem seems a bit deeper than this too. In my /bin folder, I have an lsmod.old, which points to lsmod.old in my /sbin folder, which in turn points to insmod.old in my /sbin folder. This means I dont actually have an lsmod file? When I run lsmod from the command line, it says "-bash: lsmod: command not found". Is there some way I can fix this?

Boow 07-11-2004 10:56 PM

why would you need to install new moudule-init-tools anyways. the one that come with slack work fine even on 2.6.0 kernels. if it aint broke don't fix it lol.

Boow 07-11-2004 11:05 PM

rename the files back to their regular names. older versions of mod init tools would not load modules with the .ko extention but slacks are up to date ulnless you just want the latest greatest.

Tuttle 07-12-2004 01:18 PM

what he said ^


All times are GMT -5. The time now is 08:10 AM.