[systemd-devel] [PATCH 07/10] units: order remote-fs.target after local-fs.target

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 16, 2014 at 03:56:27PM +0200, Jon Severinsson wrote:
> > So the only thing it does is that it'll delay remote-fs.target if it were to
> > be reached before local-fs.target.
> 
> Which in my oppinion is a good thing, as writers of service files, as well as 
> legacy init scripts, should rightfully be able to assume that if they request 
> all remote file systems to be mounted, local file systems will be too.
> 
> Also I would have a hard time explaining why a change of a remote mount to a 
> local one should be allowed to cause regressions...
local-fs.target is part of sysinit.target, so all normal units get it
by default. Explicit relationships with local-fs.target are only necessary
for special early-boot services, which have to carefully set all dependencies,
so are out of scope here. Everything else should be fine.

Zbyszek