[systemd-devel] recent udev dependency change delays plymouth and udev

[Lennart Poettering]

On Tue, 07.04.15 18:10, Dimitri John Ledkov (dimitri.j.ledkov at intel.com) wrote:

> On 2 April 2015 at 00:39, Martin Pitt <martin.pitt at ubuntu.com> wrote:
> > Hello all,
> >
> > The recent commit
> > http://cgit.freedesktop.org/systemd/systemd/commit/?id=d99ce933 (which
> > also made it into v219-stable at
> > http://cgit.freedesktop.org/systemd/systemd-stable/commit/?h=v219-stable&id=b238b0eaf71)
> > fixed a typo in udevd's dependencies, which now results in udev
> > waiting for systemd-hwdb-update.service.
> >
> > While this is certainly "correct" especially for stateless systems, it
> > is quite a bit inconvenient as it now causes a long dependency chain:
> >
> > plymouth-start.service → systemd-udevd.service → systemd-hwdb-update.service →
> > systemd-remount-fs.service → systemd-fsck-root.service → systemd-fsckd.socket
> >
> 
> I dislike building hwdb on boot, thus locally I make sure that update
> mechanisms have up to date @udevlibexecdir@/hwdb.bin and thus
> systemd-hwdb-update.service is not run.
> 
> If triggers rebuild the database, shouldn't the update-process /
> conditions be modified such that the database is not rebuild on boot?

Hmm? I cannot parse this?

The hwdb rebuild is only done at boot if /etc/.updated is older than
/usr, or non-existant. If your distro upgrade routine updates /etc in
full before rebooting, you can just touch that file afterrwards, and
the service will not trigger...

Lennart

-- 
Lennart Poettering, Red Hat