On today's update (includeing eudev-1.1 → eudev-1.3) I've seen the following message: * Please add the udev-postmount init script to your default runlevel * to ensure the legacy rule-generator functionality works as reliably * as possible. * rc-update add udev-postmount default * But I already have udev-postmount script in my default runlevel: # rc-update show | grep udev-postmount udev-postmount | default Ebuild (sys-fs/eudev/eudev-1.3.ebuild) contains the following conditions for this message: "if use rule-generator && use openrc; then" To my mind portage also should perform a check about udev-postmount script status and echo this message only if it isn't present in auto-start (rc-update show) list.
1. udev-init-scripts, which is a dependency for eudev, suggests to remove udev-postmount from any of runlevels. It's not used by sys-fs/udev. 2. Why udev-postmount (eudev's) supposed to run in default runlevel?
sys-fs/udev doesn't do any rule-generation since version 183; eudev does, however, when built with USE="rule-generator". The udev-postmount init script is specifically meant to be run after all (at least local) filesystems have been mounted, so that any generated rules can be saved to disk. I concur with the original poster; this message only -needs- to be specified when eudev is built with USE="rule-generator" enabled. Technically, if we follow the other recent elog recommendations, it shouldn't show up unless USE="rule-generator" goes from disabled to enabled, regardless of whether it is actually in a runlevel. We will adjust for the next revision. Thanks for reporting!
(In reply to Ian Stakenvicius from comment #2) > sys-fs/udev doesn't do any rule-generation since version 183; eudev does, > however, when built with USE="rule-generator". The udev-postmount init > script is specifically meant to be run after all (at least local) > filesystems have been mounted, so that any generated rules can be saved to > disk. > > I concur with the original poster; this message only -needs- to be specified > when eudev is built with USE="rule-generator" enabled. Technically, if we > follow the other recent elog recommendations, it shouldn't show up unless > USE="rule-generator" goes from disabled to enabled, regardless of whether it > is actually in a runlevel. > > We will adjust for the next revision. Thanks for reporting! Ian can you take care of this in 1.5.3-r1 and -9999.
(In reply to Anthony Basile from comment #3) > (In reply to Ian Stakenvicius from comment #2) > > sys-fs/udev doesn't do any rule-generation since version 183; eudev does, > > however, when built with USE="rule-generator". The udev-postmount init > > script is specifically meant to be run after all (at least local) > > filesystems have been mounted, so that any generated rules can be saved to > > disk. > > > > I concur with the original poster; this message only -needs- to be specified > > when eudev is built with USE="rule-generator" enabled. Technically, if we > > follow the other recent elog recommendations, it shouldn't show up unless > > USE="rule-generator" goes from disabled to enabled, regardless of whether it > > is actually in a runlevel. > > > > We will adjust for the next revision. Thanks for reporting! > > Ian can you take care of this in 1.5.3-r1 and -9999. Done. I also patched udev-init-scripts so that it doesn't ask users to remove the runlevel anymore if eudev[rule-generator] is installed, that should be a big help.
(In reply to Ian Stakenvicius from comment #4) > (In reply to Anthony Basile from comment #3) > > (In reply to Ian Stakenvicius from comment #2) > > > sys-fs/udev doesn't do any rule-generation since version 183; eudev does, > > > however, when built with USE="rule-generator". The udev-postmount init > > > script is specifically meant to be run after all (at least local) > > > filesystems have been mounted, so that any generated rules can be saved to > > > disk. > > > > > > I concur with the original poster; this message only -needs- to be specified > > > when eudev is built with USE="rule-generator" enabled. Technically, if we > > > follow the other recent elog recommendations, it shouldn't show up unless > > > USE="rule-generator" goes from disabled to enabled, regardless of whether it > > > is actually in a runlevel. > > > > > > We will adjust for the next revision. Thanks for reporting! > > > > Ian can you take care of this in 1.5.3-r1 and -9999. > > Done. > > I also patched udev-init-scripts so that it doesn't ask users to remove the > runlevel anymore if eudev[rule-generator] is installed, that should be a big > help. Looks good thanks!
