% in crontab

if you would like to use construction like this `date '+%a'` in crontab, you need to backslash the % sign.

1 1 * * * touch /tmp/`date '+\%a'`.touch

It works in Linux but in Solaris does not. It creates file names where is a slash before a week name.

In Solaris the ' sign should not be used.

1 1 * * * touch /tmp/`date +\%a`.touch

W: GPG error: http://ppa.launchpad.net maverick Release: The following signatures couldn't be verified because the public key is not available:

After some paranoiac permission setting in my home folder I wanted to update repository and received error:

root@zzz:~# aptitude update

Hit http://ru.archive.ubuntu.com maverick-updates/multiverse amd64 Packages

Fetched 2,952B in 17s (167B/s)

W: GPG error: http://ppa.launchpad.net maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0EE1BF5F3C8E2A7F

kvm, failed to start network default in virsh

xxx@yyy:~$ virsh net-start default
error: Failed to start network default
error: internal error '/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 69 --jump ACCEPT' exited with non-zero status 1 and signal 0: iptables: Bad rule (does a matching rule exist in that chain?).

in messages:
Dec 27 23:15:39 yyy libvirtd: 23:15:39.512: warning : networkAddIptablesRules:850 : Could not add rule to fixup DHCP response checksums on network 'default'.
Dec 27 23:15:39 yyy libvirtd: 23:15:39.512: warning : networkAddIptablesRules:851 : May need to update iptables package & kernel to support CHECKSUM rule.

and there is no virbr0 interface.

Virtualization, KVM hypervisor

I started to explore KVM as full virtualization solution for Linux. The mail idea to sturdy different Oracle option on different platforms and emulate failure events to work out backup and recovery. Configuration and tuning is important part as well. So, I chosed KVM under KUbuntu 10.10. and started different installations. As I expected later there is a problem to communicate two virtual machines to each other. I asked google but didn't get definite answer. Accidentally I've found a solution lies in the plane of IP filters.