Public bug reported:
Binary package hint: bind9
Bind9 uses per default (compiled from scratch)
/etc/named
/var/cache/named
/var/lib/named
/var/log/named
/var/run/named
/var/tmp/named
With ubuntu this is now:
/etc/bind
/var/cache/bind
/var/lib/bind
/var/log/named
/var/run/named
/var/tmp/bind
Could we please have this as expected by the binary: all in "named"
directories? It is quite a pitty to transfer named configurations across
systems if one doesn't stay in line, renaming parts inconsistently, just
because someone thought this could be a good idea!
Could we please stay at using "named" for all and everything "/usr/sbin/named"
is using??!
Same for all starting scripts: please use "/etc/default/named".
This was my first. Had to lower my angriness.
Second: /etc/apparmor.d/use.sbin.named (arrrrrggghhhhhhh --- if it had been
consequent: why "usr.sbin.named" here???) does hold wrong permissions. There
made for "named", but the directory created installing the package is called
"bind":
As found in /etc/apparmor.d/usr.sbin.named:
/var/tmp/named/** rw,
/var/tmp/named/ rw,
What it is configured for:
/var/tmp/bind/** rw,
/var/tmp/bind/ rw,
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bind9 1:9.7.1.dfsg.P2-2ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
Uname: Linux 2.6.35-24-generic-pae i686
Architecture: i386
Date: Wed Jan 5 10:54:49 2011
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386
(20101007)
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: bind9
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 maverick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
https://bugs.launchpad.net/bugs/697584
Title:
inconsistent and incompatible naming of bind files
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
