public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Greg KH" <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Trying to run 2.6.0-test3
Date: Sat, 16 Aug 2003 22:20:55 +0900	[thread overview]
Message-ID: <0ed701c363f9$47667790$1aee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20030815171636.GA3129@kroah.com

"Greg KH" <greg@kroah.com> replied to me:

> > 2.  When I attach a USB hard disk drive, 2.6.0 drivers log:
> > [...] no runnable /etc/hotplug/scsi_device.agent is installed
> > 2.4.19 didn't have this problem.  2.4.19 automatically updated
> > /etc/fstab.
>
> Try getting the latest update of the hotplug scripts from
> http://linux-hotplug.sf.net/ if you don't like seeing this in your log
> files.  It's a very harmless message.

Once I know that the message is harmless, I don't need to worry about it.
But it would be nice if 2.6.0 would automatically update /etc/fstab the way
2.4.19 did.  I assume that the new hotplug scripts will do that.

By the way, since we had some discussion of USB keyboards, I want to mention
that it is separate (so far) from the keyboard problems that I've reported
for 2.6.0-test1 through test3.  So far I've only tested 2.6.0 on machines
with PS/2 keyboards (or emulations thereof).  Considering the patch for
test1 which still hasn't made it into test3, maybe I ought to try connecting
a USB keyboard to one machine soon.  Meanwhile I don't dare to even try
2.6.0 on a machine which depends on its USB keyboard (no PS/2 ports and
cessation of BIOS emulation when the OS boots).


  reply	other threads:[~2003-08-16 13:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15  8:11 Trying to run 2.6.0-test3 Norman Diamond
2003-08-15  8:53 ` Felipe Alfaro Solana
2003-08-15 10:00   ` Norman Diamond
2003-08-15 11:53     ` Felipe Alfaro Solana
2003-08-15 13:20       ` Norman Diamond
2003-08-15 15:02         ` Felipe Alfaro Solana
2003-08-16 13:21           ` Norman Diamond
2003-08-15 10:14 ` Russell King
2003-08-15 12:39   ` Norman Diamond
2003-08-15 13:04     ` Mikael Pettersson
2003-08-17  1:51       ` Norman Diamond
2003-08-15 16:43     ` Joshua Kwan
2003-08-15 17:06       ` Randy.Dunlap
2003-08-15 17:15         ` Russell King
2003-08-15 17:16 ` Greg KH
2003-08-16 13:20   ` Norman Diamond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-17  7:59 Norman Diamond
2003-08-17 13:33 ` Russell King
2003-08-18 10:41   ` Norman Diamond
2003-08-18 11:21     ` Russell King
2003-08-17  9:57 Norman Diamond
2003-08-17 17:25 ` Alan Cox
2003-08-18 10:35   ` Norman Diamond
2003-08-18 11:00     ` Vojtech Pavlik
2003-08-23 12:29       ` Norman Diamond
2003-08-25 14:24         ` Vojtech Pavlik
2003-08-18 11:37 John Bradford

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='0ed701c363f9$47667790$1aee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=greg@kroah.com \
    --cc=linux-kernel@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