Summary: | =sys-fs/udev-146 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew Schultz <mattsch> |
Component: | New packages | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | eugene.shalygin, polynomial-c |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.kernel.org/pub/linux/utils/kernel/hotplug/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 270859 | ||
Attachments: |
udev-146.ebuild
udev-146.ebuild udev-posttrigger.initd udev-146.ebuild udev-postmount.patch udev-146.patch |
Description
Matthew Schultz
2009-09-01 13:52:03 UTC
Created attachment 202974 [details]
udev-146.ebuild
I had to update the md5 of 50-udev-default.rules since upstream fixed a comment with a spelling error on line 81. Other than that, everything is the same as 145. It compiles and is running on x86.
Created attachment 203217 [details]
udev-146.ebuild
Merges changes from udev 145-r1.
Created attachment 203247 [details]
udev-posttrigger.initd
Init script for default runlevel to initialize modules that weren't initialized on the initial udev trigger.
Created attachment 203248 [details]
udev-146.ebuild
Added udev posttrigger init script to ebuild.
Yeah, I also wanted to add some code to udev-postmount running "udevadm trigger --type=failed". So is there a reason to add another script and not add that to udev-postmount? And please, next time add a patch against the latest udev ebuild instead of a copy, as so one can easily get the differences and not get confused as the ebuild in tree gets changed. (In reply to comment #5) > Yeah, I also wanted to add some code to udev-postmount running "udevadm trigger > --type=failed". > So is there a reason to add another script and not add that to udev-postmount? > > And please, next time add a patch against the latest udev ebuild instead of a > copy, as so one can easily get the differences and not get confused as the > ebuild in tree gets changed. > Does udev-postmount have to run on the boot run level or can it run on the default run level? I ask this because trigger failed needs to run after dbus. Created attachment 203288 [details, diff]
udev-postmount.patch
Ok, looks like udev-postmount gets hotplugged and doesn't need to be in a runlevel. So here's a patch for that. A new script isn't needed then.
Created attachment 203290 [details, diff]
udev-146.patch
patches udev-145-r1 -> udev-146.
Bumped to udev-146, but the init-script changes are not yet done. (In reply to comment #9) > Bumped to udev-146, but the init-script changes are not yet done. These changes are now integrated in udev-146-r2/udev-147. |