On 12/05/2011 06:53 AM, Andreas Jaeger 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...
Yes, no problem for things that run all the time. But for things that only run once and do not have a "formal" firstboot procedure it appears overkill. Previously a simple if [ -f SOME_TRIGGER ]; then RUN_MY_ONETIME_SETUP REMOVE_THE_TRIGGER fi did just fine. Of course I can set up a unit file for this but that just seems stupid. What I don not know and have not tried is what happens when one installs yast2-firstboot and has no firstboot.xml. Wonder if a script in /usr/share/firstboot/scripts would be executed in this case. In any event the key is one time automatic configuration (no keyboard, no monitor connected) Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org