This will be one of those posts I’d like to publish primarily to be able to coma back later and check it out instead of reading docs again
So, we have a server with two (or more) network interfaces are we need to be able to use more than one interface in our VDS machines. How do we set it up?
Read the rest of this entry →
Few days ago I’ve started migration of some of my non-critical servers to Debian Etch (from Sarge). Just after first apt-get update && apt-get dist-upgrade, when apt has been upgraded, I noticed really strange (as for me) error: when I’ve tried to do “apt-get update” it worked fine, but there was annoying message like following:
# apt-get update
Fetched 5562B in 13s (421B/s)
Reading package lists... Done
W: There are no public key available for the following key IDs:
W: You may want to run apt-get update to correct these problems
UPDATE: Thanks to Kurt Fitzner we know, that:
There is already a mechanism to do this automatically:
This will obtain the necesary keys and import them. No need to go through gpg directly.
After not so long research I figured out, that this problem was caused by change of gpg key used by ftpmaster on Debian official repository servers. Google gave me some information and I found some fix which works fine for me:
# gpg --keyserver wwwkeys.eu.pgp.net --recv-keys XXXXXXXXXXXXXXXX
# apt-key add /root/.gnupg/pubring.gpg
# apt-get update
Where XXXXXXXXXXXXXXXX is your missing key (e.g A70DAF536070D3A1).
That’s it! Happy using Debian GNU/Linux!
I really like Debian and Debian-based Linux distributions. That is because I am admin and I am lazy as all good system administrators With apt-get based distributions I can install/update/deinstall system packages very fast and my work becomes very efficient (there is no rpm-hell or constant building of new software or software updates).
Today I dugg very useful primer for apt-get/dpkg users. It contains many real-life examples of work with apt-get and dpkg utilities and may be interesting for new debian administrators.