Bug#387176: modprobe incorrectly used in init script

To: Trecourt Nicolas <fosco@fosconetwork.org>
Cc: 387176@bugs.debian.org
Subject: Bug#387176: modprobe incorrectly used in init script
From: Kenshi Muto <kmuto@debian.org>
Date: Fri, 15 Sep 2006 00:40:27 +0900
Message-id: <[🔎] 20060914154027.C82C21A7BA5@mail.topstudio.co.jp>
Reply-to: Kenshi Muto <kmuto@debian.org>, 387176@bugs.debian.org
In-reply-to: <[🔎] 20060912183939.14996.4082.reportbug@ATuin.frontier.fr>
References: <[🔎] 20060912183939.14996.4082.reportbug@ATuin.frontier.fr>

tags 387176 + pending
thanks

At Tue, 12 Sep 2006 20:39:39 +0200,
Trecourt Nicolas wrote:
> Package: cupsys
> Version: 1.2.2-2+b1
> Severity: normal
> Tags: patch
> 

> Maybe we should also check that modprobe is available (and executable?).

committed. I chose "-x" for modprobe checking.

Thanks,
-- 
Kenshi Muto
kmuto@debian.org

Reply to:

Follow-Ups:
- Processed: Re: Bug#387176: modprobe incorrectly used in init script
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

References:
- Bug#387176: modprobe incorrectly used in init script
  - From: Trecourt Nicolas <fosco@fosconetwork.org>

Prev by Date: Processed: Re: Bug#387176: modprobe incorrectly used in init script
Next by Date: Bug#386942: marked as done (cupsys-dbg: cups-driverd compiled incorrectly?)
Previous by thread: Bug#387176: modprobe incorrectly used in init script
Next by thread: Processed: Re: Bug#387176: modprobe incorrectly used in init script
Index(es):
- Date
- Thread