linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Strange udev problem
Date: Fri, 18 Jun 2004 17:51:35 +0000	[thread overview]
Message-ID: <20040618175135.GA14672@kroah.com> (raw)
In-Reply-To: <042401c45430$fd8c72e0$d100a8c0@W2RZ8L4S02>

On Fri, Jun 18, 2004 at 09:16:43AM -0700, Jim Gifford wrote:
> 
> ----- Original Message ----- 
> From: "Richard Troth" <rtroth@bmc.com>
> To: "Jim Gifford" <maillist@jg555.com>
> Cc: "HotPlug Developer List" <linux-hotplug-devel@lists.sourceforge.net>
> Sent: Thursday, June 17, 2004 8:03 AM
> Subject: Re: Strange udev problem
> 
> 
> > On Thu, 17 Jun 2004, Jim Gifford wrote:
> > > The SMP machine is a server and has multiple tasks runnning.
> >
> > Is your SMP machine running a database?   Maybe UDB?
> >
> > We do a lot with mainframe Linux,  which means we do a lot with
> > IBM products.   Something  (I *think* it was IBM's UDB,  but am
> > not certain)  kept changing the permission bits on /dev/null
> > every time one certain virtual Linux got rebooted.   I never
> > found out what because we have such a large flock of penguins.
> >
> > It could have been Websphere.   Heck,  maybe even Oracle.
> >
> > I attributed the problem to a bug in a start-up script.
> > If so,  it's completely unrelated to HotPlug.
> >
> > -- R;
> >
> Everything worked on my system under udev026, it's just with 027 this
> problem started. I have reverted back and changed the files, and everything
> works fine. At least it appears that way, I will have to wait and see.

There were only 2 changes between 026 and 027:
  <fork0:users.sf.net>:
   o fix handle leak in udev_lib.c

  Greg Kroah-Hartman:
    o tweak the gentoo default permission rules as they are wrong for
    tty and misc devices

I don't think that either of these changes caused anything to cause
device nodes to have their permissions changed, but if so, I would be
very interested in it.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-06-18 17:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  6:04 Strange udev problem Jim Gifford
2004-06-17 11:37 ` Kay Sievers
2004-06-17 12:45 ` Jim Gifford
2004-06-17 13:31 ` Jim Gifford
2004-06-17 15:01 ` Kay Sievers
2004-06-17 15:03 ` Richard Troth
2004-06-18  0:23 ` Jim Gifford
2004-06-18 16:16 ` Jim Gifford
2004-06-18 17:51 ` Greg KH [this message]
2004-06-18 18:24 ` Jim Gifford
2004-06-19  4:40 ` Jim Gifford
2004-06-19 16:31 ` Jim Gifford
2004-06-20  0:34 ` Jim Gifford

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=20040618175135.GA14672@kroah.com \
    --to=greg@kroah.com \
    --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).