Re: HELP!!!! BAD ENTRY IN /etc/ld.so.preload CAUSING ERROR IN LINUX BOOT UP

From: Sukumar Thirunarayanan (sthiru68@hotmail.com)
Date: Sat Jun 03 2000 - 16:52:16 EST


The problem is even after I boot by
linux init=/sbin/sash

None of these commands like
rm
echo
vi
mv

When I try this command I get the same error (Error loading shared library).

are working since they all are not standalone program so I am not able to
modify/remove the file /etc/ld.so.preload.

----Original Message Follows----
From: "Khimenko Victor" <khim@sch57.msk.ru>
To: sthiru68@hotmail.com, root@chaos.analogic.com
CC: linux-kernel@vger.rutgers.edu
Subject: Re: HELP!!!! BAD ENTRY IN /etc/ld.so.preload CAUSING ERROR IN
LINUX BOOT UP
Date: Sat, 3 Jun 2000 01:43:50 +0400 (MSD)

In <20000602194130.17340.qmail@hotmail.com> Sukumar Thirunarayanan
(sthiru68@hotmail.com) wrote:
> I use a boot disk to boot linux, at boot prompt do I have to say "linux
> single" to boot in the single user mode?

Yes, but it'll not help you - see below :-)

> Does this mean it doesn't use the "init" program to boot in this mode?

It does so you can not use single mode to pull itself out of such situation.

> Another thing I noticed was after I created this file /etc/ld.so.preload
all
> the programs/command like vi rm cp etc was failing with the same error
> message what I got from "init" program, at that point I did a shutdown
and
> restarted it and it never came back up because the "init" program was
> failing.

> So even if I get it in the single user mode will I be able to use the
> "mount" and other utilities with out any problem.

> Can You also please show me the steps in what I have to do?

So you are total novice then ? Hmm. Try to enter
-- cut --
init=/sbin/sash
-- cut --
while using boot disk. It'll load /sbin/sash instead of /sbin/init .
There you can remove /etc/ls.so.preload with
-- cut --
# echo > /etc/ld.so.preload
-- cut --
trick (it's built-in command) and then you can do
-- cut --
sync
-- cut --
(to push changes to disk) and reboot system with reset button (it's possible
to do it more cleanly but since you rebooted system many times already
uncleanly it's better to force fsck anyway).

Hope it helps.

> Thank You

> ----Original Message Follows----
> From: "Richard B. Johnson" <root@chaos.analogic.com>
> Reply-To: root@chaos.analogic.com
> To: Sukumar Thirunarayanan <sthiru68@hotmail.com>
> CC: linux-kernel@vger.rutgers.edu
> Subject: Re: HELP!!!! BAD ENTRY IN /etc/ld.so.preload CAUSING ERROR IN
LINUX
> BOOT UP
> Date: Fri, 2 Jun 2000 15:16:58 -0400 (EDT)

> On Fri, 2 Jun 2000, Sukumar Thirunarayanan wrote:

>> I have a bad entry in /etc/ld.so.preload which is causing the init
>> program at start up to fail saying
>>
>> init: error in loading shared libraries
>> <bad entry>: cannot map file data: Operation not supported by device
>>
>> How can I fix this?
>>
>> Thank You
>>

> Just rename it out of the way if this is causing the problem.
> Boot in single-user mode, mount the root file-system, then
> execute ldconfig to clean up.

> Cheers,
> Dick Johnson

> Penguin : Linux version 2.3.41 on an i686 machine (800.63 BogoMips).

> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:17 EST