Bug#778554: unblock: systemd/215-12

Martin Pitt mpitt at debian.org
Tue Feb 17 14:11:24 GMT 2015


Hey Niels,

Niels Thykier [2015-02-16 20:10 +0100]:
> I have not had time to review this fully.  However, I noticed #778565,
> which suggests a regression in this version of udev.  I am putting this
> unblock request on hold until you have had a time to review #778565.

Michael and I responded to that and asked for some more information
and log output. This looks very dubious, given that udev hardly
changed at all in 215-12 except for blacklisting the mmcblkb-*rpmb
devices (which are totally unrelated).

> > While you are at it, would you mind having a look at #755722? I'd be
> > interested in your opinion whether for jessie we should (1) ignore the
> > problem, (2) apply the sysv behaviour compatible hwclock.service, or
> > (3) boldly go and enable timesyncd.
> > 
> > Thanks,
> > 
> > Martin
> > 
> > unblock systemd/215-12
> > 
> 
> Personally, I am leaning towards (2) in the absence of a patch/diff for (3).

The bug trail has a pointer to the experimental fix for this:

  http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=929bece5326

But anyway, this will not cover the edge cases that the (rather vocal)
reporters of #755722 are concerned about, e. g. if the machine is
always offline. So (3) is probably not a full solution yet, and this
might require some more adjustment in fsck or other places.

>   Though, as I understood the link to the upstream date, part of the
> reason for not sync'ing the time was to make it easier on live-CDs.  Is
> this the sort of change that will break live-CDs?  If so, what will it
> take to "not break" live-CDs with (2) (or possibly (3)).

I figure this rather means "live CDs are not supposed to touch the
system", and syncing the hw clock to a potentially wrong time of a
live system is bad. However, that's precisely what has happenend under
sysvinit (through util-linux' /etc/init.d/hwclock.sh) all the years;
that's what I meant with "bug compatible to sysvinit" :-)
However, with (3) we'd essentially get the same behaviour if the live
system gets network connectivity.

Personally I'm leaning towards the hwclock-save.service (2) or even
ignoring this (1).

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150217/80cee895/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list