Bug#426465: documentation does not describe the situation

2008-07-25 Thread Marco d'Itri
On Apr 10, Marco d'Itri <[EMAIL PROTECTED]> wrote: > This is not a bug, saying that "modprobe something" behaves differently > when called by acpid than when called by the command line is science > fiction. I suggest you try harder to diagnose the actual causes of the > issue you are experiencing.

Bug#426465: documentation does not describe the situation

2008-04-10 Thread Marco d'Itri
On Apr 09, martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Marco d'Itri <[EMAIL PROTECTED]> [2008.04.05.0137 +0200]: > > Should I close this bug? > Well, the bug still exists... This is not a bug, saying that "modprobe something" behaves differently when called by acpid than when called b

Bug#426465: documentation does not describe the situation

2008-04-10 Thread martin f krafft
also sprach Marco d'Itri <[EMAIL PROTECTED]> [2008.04.05.0137 +0200]: > Should I close this bug? Well, the bug still exists... -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://deb

Bug#426465: documentation does not describe the situation

2008-04-04 Thread Marco d'Itri
On Jul 09, martin f krafft <[EMAIL PROTECTED]> wrote: > > Did you find out what's wrong? > No, I did not. Should I close this bug? -- ciao, Marco signature.asc Description: Digital signature

Bug#426465: documentation does not describe the situation

2007-07-09 Thread martin f krafft
also sprach Marco d'Itri <[EMAIL PROTECTED]> [2007.07.08.2107 +0100]: > > On May 29, martin f krafft <[EMAIL PROTECTED]> wrote: > > > If I look at the modprobe.conf manpage's blacklist section, nothing > > > suggests any of the above behaviour. Could you please extend the > > > manpage to explain w

Bug#426465: documentation does not describe the situation

2007-07-08 Thread Marco d'Itri
On Jun 13, Marco d'Itri <[EMAIL PROTECTED]> wrote: > On May 29, martin f krafft <[EMAIL PROTECTED]> wrote: > > If I look at the modprobe.conf manpage's blacklist section, nothing > > suggests any of the above behaviour. Could you please extend the > > manpage to explain what's going on? > I don't

Bug#426465: documentation does not describe the situation

2007-06-13 Thread Marco d'Itri
On May 29, martin f krafft <[EMAIL PROTECTED]> wrote: > If I look at the modprobe.conf manpage's blacklist section, nothing > suggests any of the above behaviour. Could you please extend the > manpage to explain what's going on? I don't know, why don't you tell me? (Also see #426166.) -- ciao, M

Bug#426465: documentation does not describe the situation

2007-05-28 Thread martin f krafft
Package: module-init-tools Version: 3.3-pre11-1 Severity: minor I am trying to blacklist a module from udev while allowing the admin as well as acpid to modprobe it. Since udev does not have a blacklist facility but relies on module-init-tools, I proceeded to blacklist the module in /etc/modprobe.