[gentoo-user] Re: udev and init.d. Should it be running now?

[walt <w41ter@gmail.com>]

On 09/10/2009 03:43 PM, Dale wrote:
> Jonathan Callen (ABCD) wrote:
>> Dale wrote:
>>> Hi folks,
>>
>>> I was browsing around and noticed that I now have a udev in
>>> /etc/init.d/.  I checked, it is not running but udevd is not running
>>> either.  See below:
>>
>>>> root@smoker / # /etc/init.d/udev status
>>>>   * status:  stopped
>>>> root@smoker / #
>>>> root@smoker / # ps aux | grep udev
>>>> root     30451  0.0  0.0   1888   504 pts/0    R+   16:04   0:00 grep
>>>> --colour=auto udev
>>>> root@smoker / #

>>> Also, keep in mind, everything works fine.  I just don't want to add it
>>> to boot or default runlevels and then break something.
>>
>> In baselayout-1, udev is started directly by baselayout itself, outside
>> of any init scripts.  In baselayout-2/openrc, an initscript is needed to
>> start udev.  If you actually read the script, you may notice that the
>> script will immediately fail if you attempt to run it on a baselayout-1
>> system, as it isn't needed...
>
> ...Anyway, I used ps and less to list those processes and noticed
> that udev was not running.  It used to be running in the past.

I was surprised to read Jonathan's post, but I see he's right.  On my
x86 machine the status of udev is "stopped" and on ~amd64 it's "started".

But both machines show that /sbin/udevd is indeed running, so I can see
why you are uneasy about your status quo.

Have you tried running /sbin/udevd --daemon from a command prompt? When
I try it I get a message that udevd is already running.