[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-autoinstall
Subject:    Re: [suse-autoinstall] changing init script launch sequence & getting
From:       Rich <rich () hq ! vsaa ! lv>
Date:       2006-10-18 12:30:06
Message-ID: 45361E4E.80600 () hq ! vsaa ! lv
[Download RAW message or body]

Uwe Gansert wrote:
> On Wednesday 18 October 2006 13:11, Rich wrote:
> 
>> is it possible to easily change init script ('autoyast') launch
>> sequence/requirements so that it is launched after sshd has started ?
>> currently, it runs together with sshd, which is generating keys for some
>> time, and that is inconvenient for some actions script has to perform.
> 
> hm. Have you tried to turn off the RUN_PARALLEL in /etc/sysconfig/boot?
> Maybe you have to do that in a chroot script, because the sysconfig section 
> in the profile might be evaluated too late.

i'll try this. will probably have to enable it later, and this probably 
would slightly increase time needed for the initial boot.

at which point does /etc/init.d/autoyast appear ? maybe it is possible 
to simply add sshd to Required-Start ? or even better - add autoyast to 
sshd required services... yes, this would be even better. i'll try doing 
this in chroot script, then :)

>> additionally, is it possible to get init script location data (defined
>> in <location>) in the script itself some way (a variable ?) ?
>> as in "use here the same host/directory you came from".
> 
> maybe you can try to put the location in the <filename> too. Then you can 
> access it via $0

this would remove the benefit, as i would like to access initial script 
from a remote http server. putting address in location would require 
remastering the boot cd every time location changes.
that is unless, i misunderstood something :)

> Or you can use a chroot-script that evaluates the /tmp/profile/autoinst.xml 
> and stores the location information in /mnt/tmp for the init-script later.
> Those are the only ideas I have at the moment.

this would probably work, although making the setup slightly more complex.
would it make sense to export data like this to scripts with some 
environment variables ? if so, i could report a wish.
-- 
  Rich

-- 
To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com
For additional commands, e-mail: suse-autoinstall-help@suse.com

[prev in list] [next in list] [prev in thread] [next in thread]