On Sat, Jun 30, 2012 at 3:34 PM, Colin Guthrie <gm...@colin.guthr.ie> wrote: > 'Twas brillig, and Kay Sievers at 29/06/12 23:48 did gyre and gimble: >> On Fri, Jun 29, 2012 at 3:15 AM, Colin Guthrie <gm...@colin.guthr.ie> wrote: >>> 'Twas brillig, and Lennart Poettering at 27/06/12 21:38 did gyre and gimble: >>>> On Wed, 27.06.12 14:56, Dave Reisner (dreis...@archlinux.org) wrote: >>>> >>>>> The service is systemd-udev.service, not systemd-udevd.service. >>>> >>>> Applied, thanks! >>> >>> Why isn't it called systemd-udevd.service? It would be more consistent >>> with the others (systemd-logind.service, systemd-journald.service, >>> systemd-localed.service etc.) >> >> Sound good to me to rename it to *d. > > I've done this in my tree. Quick question... which of the systemd-udev* > units should be renamed? > > Obviously systemd-udev.service, but what about > systemd-udev-control.socket and systemd-udev-kernel.socket which are > really sockets relating quite strongly to the daemon so perhaps should > follow suit? > > And finally systemd-udev-settle.service and > systemd-udev-trigger.service. These (to me) feel like they should remain > as they currently are.
Sure, sounds fine to rename the sockets too, and leave the rest. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel