try to remove/comment out the LD_ASSUME_KERNEL thingy in the start scripts. I use a 2.6.18.2-kernel, both freenet versions (5 and 7) runs proper without this und both give me lib errors if LD_ASSUME_KERNEL is set...
Am Donnerstag, 4. Januar 2007 02:52 schrieb urza9814 at gmail.com: > So I had this exact same problem before, and I fixed it by using a > different linux distro (switch from slackware back to Mandriva 2006). > But now I'm on the distro that worked a year later (Mandriva 2007) and > it's no longer working. But I'm a bit smarter now, so I'm hoping I can > get it figured out. Anyways, I have freenet 0.5, jre 5.0, and I'm > getting the following error: > > [root at localhost fnet2]# sh start-freenet.sh > Detected freenet-ext.jar > Detected freenet.jar > Sun java detected. > head: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > sed: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > grep: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > grep: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > grep: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > Sun Java 1.4.2 detected. > uname: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > Starting Freenet now: Command line: java -Xmx128m freenet.node.Main > nice: error while loading shared libraries: libc.so.6: cannot open > shared object file: No such file or directory > Done > > I know, you shouldn't run freenet as root. That's step 2. lol > Anyways, the problem with the above error is that I have libc.so.6. > It's currently located in /lib, and is pointing to libc-2.4.so Should > I maybe link to it from somewhere else? Is it a problem with libc-2.4? > (I had 2.3.5 before). Any ideas? -- Mfg saces
