i had an unstable libc6 and i couldnt downgrade it.
so i went ahead and removed it using dpkg ignoring dependencies. what i didnt know is that i cant execute any commands to install the stable libc6.(i blame all those people who do not reply to my posts)
since the system is still up, including this browser i need to figure out how im gonna install it back. from what i read i can boot into rescue (ok which rescue? will debian net install cd work?) and using dpkg chroot (will change root into this partition here that i will mount prior to that).
whats your suggestion? how would you do it?
walk me through it if you can. please, i had this system configured nicely (up for several months) i dont want to reinstall and start over.
keep in mind i have only one shot at this. the system must be prepared prior to restart, or otherwise its gone forever. i have only one shot at this.
as you read this right now, i am sitting there and waiting for someone's reply.

Why don't you just "apt-get install libc6" ?

dude no offense... read above. i cant execute any commands right now.
BitX:~# apt-get
bash: /usr/bin/apt-get: No such file or directory
BitX:~# dpkg
bash: /usr/bin/dpkg: No such file or directory
BitX:~# ls
bash: /bin/ls: No such file or directory
BitX:~#

fair enough. i can browse using nautilus since its still in the memory. the binaries are there but command interpretation no longer works becase libc6 is missing.

ANYONE ELSE?

If you have knoppix, you could chroot into your hard drive install and then use apt-get.

yeah thats sorta what i thought. ok gonna look around a little more and will restart and try it. shutting down will be fun (cant execute term and kill commands).

ok im in knoppix... chroot does not work. dpkg does not work. apt-get does not work. fun. since i have already rebooted the system will not boot without libc... i am totally f*cked.
i will not reinstall. if the system cannot be recovered, it will be the last time i am using linux. i have been working hard configuring this system, which was nearly ruined by an unstable libc6, now its trashed.
please help if you can.

That pretty much guaranteed that many more people will skip your posts, but I have caffeine beside me and the world is good...
chroot does work - can you please post what you typed and what it responded with?
No need for that - just stop looking to lay blame and look for as much info as possible to give the people here...

basically the operating system/command interpretation (including knoppix) does not see files. i can browse them, but i cannot execute commands with them.

root@ttyp0[knoppix]# chroot /mnt/hda1
chroot: cannot run command `/bin/bash': No such file or direct

if i do this:

root@ttyp0[knoppix]# cd /mnt/hda1/bin
root@ttyp0[bin]# ls bash
bash

yep, its there

or

root@ttyp0[bin]# cd /bin
root@ttyp0[bin]# ls bash
bash

its there too...

i can do this:

root@ttyp0[bin]# cd /mnt/hda1/bin
root@ttyp0[bin]# bash
root@ttyp0[bin]#

ok so it ran just fine without complaining about missing.

so basically NOTHING is seen on my system unless called on directly.

dpkg cannot run the scripts inside the packages since it does not see them.

i tried booting the system i get a kernel panic because it cannot find chroot. chroot is there:

root@ttyp0[sbin]# cd /mnt/hda1/usr/sbin
root@ttyp0[sbin]# ls chroot
chroot

basically i need to make the system see the files, then i can repair packages. until i can run anything i cant go any further.

what really disturbs me is that i see like 20 views on my posts but 0 replies. sorry if i am being offensive. after starting 10 threads over a period of time with 0 result becomes quite frustrating. normally i make my posts quite long with detailed information... unfortinately often with no result either.
please, i really need any help i can get resolving this.

Well for starters that isn't going to run your Debian bash install, it's going to run the Knoppix one. Try this...
In regards to your problem, this is what you get when you install unstable software and don't know how to fix it. Unstable/testing/devel repositories in distros are designed for people to play with and report bugs to the developers when something breaks. While plenty of people run then on their daily desktops that isn't the idea behind them and you shouldn't be doing that unless you know how to fix stuff when it does decide to crap itself.

my bad

here it works:

root@ttyp0[sbin]# cd /mnt/hda1/bin
root@ttyp0[bin]# ./bash
root@ttyp0[bin]#

but i still cant chroot. dpkg does not see the pre/post install scripts.

i added a testing repository because i had to get one package which was not avaliable in stable release. i forgot to remove the testing repository and accedentally updated libc6 and couldnt go back to stable version.
if all packages were avaliable in stable release i would never be using any testing packages. does that answer the question?

I just wanted to point out that you seem to have received replies to all but 1 of your threads you have started in the past. Notice that how much help you get is directly related to how polite/humble you are? We do not get paid to solve your problems, try using a little respect when asking for our free help.

PS:
the answer to your question has been answered on one of your many threads that you have started with the same questions. I will let you figure out which one.

regards,
...drkstr

that is incorrect. how competent of a user/developer can you be if you cant even count?
the search function on this forum is broken just so you know. it doesnt show half of my posts. but you couldnt count even the number of unanswered posts that is actually reported by the search engine.
ouch man... go kill yourself.
this is one of those posts that plainly wastes my time. go waste peoples time elsewhere. go read tax law or something. i dont need to take this discussion any further so i have no use for your reply. if you would like to make a statement regarding your competence, go find a nice brick wall and talk to it.

As a result of your poor attitude, this whole thread is a waste of every ones time. Remember, it wasn't the people here that messed up your computer, it was YOU who did.

Feel free to post again later when you don't feel like acting childish.

Closed.