Thanks a lot Ondrej. I saw it run now:
root     15243     1  0 08:22 ?        00:00:00 /usr/sbin/knotd -c 
/etc/knot/knot.conf
But the running user is "root", does it have any risk? Thx.
On 2015/8/20 星期四 16:09, Ondřej Surý wrote:
 It's a bug in launchpad... Try
 apt-get install language-pack-en
 LC_ALL=en_US.UTF-8 add-apt-repository ppa:cz.nic-labs/knot-dns
 On August 20, 2015 9:59:25 AM GMT+02:00, Ken Peng <kpeng@runbox.com> wrote:
     Hello,
     I upgraded the system to ubuntu 14.04 x64. following the document
     again,but got:
     # add-apt-repository ppa:cz.nic-labs/knot-dns
        Knot DNS is a high-performance authoritative-only DNS server which
     supports all key features of the domain name system
including zone
     transfers, dynamic updates and DNSSEC.
        More info:https://launchpad.net/~cz.nic-labs/+archive/ubuntu/knot-dns
     Press [ENTER] to continue or ctrl-c to cancel adding it
     gpg: keyring `/tmp/tmpyqfouwgp/secring.gpg' created
     gpg: keyring `/tmp/tmpyqfouwgp/pubring.gpg' created
     gpg: requesting key F9C59A45 from hkp serverkeyserver.ubuntu.com  <http://keyserver.ubuntu.com>
     gpg: /tmp/tmpyqfouwgp/trustdb.gpg: trustdb created
     gpg: key F9C59A45: public key "Launchpad Datovhr" imported
     gpg: Total number processed: 1
     gpg:
        imported: 1  (RSA: 1)
     Exception in thread Thread-1:
     Traceback (most recent call last):
         File "/usr/lib/python3.4/threading.py  <http://threading.py>", line 920, in _bootstrap_inner
           self.run()
         File "/usr/lib/python3.4/threading.py  <http://threading.py>", line 868, in run
           self._target(*self._args, **self._kwargs)
         File
     "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py  <http://SoftwareProperties.py>",
     line 687, in addkey_func
           func(**kwargs)
         File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py  <http://ppa.py>", line
     370, in add_key
           return apsk.add_ppa_signing_key()
         File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py  <http://ppa.py>", line
     261, in add_ppa_signing_key
           tmp_export_keyring, signing_key_fingerprint, tmp_keyring_dir):
         File
     "/usr/lib/python3/dist-packages/softwareproperties/ppa.py  <http://ppa.py>", line
     210, in _verify_fingerprint
           got_fingerprints = self._get_fingerprints(keyring, keyring_dir)
         File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py  <http://ppa.py>", line
     202, in _get_fingerprints
           output = subprocess.check_output(cmd, universal_newlines=True)
         File "/usr/lib/python3.4/subprocess.py  <http://subprocess.py>", line 605, in check_output
           output, unused_err =
process.communicate(inputdata, timeout=timeout)
         File "/usr/lib/python3.4/subprocess.py  <http://subprocess.py>", line 936, in communicate
           stdout = _eintr_retry_call(self.stdout.read)
         File "/usr/lib/python3.4/subprocess.py  <http://subprocess.py>", line 487, in _eintr_retry_call
           return func(*args)
         File "/usr/lib/python3.4/encodings/ascii.py  <http://ascii.py>", line
     26, in decode
           return codecs.ascii_decode(input, self.errors)[0]
     UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 86:
     ordinal not in range(128)
     how to fix up this? Thanks.
     On 2015/8/20 星期四 15:49, Ondřej Surý wrote:
        Hi,
         I am sorry, but Debian 6.0 is not supported as we require more
         recent
         build tools and also many libraries are not recent enough or
         present in
         Debian LTS.
         You might be able to produce a static binaries on Debian Jessie
         and copy
         them to the old system, or prepare Debian Jessie chroot on your
         old system.
         However I would rather recommend upgrading the main system to recent
         Debian stable and move the stuff that require Debian 6.0 inside LXC
         container.
         Cheers, Ondřej
         On August 20, 2015 3:51:42 AM GMT+02:00, Ken Peng
         <kpeng@runbox.com> wrote:
         Hi,
         My system is debian 6.0 (yes I know it's out of date).
         When I installed knot from source following the document, I got
        
failed
         as below. How can I get continued? thanks.
         $ autoreconf -i -f
         libtoolize: putting auxiliary files in `.'.
         libtoolize: copying file `./ltmain.sh <http://ltmain.sh>
         <http://ltmain.sh>'
         libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
         libtoolize: copying file `m4/libtool.m4'
         libtoolize: copying file `m4/ltoptions.m4'
         libtoolize: copying file `m4/ltsugar.m4'
         libtoolize: copying file `m4/ltversion.m4'
         libtoolize: copying file `m4/lt~obsolete.m4'
         configure.ac:35: error: possibly undefined macro: AC_SUBST
         If this token and others are legitimate, please use
         m4_pattern_allow.
         See the Autoconf documentation.
         configure.ac:93: error: possibly undefined macro: AS_IF
         configure.ac:102: error: possibly undefined macro: AC_MSG_WARN
         configure.ac:122: error: possibly undefined macro: AC_DEFINE
         configure.ac:163: error: possibly undefined macro: AC_MSG_ERROR
         configure.ac:251: error: possibly undefined macro: AC_SEARCH_LIBS
         autoreconf: /usr/bin/autoconf failed with exit status: 1
         knot-dns-users mailing list
         knot-dns-users@lists.nic.cz
         https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
         --
         Sent from my Android device with K-9 Mail. Please excuse my brevity.
 --
 Sent from my
Android device with K-9 Mail. Please excuse my brevity.