linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Toscano <pete@toscano.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: "Cold"-plugging my printer
Date: Wed, 07 Mar 2001 04:32:23 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98393957508053@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98385565702908@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]

I am _such_ an idiot.  When I downloaded the hotplug package, I got the
SRPM and rebuilt and intalled it.  Something must have gone wrong
somewhere because the hotplug script wasn't starting on boot anymore.  I
double-checked the SRPM, rebuild the package, reinstalled it and checked
the startup script and it's in there now...  I'm sure it was some of my
own special brain damage.

I'm very sorry for taking up your time.  Everything's working now.

/crawls back into his hole.

Thanks,
pete

On Tue, 06 Mar 2001, David Brownell wrote:

> So what did the "sh -x" invocation tell you about exactly why
> the USB agent did nothing when it contemplated loading
> "printer"?  We know the result is wrong.  We don't know why,
> but the answer is surely in that part of your "sh -x" output.
> 
> - Dave
> 
> 
> ----- Original Message ----- 
> From: "Pete Toscano" <pete@toscano.org>
> To: "David Brownell" <david-b@pacbell.net>
> Cc: <linux-hotplug-devel@lists.sourceforge.net>
> Sent: Tuesday, March 06, 2001 7:09 PM
> Subject: Re: "Cold"-plugging my printer
> 
> This is weird... (Not a good sign, eh? =)  I tried what you said.  I
> rebooted into single-user mode and ran "sh -x /etc/..."  Errrr, oops.  I
> just realized that I ran /etc/init.d/hotplug start (which, in turn, ran
> /etc/hotplug/usb.rc start).  After, when I ran lsof, I noticed that the
> printer module was indeed loaded.  Being a little surprised by this, I
> ran hotplug stop and then start and this time, a lot more debugging was
> printed out (all that USB setup info) and the printer module was not
> loaded.  I tried it again and the same thing happened.
> 
> pete
> 
> On Tue, 06 Mar 2001, David Brownell wrote:
> 
> > Or there could be something wrong in the boot-time init code, so that
> > a bit of shell script debugging is in order on your system.  Maybe you
> > can boot in single-user mode and "sh -x /etc/hotplug/usb.rc start" to
> > watch what it's doing wrong!  (Called by "/etc/rc.d/init.d/hotplug start",
> > as Greg suggested.)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-03-07  4:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06  5:14 "Cold"-plugging my printer Pete Toscano
2001-03-06  6:33 ` Greg KH
2001-03-06 16:03 ` David Brownell
2001-03-07  2:26 ` Pete Toscano
2001-03-07  3:09 ` Pete Toscano
2001-03-07  3:38 ` David Brownell
2001-03-07  4:32 ` Pete Toscano [this message]
2001-03-07  6:09 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-98393957508053@msgid-missing \
    --to=pete@toscano.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).