All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: new release of udev?
Date: Thu, 19 May 2005 07:55:48 +0000	[thread overview]
Message-ID: <20050519075548.GA26138@kroah.com> (raw)
In-Reply-To: <20050519065848.GA25640@kroah.com>

On Thu, May 19, 2005 at 09:30:27AM +0200, Kay Sievers wrote:
> On Wed, 2005-05-18 at 23:58 -0700, Greg KH wrote:
> > Ok, now that the next kernel release is going to require people to
> > update udev, I want to make a new release.  I know the two of you have
> > been talking a lot about if the 057 release was good enough to package
> > up due to the dev.d change.
> > 
> > Did you come to any conclusions?
> 
> It wasn't continued. I'm on the way starting a big next roud of work on
> the udev package. Basically moving a lot of the SUSE version upstream.
> The SUSE package has a lot of nice features, like netlink instead of
> udevsend and initramfs-event-replay... All that can be compile options
> in the upstream package.

That's great, but I think I need to get a release out before then, due
to the kernel issue I created :)

> There is a small hole in the rules concept:
> If a custom rule want's to set custom permissions, but the system has a
> SUBSYSTEM-only rule to set default permissions, the user supplied perms
> are overridden. To prevent that, the rule can use "last_rule", but that
> prevents later RUN-rules to be executed.
> 
> That behavior was that way since the beginning, not a change in 057.
> Only the use of the RUN key is a bit difficult then. To solve that, I
> will implement deferred(question mark) assignment, like in Makefiles for
> the default system-supplied rules to use:
>   SUBSYSTEM="block", GROUP?="disk"
> 
> will only set the permissions if no other rule has already set the
> group. This should solve that small issue.

Ah, ok, thanks for the explaination.  And thanks for the proposed fix.

> > For now, we are still processing the dev.d tree by default, right?
> 
> Yes, nothing has changed in that area.

Good, it shouldn't be that tough of an upgrade then.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id\x16344&op=click
_______________________________________________
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:[~2005-05-19  7:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:58 new release of udev? Greg KH
2005-05-19  7:30 ` Kay Sievers
2005-05-19  7:55 ` Greg KH [this message]
2005-05-19 10:32 ` Marco d'Itri
2005-05-19 14:12 ` Kay Sievers
2005-05-19 16:09 ` Marco d'Itri
2005-05-19 17:49 ` Darren Salt
2005-05-19 21:02 ` Greg KH
2005-05-19 21:24 ` Darren Salt
2005-05-19 22:31 ` Kay Sievers
2005-05-22  0:59 ` Marco d'Itri
2005-05-22  1:09 ` Kay Sievers
2005-05-22 12:01 ` Marco d'Itri
2005-05-22 12:42 ` Kay Sievers
2005-05-22 12:55 ` Marco d'Itri
2005-05-22 13:00 ` Kay Sievers
2005-05-22 13:07 ` Marco d'Itri
2005-05-22 17:38 ` Kay Sievers
2005-05-23  6:52 ` Hannes Reinecke
2005-05-23  7:34 ` Marco d'Itri
2005-05-23  9:43 ` Marco d'Itri
2005-06-20 18:10 ` Marco d'Itri
2005-06-20 20:40 ` Kay Sievers

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=20050519075548.GA26138@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.