public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: Re: Debian Sid startup problems
Date: Sat, 12 Jun 2004 14:50:54 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406121445360.1825@debian-emach> (raw)
In-Reply-To: <5.1.0.14.1.20040612121108.01fc9a80@celine>

On Sat, 12 Jun 2004, Ray Olszewski wrote:

> in the kernel) called /proc/sys/kernel/hotplug . You might want to run
> /sbin/hotplug from the command line to see what its output is.

No output.  Doesn't generate any error report or anything.  Just returns
to the root command prompt (ran it as root, of course).  My inclination
would be to just stick with usbmgr, since it does seem to be working.
I'll undoubtedly need to remove hotplug from the system before doing any
dist-upgrades.

> installing  a kernel as (for example) "kernel-image-2.6-386" or as (for
> example) "kernel-image-2.6.5-1-386"? There isn't a "right" or wrong" answer
> to this ... both choices are reasonable ... but they cause upgrades to work
> differntly.

The former.  Looks like I'm in for another kernel upgrade if I do apt-get
dist-upgrade.

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-06-12 19:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 21:01 Debian Sid startup problems James Miller
2004-06-11 23:15 ` Ray Olszewski
2004-06-12  1:05   ` James Miller
2004-06-12  1:55     ` Ray Olszewski
2004-06-12  2:21       ` James Miller
2004-06-12  3:12         ` James Miller
2004-06-12  4:36           ` James Miller
2004-06-12  5:08             ` Ray Olszewski
2004-06-12 16:20               ` James Miller
2004-06-12 18:04                 ` chuck gelm
2004-06-12 18:10                   ` James Miller
2004-06-12 18:47                     ` James Miller
2004-06-12 18:32                 ` Ray Olszewski
2004-06-12 19:04                   ` James Miller
2004-06-12 19:27                     ` Ray Olszewski
2004-06-12 19:50                       ` James Miller [this message]
2004-06-12 22:36                         ` net (& module, I guess) problems after dist-upgrade James Miller
2004-06-13  3:57                           ` Ray Olszewski
2004-06-14 15:01                             ` James Miller
2004-06-14 16:35                               ` Ray Olszewski
2004-06-14 17:33                                 ` James Miller
2004-06-14 18:06                                   ` James Miller
2004-06-14 18:50                                     ` Ray Olszewski
2004-06-14 19:13                                       ` James Miller
2004-06-14 22:44                                         ` James Miller
2004-06-14 19:25                                       ` pa3gcu
2004-06-13  4:43                           ` joy
2004-06-12  1:36   ` Debian Sid startup problems James Miller
2004-06-12  2:07     ` Ray Olszewski

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=Pine.LNX.4.58.0406121445360.1825@debian-emach \
    --to=jamtat@mailsnare.net \
    --cc=linux-newbie@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