On Mon, Dec 5, 2011 at 6:53 AM, Andreas Jaeger <aj@suse.com> wrote:
On Monday, December 05, 2011 06:47:12 Mark Gray wrote:
On Mon, Dec 5, 2011 at 5:16 AM, Andreas Jaeger <aj@suse.com> wrote:
What is your use-case? Perhaps it can be solved differently
On the only computer where it matters, my after.local sets up my iptables (so networking should be up), and uses the --bind option of mount to "splice" my large archive disk into several places on my smaller root disk (so all file systems need to be mounted rw by then.)
So far putting these into boot.local works fine, but my reading of boot.local's use suggests it might be executed at most any point in the boot process, and after.local's used to be executed after the run level was reached.
You can create separate service for these, there shouldn't be a problem...
Good enough -- I suppose I really should learn systemd. I have a premonition though that systemd's configuration "language" is going to undergo a major change before I die (like bind and grub2 did) making everything I learn about it obsolete :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org