On Tue, 08.07.14 14:38, Chaiken, Alison (alison_chai...@mentor.com) wrote: > >I am actually all for moving the file, though. But can't we find a more > >automatic solution for this, that doesn't > >require manual configuration. Maybe a scheme like this could work: > >a) readahead-reply would look for both /.readahead and > > /var/lib/systemd/readahead. If both files exist, it picks the newer > >one, if only one exists it picks that one. > >b) readahead-collect would check if /var/lib/systemd is on the same > >mount point as /. If so, it would store the file in > > /var/lib/systemd/readahead. Otherwise it would store the file in > > /.readahead, as before. > >This would move the file for most folks, while still allowing a split off > >/var -- but I figure this wouldn't solve your specific problem? > > In our case, /var/lib/ is part of / partition that is unwritable, but > /var/opt is not. How about a tristate option, where we implement the > solution you suggest above, but also allow runtime specification to > override the other two choices?
I think we should cover the usual setups with systemd upstream only, where /var is variable, as the name suggest, and hence writable during runtime. It is OK to run things differently, but that would have to be a downstream change. That all said, we have the intention to remove systemd-readahead entirely from the package (see announcement the other day), hence I am not sure it's worth investing any more time in this anyway... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
