[gentoo-dev] newsitem: udev-init-script changes (second draft)

[gentoo-dev] newsitem: udev-init-script changes (second draft)

[William Hubbs]

[-- Attachment #1.1: Type: text/plain, Size: 138 bytes --]

All,

here is the second version of this news item; there are more changes I
think I should mention, so they are in this draft.

William


[-- Attachment #1.2: 2015-06-01-udev-init-scripts-changes.en.txt --]
[-- Type: text/plain, Size: 852 bytes --]

Title: udev-init-scripts-28 important changes
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2015-06-01
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <=sys-fs/udev-init-scripts-28

In udev-init-scripts-28 and newer, the udev service script has been
split into udev, udev-settle and udev-trigger.

This means the settings in /etc/conf.d/udev have also been migrated
to the appropriate /etc/conf.d files, so be careful when you update your
configuration settings.

It is also important that you add udev-trigger to the sysinit runlevel.
This is done by issuing the following command:

# rc-update add udev-trigger sysinit

Udev-settle should not be added to any runlevels since it should not be
needed most of the time. If another service needs it, this service
should add "need udev-settle" to its dependencies.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-dev] newsitem: udev-init-script changes (second draft)

[Alexis Ballier]

On Fri, 29 May 2015 14:50:31 -0500
William Hubbs <williamh@gentoo.org> wrote:
[...] 
> First, there is now a udev-trigger init script which you will need to
> add to the sysinit runlevel. You do this by issuing the following
> command:
> 
> # rc-update add udev-trigger sysinit

Unrelated to the news items, but is there any case when one would not
want to do this ?

[...]
> Display-If-Installed: <=sys-fs/udev-init-scripts-28
[...]
> The second change is that, from this point forward, the init scripts
> will not be automatically added to the sysinit runlevel.


This sounds like something that is of much higher importance when
*not* upgrading from older versions, yet this wont be displayed for new
installs it seems.

Re: [gentoo-dev] newsitem: udev-init-script changes (second draft)

[Anthony G. Basile]

On 05/29/15 15:50, William Hubbs wrote:
> All,
>
> here is the second version of this news item; there are more changes I
> think I should mention, so they are in this draft.
>
> William
>

sys-fs/udev-init-scripts-28 is not on the tree yet.  i'd like to test 
this with both eudev and with the embedded stages that i do.  can i use 
-9999 or will you put -28 on the tree before this news item goes out. 
while i think i get what you're up to, i'd like to see it first hand.


-- 
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197

Re: [gentoo-dev] newsitem: udev-init-script changes (second draft)

[William Hubbs]

[-- Attachment #1.1: Type: text/plain, Size: 116 bytes --]

All,

here is the latest version of this news item. It will be submitted on 5
Jun if there is no feedback.

William

[-- Attachment #1.2: 2015-06-05-udev-init-scripts-changes.en.txt --]
[-- Type: text/plain, Size: 722 bytes --]

Title: udev-init-scripts-28 important changes
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2015-06-05
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <=sys-fs/udev-init-scripts-28

In udev-init-scripts-28 and newer, the udev service script has been
split into udev, udev-settle and udev-trigger.

This means the settings in /etc/conf.d/udev have also been migrated
to the appropriate /etc/conf.d files, so be careful when you update your
configuration settings.

udev and udev-trigger will be added to your sysinit runlevel, but not
udev-settle. udev-settle should not be added to a runlevel. Instead, if
a service needs this, it should add "need udev-settle" to its
dependencies.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]