From: "Jonathan Callen (ABCD)" <abcd@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: udev and init.d. Should it be running now?
Date: Thu, 10 Sep 2009 18:05:28 -0400 [thread overview]
Message-ID: <4AA97828.3000102@gentoo.org> (raw)
In-Reply-To: <4AA96A8A.6010608@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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 / #
>
> This is the baselayout that is installed:
>
>> [I--] [ ] sys-apps/baselayout-1.12.11.1
>
> I seem to recall that baselayout 2 is going to be a service thing but
> since I am on baselayout 1, should this be running? It seems to belong
> to the udev package tho according to this:
>
>> root@smoker / # equery belongs /etc/init.d/udev
>> [ Searching for file(s) /etc/init.d/udev in *... ]
>> sys-fs/udev-141 (/etc/init.d/udev)
>> root@smoker / #
>
> You can see from that what udev version is installed too. I also
> checked the elogs and I see no mention of it being changed to a service
> or that it needs to be added to a runlevel.
>
> Also, keep in mind, everything works fine. I just don't want to add it
> to boot or default runlevels and then break something.
>
> Thanks for any advice. I searched the forums and udev on g.o but didn't
> see anything relevant.
>
> Dale
>
> :-) :-)
>
>
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. If/when you upgrade to baselayout-2/openrc,
it will automatically be added to the boot runlevel, but only if
baselayout-1 had been previously installed.
In short, don't worry about it. :)
(this didn't appear to send the first time, so resending...)
- --
Jonathan Callen (ABCD)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqpeCgACgkQOypDUo0oQOppywCfa3+jnwddXZfocNqvDeWbbjGC
3UAAoL7b9ElKq+72QpFwtrW/hpSWVUOD
=3KGk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-09-10 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 21:07 [gentoo-user] udev and init.d. Should it be running now? Dale
2009-09-10 22:05 ` Jonathan Callen (ABCD) [this message]
2009-09-10 22:43 ` [gentoo-user] " Dale
2009-09-11 1:15 ` walt
2009-09-11 1:26 ` Dale
2009-09-11 4:23 ` Philip Webb
2009-09-11 4:43 ` Dale
2009-09-12 11:23 ` Dale
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=4AA97828.3000102@gentoo.org \
--to=abcd@gentoo.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox