Bug#353501: nfs-kernel-server: /etc/exprots should not be a 'conffile'

2006-04-03 Thread Steinar H. Gunderson
On Mon, Apr 03, 2006 at 11:52:59AM -0700, Vagrant Cascadian (bugs) wrote: > in my experience, nfs server does not start if there are no exports. It does; this was fixed not too long ago. > also, it makes it difficult for packages (such as ltsp-server) to > configure NFS while remaining compliant

Bug#353501: nfs-kernel-server: /etc/exprots should not be a 'conffile'

2006-04-03 Thread Vagrant Cascadian (bugs)
> On Sat, Feb 18, 2006 at 06:18:30PM -0800, Vagrant Cascadian (bugs) > wrote: >> /etc/exports is marked as a conffile, but there is no sane default >> values to make it useful, so admins must modify /etc/exports >> appropriate to their network. > > Well, it is actually useful in an empty state; it

Bug#353501: nfs-kernel-server: /etc/exprots should not be a 'conffile'

2006-04-02 Thread Steinar H. Gunderson
On Sat, Feb 18, 2006 at 06:18:30PM -0800, Vagrant Cascadian (bugs) wrote: > /etc/exports is marked as a conffile, but there is no sane default > values to make it useful, so admins must modify /etc/exports > appropriate to their network. Well, it is actually useful in an empty state; it makes the

Bug#353501: nfs-kernel-server: /etc/exprots should not be a 'conffile'

2006-02-18 Thread Vagrant Cascadian (bugs)
Package: nfs-kernel-server Severity: normal /etc/exports is marked as a conffile, but there is no sane default values to make it useful, so admins must modify /etc/exports appropriate to their network. this seems to be in inappropriate use of a conffile, according to debian policy 10.7.3: 10.7.3