Package: iodine Version: 0.4.1-3 Severity: wishlist Tags: upstream DNS is a datagramme protocol, meaning that connections don't exist. Yet, an iodine process seems to be bound to one DNS server. If iodine would instead simply always use the resolver in /etc/resolv.conf, I could keep the process running for days and roam between networks.
Obviously, the server would need to support this similarly. I am not sure it's possible, I figure it's best to have the wishlist recorded... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1+scoflowctrl.1-686 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iodine depends on: ii adduser 3.107 add and remove users and groups ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy ii libc6 2.7-10 GNU C Library: Shared libraries ii makedev 2.3.1-87 creates device files in /dev ii udev 0.114-2 /dev/ and hotplug management daemo ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime iodine recommends no packages. -- debconf information excluded -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
