,--[ On Sunday 02 Dec 2007, Yashpal Nagar wrote:

[...]

| I boot the system with Ubuntu x86_64, Live CD, and mounted the root file
| system (/dev/cciss/c0d0p4) and found ld-linux-x86-64.so.2 was already
| present.
| # ls /mnt1/lib64/ld-*
| ld-2.3.3.so
| ld-linux-x86-64.so.2
| ld-lsb-x86-64.so.1

so, probably your libc.so.* was lost.

| Then i just copied all the /lib/* and /lib64/* from another system, Then
| i rebooted and found the above error

I think he asked you to copy only /lib{,64}/libc.so.*, not 
complete /lib{,64}/* . And it'll be better if you rsync-ed, so that symlinks 
will copied as symlinks.

[...]

| The issue is I still have two boxes with glibc-2.3.3 and glibc-2.6.1
| installed
|
| host3:/ # rpm -qa|grep -i glib
| glibc-i18ndata-2.3.3-98.61
| glibc-32bit-9-200512100800
| glibc-locale-32bit-9-200512100801
| glibc-2.6.1-18
| glibc-locale-2.3.3-98.61
| glib-32bit-9-200501041713
| glibc-info-2.3.3-98.61
| glibc-devel-2.3.3-98.61
| glibc-devel-32bit-9-200512100801
| glib-1.2.10-586.2
| glibc-2.3.3-98.61
| glib2-2.2.3-117.2
| glib2-32bit-9-200507121454
| glibc-2.4-31.2
|
| Could anyone help, to properly remove glibc-2.6.1 ?

I've no experience of SLES, but do they've some convention of naming 32-bit 
packages on amd64 architecture with '32bit' in their names, hmm... ? Paste 
the output of following command:

% rpm --qf '%{name}.%{arch}\n' -qa

You've three (or four) versions of glibc installed. And, BtW, what error do 
you get when you try to remove 'glibc-2.6.1' ?

|
| Thanks a lot for your patience :)
|
| Best regards,
| Yash

HTH
-- 
Ashish Shukla आशीष शुक्ल                      http://wahjava.wordpress.com/
·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --

_______________________________________________
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Next Event: http://freed.in - February 22/23, 2008
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/

Reply via email to