Recover peerguardian how to#

But I'm more than happy to be your 'guinea pig' on any other reasonable strategy you can make me understand how to recover from, if all goes south. deb from the long-prior posting, or that I get the debian libc to satisfy the dependency? (I'm much less comfortable shoving a debian update into Ubuntu, since I'm not quite savvy enough to fix this solid OS if I manage to break it with something unorthodox.)įor the time being, since I seem to need to 'break a rule' to satisfy the libc dependency, I'll go back to that moblock. Given this situation, would you recommend that I install the moblock. Attempts to install moblock from the repository still complain at me about the apparent shortcomings of my libc, as I'm not using debian per se. debs that had been posted here and installed your new libn*. I fully uninstalled moblock and the libn* components from the. Having said that, I should mention that I'm using Ubuntu Dapper, and I've heard enough stories about Edgy to give me pause to go beyond this level right now. or does apt-get do that nowdays?) so that you have a clean ubuntu base to start with.I'm totally game for trying this out. If you have added any debian repo (as someone suggested) you need to uninstall moblock 'sudo aptitude remove moblock-nfq' (aptitude to remove dependancies too. It works for me, but i can't be sure until some of you tried it out. To get around that, i chose to build libnfnetlink and libnetfilter-queue for ubuntu. The problem with moblock, is that it's relying on som new libraries in the debian repos.

Recover peerguardian