"Durk Strooisma" <[EMAIL PROTECTED]> writes:
>> However, one thing that we can do is have the init script exit with a 0
>> status if run when there's no module available.
>
> Exactly, just like the current check on file system level. It does an
> "exit 0" just like you said. There only needs to be
> I agree that this is a problem, but unfortunately there's no good way
> to fix it without creating other, more serious problems. dpkg and apt
> don't enforce installation order without Depends, but having
> openafs-client Depend on the module breaks anyone who builds the module
> themselves rath
Durk Strooisma <[EMAIL PROTECTED]> writes:
> Package: openafs-client
> Version: 1.4.7.dfsg1-2
> Severity: normal
>
> The OpenAFS Client is only started if the Linux openafs module exists.
> This check is not strong enough (see below). Besides checking for
> existence of the kernel module on file s
Package: openafs-client
Version: 1.4.7.dfsg1-2
Severity: normal
The OpenAFS Client is only started if the Linux openafs module exists.
This check is not strong enough (see below). Besides checking for existence
of the kernel module on file system level, the init.d script should check
whether the
4 matches
Mail list logo
