I know I've asked this once before, but I've spent some more time going through the scripts and still can't find out how to accomplish what I'm looking for (having the lan module run during Yast2.firstboot, without taking the default proposals)
From what I gather, if you use autoyast it does a few things to prep the
system for the first. 1) creates the /var/lib/YaST2/runme_at_boot file and 2) creates the /etc/install.inf
... It does other stuff, but I'm not worried about that right now.
When /etc/init.d/boot is run it checks for runme_at_boot and if that exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts
/usr/lib/YaST2/bin/YaST2 installation continue
This reads the /etc/install.inf file and the values there are used for the rest of the autoinstall.
If I make Manual = 1 in /etc/install.inf, yast asks about the network modules, but never drops me to the yast2 lan module, it looks like it just accepts the proposal based on the autoyast=file///a.xml file.
If I could force the lan module to run and not accept any defaults it would save me the hassle of having to generate new ssl certificates after running yast lan (host name changes).
Thanks again,
-m
-----Original Message----- From: Michael Shannon [mailto:Michael.Shannon@infospace.com] Sent: Tuesday, December 21, 2004 2:42 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] YaST.firstboot question
For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction.
I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :(
It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this?
Thanks,
-m
The answer to your question lies in the control.xml file which controls the workflow of the installation. autoyast has a different workflow than the manual installation and it shows no proposals in second stage. If you want the network proposal, you have to added it to the autoinstallation workflow. See http://yast2.suse.com/tdg/html/yast2-installation.html#product_control
for more detailes. (Above document is still work in progress).
Anas
Michael Shannon wrote:
I know I've asked this once before, but I've spent some more time going through the scripts and still can't find out how to accomplish what I'm looking for (having the lan module run during Yast2.firstboot, without taking the default proposals)
From what I gather, if you use autoyast it does a few things to prep the system for the first.
- creates the /var/lib/YaST2/runme_at_boot file and
- creates the /etc/install.inf
... It does other stuff, but I'm not worried about that right now.
When /etc/init.d/boot is run it checks for runme_at_boot and if that exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts
/usr/lib/YaST2/bin/YaST2 installation continue
This reads the /etc/install.inf file and the values there are used for the rest of the autoinstall.
If I make Manual = 1 in /etc/install.inf, yast asks about the network modules, but never drops me to the yast2 lan module, it looks like it just accepts the proposal based on the autoyast=file///a.xml file.
If I could force the lan module to run and not accept any defaults it would save me the hassle of having to generate new ssl certificates after running yast lan (host name changes).
Thanks again,
-m
-----Original Message----- From: Michael Shannon [mailto:Michael.Shannon@infospace.com] Sent: Tuesday, December 21, 2004 2:42 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] YaST.firstboot question
For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction.
I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :(
It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this?
Thanks,
-m
autoinstall@lists.opensuse.org
-
Anas Nashif -
Michael Shannon