does yast/instorder matter? Syntax errors in examples.
In some recent verification tests of my http installation server for SLES8 with Service Pack (both 2a & 3), it appears that the contents of the yast/instorder file do not affect the resulting system image. NOTE: this file is documented as having only one field. Many of the examples show 2 tab delimited fields. When you use a tab delimited file, the yast/instorder file appears to be ignored, and the displayed order of sources is as described in the yast/order file. While the listing of source order, as displayed during installation, does differ between a valid yast/instorder and an invalid one, there are no differences in the resulting systems (as measured by comparing 'rpm -qa' output from both variations). As I had read the documentation's description of the purpose of the yast/instorder file, I did expect some differences w.r.t. the yast2 packages. --Hal
Am experiencing 2 problems with my autoinst: 1, I am setting the root password using the md5 option, as well as creating a single user. The user gets created properly, along with the desired password, but the root password ends up blank - not sure if my password has a character in it that yast doesn't like, or if this is a known issue. How can I pre-crypt the password to place in the file? (should I set my local passwd and check my shadow file?) Is there a better workaround? 2. Am trying to set the firewall, ssh and apache to the correct runlevels. If I set the levels through Autoyast, it doesn't enable them, so the daemons don't actually get started. What is the proper method of setting a daemon to start at level 3 and to actually be enabled? Thanks
Root password getting set through autoinstall seems to be a problem; here is a work around: <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list"> <script> <filename>setrootpw</filename> <interpreter>shell</interpreter> <source> <![CDATA[/usr/bin/perl -pi -e 's#^root::.*$#root:<MDD5Encryption>:::::::\n#' /etc/shadow exit 0]]> </source> </script> </scripts> I wound up writing another script and making the links myself in the proper run mode directories. you need links in 3 and 5 if you expect something to run in both run levels, Scripts in 3 will not be started on the way to run level 5. Todd On Wed, 2004-02-04 at 11:24, steven.cardinal@adheris.com wrote:
Am experiencing 2 problems with my autoinst:
1, I am setting the root password using the md5 option, as well as creating a single user. The user gets created properly, along with the desired password, but the root password ends up blank - not sure if my password has a character in it that yast doesn't like, or if this is a known issue. How can I pre-crypt the password to place in the file? (should I set my local passwd and check my shadow file?) Is there a better workaround?
2. Am trying to set the firewall, ssh and apache to the correct runlevels. If I set the levels through Autoyast, it doesn't enable them, so the daemons don't actually get started. What is the proper method of setting a daemon to start at level 3 and to actually be enabled?
Thanks
participants (3)
-
Hal Wine -
steven.cardinal＠adheris.com -
Todd Ness