On Thu, 14.02.13 17:47, Seunghun Pi (sh...@samsung.com) wrote: > From: Byung-Soo Kim <bs1770....@samsung.com> > > From: Byung-Soo Kim <bs1770....@samsung.com> > > In case of root file system mounted in read-only mode, > the collected data cannot be stored. > Then add code to specify directory path of collected data as RW position. > With --savedir=PATH option, collected data can be stored in the path.
I am quite open to moving this readahead file, but there's a bit of a chicken and egg problem here: the readahead file must be available very early at boot, so it probably should be on the root file system, but if that's read-only, what to do? So, can you elaborate how your setup precisely is? There has been a long-standing item on the TODO list actually to move the readahead file to /var/lib or so, but conditionalize that on that /var/lib actually is on the same mount as /. The replay tool would look for both paths basically, and the collection tool would use /var/lib if possible in /.readahead otherwise... Anyway, before we do something about this I'd really like to figure out how you solve the "must be on root, but root is read-only" issue? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
