bind9 init script relies on unavailable capability kernel module

[Ben Howard]

The Bind9 init script contains:

 46
 47 modprobe capability >/dev/null 2>&1 || true
 48

The effect is that bind9 will not start on a Ubuntu 12.04 server.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-4ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-virtual 3.2.18
Uname: Linux 3.2.0-25-virtual x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Tue Jun 19 15:55:50 2012
Ec2AMI: ami-3a2e8d53
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.small
Ec2Kernel: aki-825ea7eb
Ec2Ramdisk: unavailable
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-4ubuntu0.1
 apparmor 2.7.102-0ubuntu3.1
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.bind.named.conf.default.zones: [modified]
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.zones.rfc1918: [modified]
modified.conffile..etc.init.d.bind9: [modified]
mtime.conffile..etc.bind.named.conf.default.zones: 2012-06-19T15:51:10.545839
mtime.conffile..etc.bind.named.conf.local: 2012-06-19T15:52:46.865843
mtime.conffile..etc.bind.zones.rfc1918: 2012-06-19T15:52:19.209839
mtime.conffile..etc.init.d.bind9: 2012-06-19T15:45:32.013841

[Ben Howard (darkmuggle-deactivatedaccount)]

Closing as invalid and a stupid error on my part.