[yast-devel] Writting to SCR before system installed
Hi List, I'm developing a module that will run as part of the autoyast installation workflow. It prompts the user for certain details that are only know at the time of auto installation. I've already included that module and a blank /etc/sysconfig/file file into the Installation System's cramfs image. The process that I designed works like this: - when autoyast starts, ask the user for the settings - use SCR to save the settings to /etc/sysconfig/file - just before the system is rebooted, copy the /etc/sysconfig/file to the installed hard drive. Here's the prompt. With step #2, I call SCR::Write but it doesn't write! I don't see any errors /var/log/YaST2/y2log either. Yet, if I run the module manually it rights fine. In both test cases, I'm starting the install using the ssh remote installation method of SLES10. This allows me to log in and fire off yast2 or the custom module itself at will. Any thoughts? The module is due soon and I don't want to disappoint. Thanks! -- Lee Leahu Home Office: 1-815-630-2349 RICIS, Inc. Cell Phone: 1-847-337-3422 lee@ricis.com Main Office: 1-708-444-2690 NOTICE: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne pondělí 19 Leden 2009 20:06:15 Lee Leahu napsal(a):
Hi List,
I'm developing a module that will run as part of the autoyast installation workflow.
It prompts the user for certain details that are only know at the time of auto installation.
I've already included that module and a blank /etc/sysconfig/file file into the Installation System's cramfs image.
The process that I designed works like this: - when autoyast starts, ask the user for the settings - use SCR to save the settings to /etc/sysconfig/file - just before the system is rebooted, copy the /etc/sysconfig/file to the installed hard drive.
Here's the prompt. With step #2, I call SCR::Write but it doesn't write! I don't see any errors /var/log/YaST2/y2log either.
Yet, if I run the module manually it rights fine.
Without knowing any details, my guess is that you use the ini-agent for writing the file. It has cache and writes the settings when YaST finishes or when being told explicitly. To dump the caches to the disk, you need to call SCR::Write (.path.you.registered.the.agent.at, nil), e.g. SCR::Write (.sysconfig.windowmanager, nil); Other option would be to store all the data in memory and save it after all packages are installed; then SCR gets redirected to the target system (I'd need to know more details to hint how to best achieve it). Hope that helps, Jiri
In both test cases, I'm starting the install using the ssh remote installation method of SLES10. This allows me to log in and fire off yast2 or the custom module itself at will.
Any thoughts? The module is due soon and I don't want to disappoint.
Thanks!
-- Lee Leahu Home Office: 1-815-630-2349 RICIS, Inc. Cell Phone: 1-847-337-3422 lee@ricis.com Main Office: 1-708-444-2690 NOTICE: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer.
-- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Jiri,
Thanks for your help.
I was able to get it working using your recommendation of calling
'SCR::Write(.path.to.agent, nill)'.
I also discovered that files in /etc/sysconfig/... in the installation server
are sym links to read-only media.
I worked around by creating a new agent that stores the config in /dev/shm/...
and then copy that file to the installed drive once the packages are installed.
On Tue, 20 Jan 2009 02:37:08 -0600
Jiri Srain
Dne pondělí 19 Leden 2009 20:06:15 Lee Leahu napsal(a):
Hi List,
I'm developing a module that will run as part of the autoyast installation workflow.
It prompts the user for certain details that are only know at the time of auto installation.
I've already included that module and a blank /etc/sysconfig/file file into the Installation System's cramfs image.
The process that I designed works like this: - when autoyast starts, ask the user for the settings - use SCR to save the settings to /etc/sysconfig/file - just before the system is rebooted, copy the /etc/sysconfig/file to the installed hard drive.
Here's the prompt. With step #2, I call SCR::Write but it doesn't write! I don't see any errors /var/log/YaST2/y2log either.
Yet, if I run the module manually it rights fine.
Without knowing any details, my guess is that you use the ini-agent for writing the file. It has cache and writes the settings when YaST finishes or when being told explicitly.
To dump the caches to the disk, you need to call
SCR::Write (.path.you.registered.the.agent.at, nil), e.g.
SCR::Write (.sysconfig.windowmanager, nil);
Other option would be to store all the data in memory and save it after all packages are installed; then SCR gets redirected to the target system (I'd need to know more details to hint how to best achieve it).
Hope that helps, Jiri
In both test cases, I'm starting the install using the ssh remote installation method of SLES10. This allows me to log in and fire off yast2 or the custom module itself at will.
Any thoughts? The module is due soon and I don't want to disappoint.
Thanks!
-- Lee Leahu Home Office: 1-815-630-2349 RICIS, Inc. Cell Phone: 1-847-337-3422 lee@ricis.com Main Office: 1-708-444-2690 NOTICE: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer.
-- Regards,
Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Thanks! -- Lee Leahu Home Office: 1-815-630-2349 RICIS, Inc. Cell Phone: 1-847-337-3422 lee@ricis.com Main Office: 1-708-444-2690 NOTICE: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (2)
-
Jiri Srain -
Lee Leahu